Find where keyboard and screen reader users get stuck, and show a buyer the claim proof.
Each step of a review keeps its accessibility tree, focus trace and what a screen reader would announce, checked against WCAG 2.2.
button "Send invitation"
heading level 1 "Team"Nothing about the invitation was announced.Every state is captured, even brief ones.
That includes the message that showed for 3 seconds and the menu that opened on focus.
Accessibility tree
What assistive technology receives at each step.
generic "Invitation sent to sam@demo-target.test." (no role, no live region; removed after 3000 ms)
Transcript
What a screen reader would say, built from the tree and the focus trace. It isn’t a real screen reader.
button "Send invitation" heading level 1 "Team" (Nothing about the invitation was announced.)
Rule output
axe and Variantly’s own rules, run over the whole capture.
status-messages 4.1.3 #invite-flash no role="status"
Grouped by component
Issues are grouped by the component that causes them, so one fix closes many.
#invite-flash 2 issues · 1 component
Who gets shut out, step by step.
Name a keyboard-only or screen-reader perspective and it works through the task the same way. Where it can’t reach a control or never hears a result, that step is marked in Blueline with its WCAG criterion.
A conformance report where every row shows its source.
When a customer asks for a VPAT, the same captures set the report: VPAT® 2.5 and OpenACR, on a public permalink with version history. Every row says how it was set and by whom.
Every row links its evidence.
- Set by
- A person, with the evidence open
- Evidence
- capture · step 5 · transcript · focus trace
- Rows, each with its source
- 56
- 44 set by a person, 11 proposed by AI and confirmed by a person, and 1 by a rule.
- Supports
- 9
- 6 set by a person who opened the evidence, and 3 proposed by AI and confirmed by a person.
Counts from Ledgerly’s published report, a demo product’s. The other 47 rows are Not applicable. Variantly makes no pass-or-fail claim about a product.
Kept current.
Starter and Team recordings run again every night; ACR only, once a month. When a recording changes, the public page says so on each row that rests on it, and keeps its date.