Solution
Assistive tooling for people who cannot complete a visual challenge. Audio and OCR paths are first-class here, not an afterthought bolted on.
Who this is for
Assistive-technology vendors, accessibility consultancies, disability organisations, and individual blind and low-vision users running a browser extension. The integration is usually a userscript or an extension that watches for a challenge and hands back an answer the user submits. Screen-reader users carry the cost of a failure, so latency here is a usability number.
The problem
Audio captcha fails for blind users at a rate near 46 percent in the Towson University study, and screen readers routinely talk over the audio track, so the WCAG-sanctioned accessible alternative often is not usable. CAPTCHAs rank among the most problematic page elements in the WebAIM screen-reader survey. In practice a form a sighted user clears in four seconds takes minutes, or does not get cleared at all.
Works with
[ 04 ]Questions about this one
Assistive-technology products and the people who use them, plus accessibility teams testing their own forms. It is the one scenario where the person solving the challenge is the person the challenge was shown to.
Because it fails often for the users it exists for, and screen readers frequently play over it. Where audio is the only path a site offers, we take the audio file directly and return the transcription.
Inside the widget’s own timeout, which for reCAPTCHA audio is roughly two minutes. Each type page publishes P50 and P95, so you can check the margin before shipping.
The two types this scenario needs most, audio and image-to-text, are already in the lowest-priced band on the rate card. Non-profit assistive-technology projects can write to us about volume terms.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.
