Accessibility audits that hold up, handed over with confidence.
For solo auditors, small shops, and teams who need more than a scan report. Author the audit, log every finding, reuse your remediation, and give clients a WCAG compliance workspace they can act on.
Issues remaining
11 of 29
Issues closed
62%
- Critical 4
- Serious 5
- Warning 2
Try itVerify this fix.
“Apply” button has no accessible name
The client says it’s fixed. Your call.
Built around what scanners miss.
Where scanners stop
Automated tools catch a fraction of real WCAG issues. Everything above that ceiling requires a human — and a record that proves one was there.
Every verdict, attributed
Every verdict is timestamped and attributed to the auditor who made the call. Not a tool. Not a confidence score.
Built for both sides
Auditors get a full working record. Clients get a plain-language workspace. Same audit, the right context for each audience.
The whole audit, in one place.
Log
Every finding gets a verdict, your name, a timestamp, and your evidence. Exactly as you tested it.
Try itSet the verdict.
“Apply” button has no accessible name
4.1.2 Name, Role, Value · VoiceOver, Safari
Not logged yet. Your call.
Reuse
Your accessibility remediation library travels with you. Write it well once, insert it everywhere.
Try itSelect Insert to add a fix you’ve written before to this finding.
Remediation library
1 of 3 inserted
- Icon-only buttons need a name 4.1.2
- Visible focus indicator 2.4.7
- Announce form errors 3.3.1
Retest
When fixes come back, retest against the original finding. Every cycle stays on the record.
Try it The client has sent fixes back. Verify confirms the next one is fixed; Reject returns it.
Hand over
Clients get a live workspace, not a PDF. Every issue explains why it matters and how to fix it.
Try it You are the client here. Tell your auditor this issue is fixed and ready to retest.
“Apply” button has no accessible name
Why it matters. Screen reader users hear only “button”, so they can’t tell what it does.
How to fix it. Give the button a text label that says “Apply promo code”.
Defensibility.
When your work gets challenged, the question is whether you can show what was tested, who tested it, and what they found. Sauva produces that record — timestamped, attributed, and built on your judgment, not a WCAG audit tool’s output.
Try itOpen an entry to see what’s behind it.
Tested with VoiceOver in Safari. Expected to hear “Apply promo code, button”. Heard only “button”.
Arrows mark the unlabelled control and the VoiceOver caption panel showing what was announced.
Give the button a visible text label, or an aria-label that says what it does: “Apply promo code”.
Retested with the same setup. Heard “Apply promo code, button”. Snapshot saved when the cycle closed.
One finding, two views.
Your working record.
Selector, evidence, private notes, and the verdict — exactly as you logged it.
“Apply” button has no accessible name
button.promo-apply
Evidence
- promo-button.png
- screen-reader-output.png
Auditor-only note
Same pattern on the gift card form. Check the shared template.
Their place to learn.
The same finding, translated for the people who have to fix it. Clients stay informed without needing you on a call.
“Apply” button has no accessible name
Why it matters. Screen reader users hear only “button”, so they can’t tell what it does.
How to fix it. Give the button a text label that says “Apply promo code”.
Accessibility auditing software built for the work, not the report.
For solo auditors, small shops, and teams who need a complete audit record — not just a scan summary.