On this page
Accessibility in CI/CD
Pipeline placement#
Flow
Typical placement
- Unit / component checks (where useful)
- Pull request automation on key templates
- Staging crawl or smoke suite
- Release notes for known exceptions
What to gate#
Good CI gates
- Serious, low-noise rules that block merges
- Stable component stories / critical routes
- Explicit allowlists for temporary debt with owners
Poor CI gates
- Huge noisy rule sets nobody trusts
- Only homepage scans while apps live behind auth
- Green badge treated as full accessibility sign-off
Test
| Action | Expect |
|---|---|
Break a name | CI fails on a representative surface |
Review allowlist | Exceptions have owners and expiry |