Documentation menuDocumentation
Surjection documentation
Accessibility checks for CI and tests, client-ready reports and accessibility statements in five languages. Built on axe-core, no overlay.
Try the live demoStart
Guides
- CLICheck a whole site from the command line.
- Keyboard and loginFind focus traps and missing focus indicators, and check pages behind a login.
- States and click stepsCheck menus, dialogs and forms in their opened state with a few click steps.
- FlowsCheck a multi-step journey such as a checkout, with a check after each step.
- Layout checksReflow at 320 pixels and text spacing, two criteria axe-core cannot test.
- GitHub ActionsCheck every pull request and show the report in the job summary.
- PlaywrightCheck pages inside your existing end-to-end tests.
- VitestCheck React components and other DOM output in unit tests.
- BaselineAccept existing issues once and fail only on new ones.
- CoverageWhich WCAG 2.2 criteria Surjection tests automatically, and which stay manual.
- Testing componentsCheck single components in Storybook, Testing Library or any test with a DOM.
- Accessibility statementGenerate the accessibility statement in German, Swiss German, French, Italian or English.
- React building blocksSmall, unstyled components for patterns that are easy to get wrong.
- Migrating to 2.0What breaks in Surjection 2.0, what is new, and how to upgrade from 1.x.
- Upgrading to 1.0What changed on the way to 1.0.0 and what to do when upgrading from 0.x.
Reference
Surjection Pro
- Surjection ProBranded client reports, history across projects and the WCAG 2.2 checklist.
- Client reportAccessibility reports in your branding, as HTML or PDF.
- HistoryTrack accessibility results across client projects and runs.
- Manual checklistWork through the WCAG 2.2 A/AA success criteria that automated tests cannot cover.