Ouro HX's accessibility claims are checked by the project's own CI. This page lets anyone run the same checks, or open the CI run behind each one, without taking the project's word. It is generated from the repository's files, so a component with no screen-reader spec shows that here rather than being left out.
What this is not. The checks are run by the project that writes the components, and no outside auditor has reviewed them. An independent audit is separate evidence and is not claimed here; the model interviews record that compliance-minded models asked for exactly that.
The four checks
- axe on every story
- What it proves: No axe violation in any story, closed and with each overlay open. It runs in Chromium, leaves out Base UI's focus-trap guards (
test/story-axe.ts), and axe finds only part of what WCAG asks - Where it lives: test/stories.test.tsx
- CI runs: main's CI runs; open a run and read its browser shards
pnpm exec vitest run --project ouro-chromium test/stories.test.tsx- Conformance matrix
- What it proves: Focus handoff, announcements, right-to-left, forced colours and hydration hold for every story; an exemption is declared in the story and named in the pull request
- Where it lives: test/conformance/, guide
- CI runs: main's CI runs; open a run and read its conformance shards
pnpm conformance- VoiceOver on macOS
- What it proves: What the screen reader says for a control's name, role and state, driven by Guidepup. Some steps pass through documented fallbacks, and the macOS 15 and strict nightly jobs are advisory
- Where it lives: screen-reader specs, guide
- CI runs: push, nightly and release runs
pnpm test:sr --project voiceover(macOS only)- NVDA on Windows
- What it proves: The same specs, read by NVDA in Chromium
- Where it lives: the same specs
- CI runs: push, nightly and release runs
pnpm test:sr --project nvda(Windows only)
Some specs pass a step through a fallback or only log it, and the lane's advisory jobs do not fail the lane; the screen-reader lane's own page lists those and the other known findings recorded against VoiceOver and NVDA, with an issue for each: known findings.
Per component
Stories are counted as the export const entries of each component's *.stories.tsx files. Every one goes through the axe and conformance checks above. A screen-reader spec exists for 18 of 113 component folders; the rest are covered by axe and the conformance matrix only, and say so below.
- celebrate
- Stories: 2
- Conformance declarations: 0
- celebrate.sr.spec.ts: 1 test on
feedback-celebrate--in-context - checkbox
- Stories: 8
- Conformance declarations: 0
- checkbox.sr.spec.ts: 1 test on
forms-checkbox--playground - checklist
- Stories: 8
- Conformance declarations: 0
- checklist.sr.spec.ts: 1 test on
lists-checklist--in-context - color-scheme-toggle
- Stories: 3
- Conformance declarations: 0
- color-scheme-toggle.sr.spec.ts: 1 test on
actions-colorschemetoggle--segmented - dialog
- Stories: 14
- Conformance declarations: 0
- dialog.sr.spec.ts: 1 test on
overlays-dialog--playground - reorderable
- Stories: 4
- Conformance declarations: 0
- reorderable.sr.spec.ts: 1 test on
lists-reorderable--disabled - route-progress
- Stories: 2
- Conformance declarations: 0
- route-progress.sr.spec.ts: 1 test on
feedback-routeprogress--in-context - sync-status
- Stories: 3
- Conformance declarations: 0
- sync-status.sr.spec.ts: 1 test on
feedback-syncstatus--in-context - text-field
- Stories: 10
- Conformance declarations: 0
- text-field.sr.spec.ts: 2 tests on
forms-textfield--states,forms-form--server-errors
Screen-reader specs that cover a pattern rather than one component:
- patterns.sr.spec.ts: a row is heard by its title, its entry's heading as the detail takes the list's place, and the row again after Back; a search that finds nothing says so; its chart and its table's scrolling region are heard by their names
What each screen-reader test says it proves
The test titles, in the words of the specs, so a reader sees the claim before opening the file.
- button
- Button is announced with its name and role, and its busy state from the live region when loading turns on
- celebrate
- Celebrate says its message once when the last task is ticked
- checkbox
- Checkbox is announced with its name, role and state, and its change when checked
- checklist
- Checklist announces an item's name, role and state, and its change when ticked
- color-scheme-toggle
- ColorSchemeToggle is announced as a radio group of schemes, and the scheme chosen with the arrow keys as checked
- command
- Command reads each command the arrow keys reach from the search, which keeps focus
- dialog
- Dialog is announced with its title and role when it opens, and its trigger again when it closes
- item
- An Item with href is heard as a link by its title, then its description
- menu
- Menu is announced from its trigger, reads each item the arrow keys reach, and returns to the trigger on Escape
- reorderable
- A disabled Reorderable's handles are heard as unavailable buttons, without the pick-up instructions
- route-progress
- RouteProgress is announced once from its status region when a navigation starts
- select
- Select is announced with its label, role and state, and its new value when one is chosen
- switch
- Switch is announced with its name, role and state, and its change when turned on
- sync-status
- SyncStatus is heard when the connection goes, and when changes are saved again
- tabs
- Tabs that are links are announced as links, the current one as the current page
- text-field
- TextField is announced with its label, role and required state, and its description - TextField's error from a submit is announced as focus moves to the field
- timer
- Timer's Start is heard in its named group, and the time being up is announced once
- toast
- Toast is announced from its live region when it appears
Rerun it
- Clone the repository and run
pnpm i. - Run
pnpm exec vitest run --project ouro-chromium test/stories.test.tsxfor axe, andpnpm conformancefor the matrix. - On macOS or Windows, run
pnpm test:sr --project voiceoveror--project nvdafor the screen-reader lane; the guide lists what the runner needs. - To read a CI result without running anything, open a run from the links above and read the job's result and log.
This page is rendered by scripts/a11y-evidence/page.mjs; pnpm claims:check renders it again and compares, so it cannot drift from the files it counts.

