Put a number on every accessibility barrier
Every event Metrickle records carries the accessibility settings seen on the device. Compare any task, funnel or journey with people using no accessibility settings, and take evidence to the backlog instead of a hunch.
| Setting | Chart | Success | Median time |
|---|---|---|---|
| No accessibility settings | 78% | 1m 31s | |
| Reduced motion | 76% | 1m 35s | |
| Zoomed in | 64% | 2m 20s | |
| Large text | 61% | 2m 07s | |
| Keyboard navigation | 44% | 3m 02s |
People using keyboard navigation are the furthest behind: 44% succeed, 34 points below people using no accessibility settings, and those who finish take twice as long.
From “is this accessible?” to an issue with numbers
A walkthrough on Quillmere, a fictional invoicing app with sample data. The same views work on your own apps from the first day of data, with nothing to set up beyond the script tag or SDK.
Compare
Open any task or funnel and split it by accessibility setting. Success rate, time on task and drop-off sit next to people using no accessibility settings.
Locate
Filter the friction report and journeys to the group that falls behind. The dead clicks, u-turns and form errors they hit are ranked by element and page.
Confirm
Read the accessibility barrier reports from the same page, ask a one-question survey shown only to that group, and watch consented replays of the attempts that failed.
Device settings on every event, with nothing to tag
The script tag and the mobile SDKs read the settings people already use and attach them to every event. On the web that means sustained keyboard navigation, zoom, large text, high contrast, forced colours, reduced motion, reduced transparency and inverted colours. In your iOS and Android apps it adds bold text, greyscale and the screen reader.
Browsers deliberately hide whether a screen reader is running, so the web reports keyboard navigation instead. The mobile SDKs read the real screen reader setting from the operating system.
Keyboard navigation counts once a session has five Tab presses and they outnumber pointer presses. Zoomed in means pinch-zoomed past 105%. Large text means a default font size above 16px on the web, or a system font scale above 115% on mobile.
- Settings, not diagnoses: Metrickle sees that large text is on, never why. Nobody is asked anything and nobody has to disclose anything. If your policy needs it, pass
a11y: falseto the web SDK to switch capture off. - Stored like device type: a short list of flags per event, used for filters and breakdowns. Sessions with no flags form the “No accessibility settings” group that every other setting is compared with.
- One filter everywhere: tasks, funnels, friction, journeys, surveys and replays all split by the same setting.
| Setting | Sessions | Friction | Conversion |
|---|---|---|---|
| No accessibility settings | 41,730 | 12% | 9.4% |
| Bold text | 3,115 | 14% | 8.9% |
| Large text | 4,480 | 21% | 6.8% |
| Screen reader | 1,262 | 33% | 4.1% |
Sessions with a screen reader convert at less than half the rate of sessions with no accessibility settings, and a third of them hit friction on the way.
Find the step that fails one group and not the others
A barrier often hides inside a healthy average. Filter a funnel to one setting and the biggest drop-off callout moves to the step that group can’t get past, even when everyone else gets through it fine.
Put the two numbers side by side and you have the cost of the barrier in lost sign-ups, orders or bookings. That is usually what moves an accessibility fix up the backlog.
- Funnels and tasks by setting, with drop-off, median time per step and where abandoned attempts stopped.
- Journeys filtered to one setting, to see where people go when the intended path fails.
- Heatmaps come with a text summary and data tables, so the evidence itself is readable with a screen reader.
Biggest drop-off: Line items → Due date (−38%)
The due-date picker loses people using keyboard navigation. People using no accessibility settings lose 6% at the same step. The top hotspot is a dead click on the calendar grid.
Let people report barriers, and ask the right group
The always-on “report a problem” widget has an accessibility barrier category. Reports arrive in a triage inbox with the page, device, app version and settings attached, plus an optional screenshot that people can highlight or partly hide before sending.
Surveys can target accessibility settings, so you can ask people using keyboard navigation or large text one question on the step that fails them, without asking anyone about disability. Answers are events, so they become filters on funnels and replays.
- Designed for WCAG 2.2 AA: the survey and feedback UI uses native controls, visible focus, 44px targets and supports forced colours and reduced motion.
- Web and mobile: surveys and feedback run everywhere, with a built-in accessible survey sheet on iOS, Android and Flutter. Heatmaps and replay are web-only for now.
| Report and page | Setting |
|---|---|
“Can’t pick a due date without a mouse” /invoices/new | Keyboard navigation |
“The total covers the Send button when text is bigger” /invoices/new | Large text |
“Selected template isn’t visible” /settings/templates | Forced colours |
Two reports name the due-date picker the funnel flagged. Each arrives with page, device, app version and settings, so it’s ready to file.
Everything you need to make the case
Accessibility is a filter on the whole product, not a separate report. It doesn’t replace an audit or research with disabled people: it shows where real people fall behind and what that costs, so you can choose what to fix first and prove the fix worked. These are the pieces you’ll use most.
Tasks and research
Success rate, median time on task, how long the slowest 10% take, and where abandoned attempts stop, for any setting.
Funnels
Drop-off per step and the biggest drop-off for each setting, so you can price a barrier in conversions.
Friction report
Rage, dead and error clicks, u-turns and form errors, with friction and conversion rate per setting.
Targeted surveys
Show a question only to people with a given setting, on the page where they struggle.
Heatmaps and replay
Replays filter by setting. Heatmaps include a text summary and data tables. From Growth.
Barriers reach the team
Accessibility barrier reports go to Slack or Teams with the reporter’s settings, and become issues measured after the fix.
AI assistants (MCP)
Ask an AI assistant over MCP which checkout step loses the most people using keyboard navigation.
Make the business case
The evidence that accessibility barriers cost conversions, with sources and a calculator for your own estimate.
See which release is costing you conversions, and who it broke for
Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.
Start free