Find what gets in the way of using your product.
Variantly tries your product’s important tasks in a browser, from the perspective you describe, and keeps every screen. Usability and accessibility findings sit on the same evidence; a person decides what to act on.
Private, accessibility only, public pages only. It doesn’t sign in or publish anything.
Automated checks find some accessibility issues on the pages captured. A clean scan does not establish accessibility conformance. Review the evidence and scope before relying on a report. How accessibility evidence is reviewed.
Exhibit · Invite a teammate · step 5 of 7
Follow one task from what you meant to what happened.
You describe the task and how you’d know it worked. An attempt tries it from the perspective you describe. Each finding keeps the screens it rests on, a person’s decision and a recheck after a change. In the product this is called a task review.
Static version: all five parts of the record, in reading order.
1 · The intended result
- The task
- Invite a teammate with the right access.
- Who is trying
- New administratorFirst week with the product· assumedSigns in as admin· test account
- How you’d know it worked
- “sam@demo-target.test” appears in “Invitations waiting for a reply”.Checks: words appear in a list on screen. Doesn’t check: that the email arrives.
2 · What the attempt did
Sample result: “Invitations waiting for a reply” check: seen in 2 of 2 attempts as New administrator.
- 01Opened Team.
- 02Typed sam@demo-target.test into Email address.
- 03Left Role as Member.
- 04Pressed Send invitation.
- 05Saw “Invitation sent to sam@demo-target.test.”Flagged: a finding rests on this step.
- 06On the next screen, the message was gone.Flagged: a finding rests on this step.
- 07Reloaded. The invitation is listed as Pending.
Attempts are counted, never averaged. In this example, the task completed; the feedback along the way is what the findings are about.
3 · The evidence kept for step 5
<div id="invite-flash" class="ok"> Invitation sent to sam@demo-target.test. </div> <!-- removed after 3000 ms; no role="status" -->
button, Send invitation (page loads) heading level 1, Team: Ledgerly demo — no announcement of the confirmation —
Each step keeps its screenshot, accessibility tree, focus trace and virtual screen-reader transcript. Both findings link here.
4 · A person’s decision
A person decides each usability finding with its evidence open, and says why. The choices are:
The accessibility finding comes from rule checks and isn’t decided here. A usability decision never sets a report row.
5 · Follow-up after a change
A recheck tries the same condition again, with the same perspective and test account, and keeps the original record beside the new one.
- Seen
- The condition appeared again.
- Not seen
- It didn’t appear on the same path.
- Couldn’t tell
- The evidence doesn’t settle it.
- Not checked
- The attempt stopped first.
This example has no recheck yet. A recheck shows how the interface behaves after the change. Whether people understand it needs research with people.
Every statement carries its mark.
A rule, the AI and a person say different things about the same screen. Each kind keeps its own mark wherever a finding appears, and so does what nobody has established.
Where the record goes.
- A task reviewIn your workspace
Findings for one task, in counts, with what the review didn’t cover. Each finding opens to its screens. Read an example review.
- A brief for engineersPaste into a ticket
The finding, evidence links, the proposed change and the recheck condition, written for a person or a coding agent.
- An accessibility conformance reportWhen a buyer asks
An ACR in VPAT® 2.5 and OpenACR formats, scoped and dated, on a public permalink. Its rows come from scoped accessibility scans and recorded journey replays, never from task-review findings.
Start free. Pay monthly or yearly, or buy the report on its own.
Starter and Team include the accessibility conformance report when billed yearly. Billed monthly, switch to yearly billing to get it.
- Free checkFree
Accessibility results for your public pages, private to you.
- Starter$100/month
Or $1,000/year, billed yearly: two months free, save $200. One product, an included usage allowance, and the accessibility conformance report when billed yearly.
- Team$300/month
Or $3,000/year, billed yearly: two months free, save $600. Multiple products, a larger shared usage allowance, and the accessibility conformance report when billed yearly.
- Report only$800 once
Without a subscription: an ACR in VPAT® 2.5 and OpenACR formats, scoped and dated. Optional renewal $500/year. Included in Starter and Team billed yearly.
- sign in
- submit forms
- attempt tasks
- publish a report
Colophon
Built by
Adam Stankiewicz
Founder and builder
Adam works across product engineering, design systems and accessibility. He has led accessibility and design-system work on education products, including seven years leading an open-source design system for an online learning platform. His research background spans human–computer interaction (HCI), computer-supported cooperative work (CSCW) and learning at scale.
Questions, feedback and corrections are welcome. Write to adam@variantly.app
- Set in
- Charis SIL and Geist
- Standard
- Built to WCAG 2.2 AA. If you find a failure on this page, it is ours to print.
- Evidence on this page
- Example screen, redrawn from a demo product. No review was performed.
- Access and data
- How we handle product access and evidence
Variantly · Your frontend, on the record. VPAT® is a registered trademark of ITI. An ACR documents conformance on a date; it is not a certification.