Accessibility statement

The standard we aim for

The target is WCAG 2.2 level AA. It is a target, not a result: this site does not claim to conform to WCAG 2.2 AA, or to any other level, and no one has audited it against the full standard.

What is checked automatically

Three automated checks run in continuous integration on the built site. Each is limited, and the limits are listed with it.

• Colour contrast, in both themes. The axe-core color-contrast rule runs in the light theme and in the dark theme on every page in the sitemap, plus four pages that are not in the sitemap in a default build: the dashboard, style guide, Mermaid sandbox and newsletter pages. It also runs on the Change Feed Playground in several states (onboarding, feed after seeding, compare, and the three guided labs), in both themes. The list of excused elements is empty. Text drawn over a gradient is something axe cannot score; for the large gradient headlines the project measured the ratios separately, once, with a script.
• A wider axe rule set on six pages. The home page, overview, introduction, quickstarts, tooling and troubleshooting are checked against axe's WCAG 2.0 and 2.1 A and AA rules. Only violations that axe rates critical or serious fail the build. On four of those pages some rules are deliberately filtered out as known issues (see below). Diagrams drawn by Mermaid are excluded.
• pa11y with the WCAG 2 AA ruleset on eight built pages in the CI accessibility job (pa11y-ci), a separate engine from axe.

What automated checks cannot catch. Tools like these find only a minority of accessibility problems. They cannot tell whether alt text or link text makes sense, whether the reading order and focus order are sensible, whether a diagram or an interactive demo can be understood or operated without a mouse or without sight, or whether the content is clear. The axe rule sets used are tagged for WCAG 2.0 and 2.1, not for the criteria that are new in 2.2, so those are not checked automatically. The only keyboard test in the suite checks that the theme toggle can take focus.

What has not been done

Testing with assistive technology has not yet been done. No one has recorded a pass with a screen reader, a switch device or voice control, and there is no recorded keyboard-only or 200 percent zoom review. A test with real assistive technology on the home page, the introduction, a module page, the playground and the assistant panel is planned but has not happened. No disabled users have been consulted.

Known limitations

• Filtered rules on four pages. The automated suite ignores some axe rules there because the issues pre-date the check: /intro/ (aria-prohibited-attr, svg-img-alt, label, aria-allowed-attr), /quickstarts/ (label, link-name, aria-allowed-attr), /tooling/ (aria-allowed-attr) and /troubleshooting/ (label). These may be real barriers, for example a form field without a label or a link without a name, and they are not fixed.
• Interactive demos and diagrams. The event demo, the Change Feed Playground and the Mermaid diagrams are checked for colour contrast at most. Whether they can be operated by keyboard, or understood with a screen reader, has not been tested, and the assistant panel has no automated accessibility check beyond the page-level ones. Treat them as likely to have barriers.
• Third-party content. Some pages load libraries or embeds from other hosts, described on the privacy page. Their accessibility is outside this project's control.

Report a barrier

If something on the site is hard or impossible to use, please say what page, what you were trying to do, and what got in the way. Your assistive technology and browser help if you want to share them.

• Write to the maintainer at the public address on the contact page.
• Or open a public issue with the bug form on GitHub. Issues are public, so do not put anything private in one.

This is a one-person project, so there is no promised reply time and no promised fix date.

How this statement was written

This page was drafted with AI assistance from the repository's test scripts and records. It has not been reviewed by the maintainer or by an accessibility specialist. If it is wrong, tell us and it will be corrected.