Accessibility
What is built in, what is missing, and how to tell us about something we have got wrong.
This site has not been audited, so we make no conformance claim. Below is what is built into these pages, and what we know is missing.
What is built in
- Everything works from the keyboard. No control needs a pointer, and the collapsible questions on the home page are native
<details>elements rather than scripted ones, so they behave the way your browser already behaves. - Focus is always visible. A 2px focus ring is defined in the stylesheet that loads with the document, so it survives even if the styling layer fails to load.
- Motion respects your setting. Every animation is switched off under
prefers-reduced-motion, including the turning icons on the questions. - Color is never the only signal. Links in text are bold as well as colored, and states in the product illustrations carry a word, not just a color.
- Structure is real. Headings are headings, lists are lists, navigation regions are labeled, and decorative illustrations are hidden from assistive technology rather than described as if they mattered.
- The page does not scroll sideways. Every page is checked from 320px upward; wide content scrolls inside its own container rather than pushing the page.
What is missing
Sizes on this site are set in pixels, so if you have raised the default font size in your browser settings, these pages will not follow it. Browser zoom does work, and works properly. This is a real limitation and a fair thing to hold against us.
The points above are things we built and can point at in the markup. They are not the same as someone using this site with a screen reader for an hour and telling us what happened. Nobody has done that yet.
The extension's side panel is a different surface with its own controls, and it has not been assessed to the same level.
Telling us about a problem
If something here does not work for you, write to us. It reaches the people who can change it. Tell us what you were trying to do and what happened instead. You don't need to know why it broke.
Reports about the site's accessibility are treated as defects, not as feature requests.