Accessibility statement

This statement covers surea11y.dev, the site you're reading right now — not the accessibility findings a scan of your own site returns, which are covered by Conformance instead.

Conformance target

This site aims to conform to WCAG 2.2 at Level AA. It follows the same brand rules that govern every SureA11y product surface: colour is never the only cue (status and active-state indicators always pair colour with a second signal — an underline, a glyph, a word), every interactive control has a visible focus outline and a minimum 44px target, and every icon that isn't purely decorative carries a text alternative.

How this site is tested

This site is built by the same team that builds @surea11y/core, so it would be a strange place to skip testing with our own engine. Every change is scanned with @surea11y/core itself, in a real browser (Chromium, through @surea11y/playwright), against WCAG 2.2 AA at 375 and 1280 px wide, and nothing is deployed while that scan reports a fail. Every real finding gets fixed, not explained away. That scan has honest limits of its own (see Known limitations): it sees one state of each page, at those two widths, and what it can't decide it reports as cantTell for a person to check.

Automated scanning is only ever a floor, not a ceiling, so it isn't the only check this site gets. Changes are also subject to manual accessibility testing — keyboard-only navigation, a screen reader pass, and a check of the things no automated tool can judge at all (whether a heading actually describes what follows it, whether focus order matches visual order, whether content that only appears after an interaction is still reachable) — the same "automated tools can't tell you everything" position this whole project is built on.

Known gaps

• The "On this page" table of contents doesn't highlight your current scroll position — that would need client-side JavaScript, and this site ships none, by design. The links themselves work normally with a keyboard or screen reader; only the "you are here" highlighting while scrolling is absent.
• Code samples are intentionally rendered on a dark background even though the rest of the site is light — the same "a terminal is a terminal" exception documented in this site's own design system. If that specific contrast combination is hard to read for you, every code sample's text is still fully selectable and copyable as plain text.

Reporting a problem

If something on this site is hard to use with a keyboard, a screen reader, or any other assistive technology, please open an issue on GitHub. Include the page URL, what you were trying to do, and what happened instead — the same detail you'd want from anyone reporting a bug against the engine itself.