Accessibility
Built to be used by everyone.
We treat accessibility as a design constraint, not an afterthought. This page documents what we aim for, where we know we still fall short, and how to tell us when we get it wrong.
What we target
The site aims to meet WCAG 2.2 Level AA. In practice that means:
- Contrast. Body text on both the light and dark theme meets the 4.5:1 ratio AA requires; large text and interface controls clear 3:1. The stone palette is checked against the same target whenever a colour changes.
- Keyboard. Everything that can be clicked can be reached and operated with a keyboard. Focus rings are visible on every actionable element, and a "Skip to content" link is the first focusable thing on every page.
- Structure. Pages use one
h1and a heading outline without level jumps, landmark regions for navigation, main content and footer, and real lists for list-like content. - Motion. Transitions are short and respect the operating system's reduced-motion preference; nothing on the site autoplays.
- Dark mode. Both themes are designed to the same contrast targets. The theme follows the system preference by default and remembers a manual choice.
- Images. Photographs and figures carry alternative text; decorative images carry
an empty
altso screen readers skip them rather than reading a filename.
How the site is built
Pages are static HTML generated at build time. A small amount of JavaScript (Alpine.js) drives the mobile menu, the theme toggle and the publication filters. Without JavaScript, the publications page shows every entry, the theme follows the system setting, and the header links remain reachable via the footer, which lists every section. Embedded videos are click-to-play and use YouTube's no-cookie domain; LinkedIn posts are LinkedIn's own embeds.
Known gaps
- Some project images are placeholders rather than the lab's own science. They have meaningful alternative text and will be swapped as real images are supplied.
- Video captions rely on YouTube's automatic captioning. Lab-reviewed captions for the most-watched videos are on the to-do list.
-
Embedded LinkedIn posts are rendered by LinkedIn inside an
iframe; their internal accessibility is LinkedIn's, not ours. Every post is also linked to on LinkedIn itself. - We have not yet completed an independent third-party audit against WCAG 2.2 AA. The internal pass uses semantic markup, automated checks, and manual keyboard and screen-reader walk-throughs.
Report a problem
If something on this site is hard to read, hard to operate, or fails with assistive technology, please email m.ghajari@imperial.ac.uk with the page URL, the assistive technology you were using, and a short description of what went wrong. We treat accessibility reports as first-priority work.