Accessibility statement

Conformance target

The component library and this site are developed against WCAG 2.2 Level AA. Accessibility regressions are treated as bugs, not enhancements.

This statement covers automated conformance evidence plus known gaps. It is not a claim of full manual conformance: assistive-technology testing with real users is ongoing.

How the library is tested

• jest-axe suites on every component, run in CI on each pull request.
• Keyboard behaviour implemented as part of the component contract (roving tabindex in composite widgets, Escape/arrow handling, visible focus rings).
• Reduced motion honoured by streaming indicators, drawers, dialogs, and scroll behaviours.
• ARIA contracts documented in each COMPONENT_MANIFEST and enforced by the same rules agents see over MCP.

Read the accessibility guide for AI-generated UI for the per-component details.

How this site is tested

The documentation site runs an automated axe-core audit over its primary routes as part of the release checklist. The audit covers WCAG 2.0/2.1/2.2 A and AA rules and is reproducible from the repository:

pnpm --filter slipstream-ui-docs build
pnpm --filter slipstream-ui-docs start -- -p 3111
pnpm --filter slipstream-ui-docs audit:a11y -- http://localhost:3111

Routes covered: home, docs index, installation, representative component pages, MCP, templates, changelog, about, this page, contact, and the legal pages. Each route is audited in both light and dark mode. On November 4, 2026 the suite passed all 13 routes in both schemes (26 page runs, 0 violations), and Lighthouse reported Accessibility 100 on the sampled routes.

Automated tooling detects a subset of issues; it cannot validate reading order, task completion, or the quality of alternative text.

Known limitations

• A full manual screen-reader audit (NVDA on Windows, VoiceOver on macOS/iOS) is not yet complete. Automated coverage is not a substitute.
• Third-party content linked from the docs (GitHub, external standards pages) is outside our control.
• Some interactive demos simulate streaming and agent behaviour with timers; they are illustrative and keyboard-operable, but not production transports.

Reporting a barrier

If something blocks you, please open an issue with the page, the assistive technology you used, and what you expected. Security-sensitive reports should follow the security policy. You can also email support@slipstreamui.com.

We aim to acknowledge accessibility reports within five business days.