We have not had this site audited, so it carries no conformance claim — a badge nobody has measured is worth less than an honest list. What follows is what is actually 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 sections in the Help Center 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 pulsing indicators in the product illustrations. - Colour is never the only signal. The current article in the Help Center rail carries a bar and bold weight, not just a colour; states in the illustrations carry an icon and a word.
- Structure is real. Headings are headings, lists are lists, navigation regions are labelled, 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. Where it falls short, it falls short — we would rather say that than let this page imply otherwise.
Telling us about a problem
If something here does not work for you, the repository's issues are the fastest route to the people who can change it, and the one place a report is visibly acted on. A description of what you were trying to do and what happened instead is plenty — you do not need to know why it broke.
Reports about the site's accessibility are treated as defects, not as feature requests.