[test] Roll the per-component reports up into a library scorecard - #48925
Draft
michelengelen wants to merge 12 commits into
Draft
[test] Roll the per-component reports up into a library scorecard#48925michelengelen wants to merge 12 commits into
michelengelen wants to merge 12 commits into
Conversation
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
michelengelen
force-pushed
the
a11y/stack/scorecard
branch
from
August 5, 2026 09:57
86b1c28 to
ecd4bb5
Compare
michelengelen
force-pushed
the
a11y/stack/scorecard
branch
3 times, most recently
from
August 6, 2026 09:43
395996d to
62a50e8
Compare
michelengelen
force-pushed
the
a11y/stack/scorecard
branch
from
August 6, 2026 10:28
62a50e8 to
73bc1f7
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.
michelengelen
force-pushed
the
a11y/stack/scorecard
branch
from
August 6, 2026 10:43
73bc1f7 to
d637170
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
pnpm a11y:scorecard, which parses the count table out of every<Component>/accessibility.md, regenerates the index table inpackages/mui-material/src/accessibility.md, and emits the JSON the public conformance page is built from.pnpm a11y:scorecard:checkfails when either output is stale, so a new component report cannot land without its rollup.This is the aggregation @mj12albert described on #48708 — rolling the per-component scorecards up into a library-level one. Current totals across the 12 assessed components:
It also rolls results up per success criterion, taking the worst rating any component scores: 32 criteria exercised, 25 Supports, 7 Partially Supports, 0 Does Not Support.
Stack position. Builds on #48924. Until that merges this PR's diff also
shows its ancestors — review only the final commit:
86b1c28
Part of the WCAG conformance effort (#14187).
Also wires
pnpm a11y:scorecard:checkinto thetest_staticCircleCI job. It fails when a conformance report changes without its rollup being regenerated, and when a report rates a criterion ⚙️ Automated without citing the test or axe rule that proves it — the check that caughtLinearProgress1.4.1 claiming automation with nothing behind it.