Repository navigation
Accessibility conformance results for Radix Primitives, ahead of publication (all checks pass) #4170
Replies: 1 comment
|
Would it help to include a coverage-change summary beside each version comparison? The scoring rules already exclude errors and block publication when they occur. For the repeated runs described here, I would also make any discarded assertion visible by ID and reason, rather than letting a smaller evaluated set look like an unchanged result. A compact comparison could separate:
Pinning the adapter and spec revisions beside those groups would help distinguish a component regression from a changed test or fixture. A synthetic case where one previously passing assertion becomes inconsistent would be a useful acceptance check: the report should expose the lost coverage even if the remaining checks all pass. This is a reporting suggestion based on the discussion and scoring documentation, not an independent validation of the results. AI-assisted drafting. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I run Railing, an open source project that tests React component libraries against the W3C ARIA Authoring Practices Guide and publishes the results. Radix Primitives is one of the seven libraries measured, and you are hearing about it before anything is public.
The short version: Radix passes every check we run. 50 assertions across four components, each citing an APG clause or WCAG success criterion, run three times and discarded if any result varies.
@radix-ui/react-dialog@1.1.23@radix-ui/react-dropdown-menu@2.1.19@radix-ui/react-tabs@1.1.14@radix-ui/react-accordion@1.2.20Components were mounted with default configuration, following your documentation, with no focus management, ARIA attributes or key handlers added by our adapter. The adapter is about fifty lines and is included in the full report below, so you can check we mounted things the way you would recommend.
Why tell you at all? Three reasons:
Everything is reproducible from a clone, and every run has a replayable Playwright trace:
How the measurement works: railing.dev/method · scoring · disclosure policy · source
Full report
Accessibility conformance results for Radix UI
You are hearing this before we publish anything. No score for Radix UI is on our index, and none will be for at least fourteen days, whatever this report says.
Railing runs component libraries against the W3C ARIA Authoring Practices Guide and publishes the results. Every check cites the clause it measures, every score names an exact version, and every result is run repeatedly and discarded if the answer changes.
The short version
We found nothing to report. Radix UI passes every check we run. We are telling you anyway, because you should hear about a public score from us rather than find it, and because you may still think we measured something wrongly.
How we tested it
Reproduce any of it from a clone of the repository:
Where we might be wrong
The most likely cause of a wrong result is our adapter, not your library.
We have got this wrong repeatedly. One library's first run scored 27% and almost all of it was a selector of ours. Another was reported as having a broken focus trap when the trap worked and our test was reading focus too early.
So the adapter source is included below. Please tell us if we mounted your component in a way you would not recommend, or if a check misreads the specification. We will correct it and, if it has already been published, correct that too.
Where to check us
What happens next
The adapter we used
This is the whole of the library-specific code. There is nothing else.
accordion.tsxdialog.tsxmenu.tsxtabs.tsxThanks for building primitives careful enough that this was the easiest report of the seven to write.
Aman
All reactions