Services · Testing types
Can Your Site Be Driven by Voice?
For the team that wants the site obeying people who click by speaking, through Voice Control on a Mac or Dragon and Voice Access on Windows.
What We Keep Finding
Voice users drive the web by saying what they see. "Click Send", and the software looks for a control named Send and clicks it. Now the failure. Your button shows Send, and its coded name is "submit-btn-2". The user says the only name they can see, and nothing happens. They say it again. Louder does not help.
WCAG calls this label in name, rule 2.5.3, and the shape of it is containment rather than an exact match. The words on the control have to live inside its coded name. So a button showing Send whose name is "Send message" passes, and the same button named "Submit" fails. It is one of the easiest rules to break with a well-meant aria-label. A scanner can compare the two strings, and the engine behind our free scan carries a rule that does exactly that. What string comparison cannot tell you is whether the mismatch actually breaks a spoken command in your product, which is the part we test by speaking, on Voice Control and Dragon at the desktop.
Icon-only buttons are the hotspot, and they need a word of care, because half the findings people write against them are misfiled. The rule only reaches controls that show text or an image of text, so a bare icon with no characters sits outside it entirely, and its failures belong to the name-and-role rule or the alt-text rule instead. Even a letter on an icon usually does not count, because a B on a text editor's bold button is a symbol rather than words, and W3C says the right accessible name there is Bold. We file each of those where it belongs rather than sweeping them all under one rule number.
What We Check
- Speak every visible label and confirm the right control responds
- Compare each coded name against the text a user can actually see
- Test icon-only buttons, where voice input breaks and findings get misfiled
- Try the show-numbers fallback, the workaround users should not need
- File each miss under the rule it actually breaks, with the one-line fix beside it
What You Get
Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.
The format is not a mystery either. Read the sample report before you spend anything.
The Honest Limit
One honest limit. Our voice pass is desktop-based, on Voice Control and Dragon, and Windows now ships Voice Access built in, which we can name in scoping if that is what your audience runs. Phone assistants lean on the same accessible names for the most part, so most of what we find carries over, and we only claim the coverage we actually ran. The report names the software and the version, so a finding can be reproduced rather than argued about.
What It Costs
Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.
Worth Reading Next
Related on this site
Guides, checklists, tools, and terms that go with this service.