Accessibility checks
Find common accessibility problems and review new or worsened findings.
Turn on checks#
An owner or admin opens the project's accessibility settings and enables Check accessibility on new runs. Framecheck runs axe-core checks for WCAG 2.2 A/AA issues on captured web stories, including supported same-origin iframes.
Accessibility runs in Chromium only and adds a billed check per tested story and viewport. It is separate from the visual snapshot limit.
Choose enforcement#
| Setting | Behaviour |
|---|---|
| Report only | Findings are listed without failing the PR check. This is the default. |
| Block pull requests | New issues affect the check according to the PR policy. |
For blocking checks, choose an impact threshold: critical only, serious and critical, moderate and above, or all issues. Lower-impact findings remain visible even when they are below the blocking threshold.
Review findings#
Open the run's Accessibility tab. Inspect the rule, impact, affected element, and suggested remediation. Compare new and worsened findings with the accepted accessibility baseline. Needs review means the automated rule could not decide; it is not a pass.
Visual approvals and accessibility approvals are separate. Approving the screenshot does not approve its accessibility findings. Establish the findings baseline on an accepted default-branch run and review later changes deliberately.
Ignore or skip deliberately#
Project settings let you ignore named rules, such as color-contrast. Use the rule ID shown in the results. Changing ignored rules changes what is checked and requires the next default-branch findings to be accepted again.
A story can skip accessibility with parameters.a11y.disable: true or parameters.a11y.test: 'off'. It will be reported as skipped, not successful. Other addon-a11y configuration is not automatically honoured.
Trends and CSV exports#
Open Accessibility trends from the project to inspect changes over time and download the offered CSV reports. Runs also provide a findings CSV. Use exports to organise remediation work, while checking the run and commit associated with each result.
Limits of automated checks#
Automated checks catch common issues, not every accessibility barrier. Test keyboard navigation, focus order, screen-reader behaviour, meaningful content, and real user tasks yourself. A green automated result is not a compliance certificate. Native screenshot capture does not imply native accessibility scanning.