[docs] Add the accessibility conformance report page - #48926
[docs] Add the accessibility conformance report page#48926michelengelen wants to merge 14 commits into
Conversation
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
105fcde to
7b27bef
Compare
michelengelen
added
docs
e6438e9 to
9002c9b
Compare
1ab4a59 to
3196ec7
Compare
Lets a fixture assert every axe rule it exercises rather than only the CSS-dependent visual ones, which is what the per-component WCAG reports need.
Adds a table-driven Playwright suite covering 1.4.10 Reflow, 1.4.4 Resize Text and 1.4.12 Text Spacing across the assessed components. axe has no rule for any of them, so they were rated Manual on evidence from source review.
Adds `pnpm a11y:scorecard`, which parses the count table out of every `<Component>/accessibility.md`, regenerates the index table, and emits the JSON that the public conformance page is built from. `--check` fails when either output is stale so a new report cannot land without its rollup.
Compares each control focused and unfocused in a real browser. axe has no rule for this criterion, and the existing unit tests for it are skipped under jsdom, so it rested on source review alone. Drops the evidence flag on the six components that carried one. The rating stays Hybrid rather than Automated: the test proves an indicator exists, not that it has enough contrast, which is 1.4.11 and still manual.
A VPAT-style report of the library's WCAG 2.2 A/AA conformance, built from the per-component reports, for procurement and accessibility review. States its own limits up front: partial component coverage, no assistive-technology testing yet, and self-assessed rather than externally audited.
3196ec7 to
807c9b5
Compare
github-actions
Bot
added
the
PR: out-of-date
PR reviewNothing merge-blocking. The generated table was re-derived by hand against the twelve component reports and every column sums correctly (206 ✅ / 24 Docs (1)1. ℹ️ "Version assessed: master" is a moving targetLocation: Procurement teams consuming VPAT-style reports generally need a fixed product version. Tracking VerdictApprove - accurate rollup, well-scoped claims; only an optional versioning consideration. 🤖 Review generated with Claude Code |
2 participants
Adds a public accessibility conformance report at Getting started → Accessibility, answering #14187 (open since 2019, and explicitly a sales-enablement request).
It is a VPAT-style report of the library's WCAG 2.2 Level A/AA conformance, built from the per-component reports rather than written by hand. Every claim traces to a report in this series.
Includes the full Level A and AA criterion tables with remarks, the ● Component / ◐ Shared / ○ Author responsibility axis explained for procurement readers, and documented workarounds for each known gap.
It states its own limits up front, deliberately:
Those four are what still stand between this and something procurement can file, and they are worth discussing before this leaves draft.
Important
How to review this PR
Layer 14 of 14 in a stacked series (#48915 → #48926). Its branch is built on
a11y/stack/focus-visible(#48945). GitHub cannot chain PR bases across a fork, so every PR in the series targetsmasterinstead.Review only the last commit —
807c9b5. Everything above it belongs to the layers below, and disappears as those merge.Part of the WCAG conformance effort (#14187).