Automated scans
Tools like axe check the code against rules: missing labels, low contrast, elements you can’t reach by keyboard. Fast and repeatable, but they only catch what a rule can express, and they can’t say who is affected.
An audit tells you whether your code meets WCAG. It can’t tell you whether people using a keyboard or large text actually finish checkout. Accessibility analytics measures that from real usage, by comparing people who use accessibility settings with people who don’t. This guide covers what you can measure, what you can’t and shouldn’t, and how to read the numbers.
| Setting | Attempts | Success | Gap |
|---|---|---|---|
| No accessibility settings | 4,410 | 71% | — |
| Reduced motion | 236 | 70% | −1 |
| Large text | 448 | 58% | −13 |
| Keyboard navigation | 342 | 38% | −33 |
People using keyboard navigation finish checkout at about half the rate of people using no accessibility settings: 38%, down from 69% before v4.12, when Tab started skipping the “Pay now” button.
Each answers a different question. None of them replaces the others.
Tools like axe check the code against rules: missing labels, low contrast, elements you can’t reach by keyboard. Fast and repeatable, but they only catch what a rule can express, and they can’t say who is affected.
An expert audit maps the product against WCAG. Testing with disabled people shows why something is hard. Both are essential, and both are snapshots of a product that keeps changing.
Real usage, every day, split by accessibility setting. It answers how many people fall behind, where, how much it costs and whether the last release made it better or worse.
Browsers and operating systems expose the settings people choose: larger text, reduced motion, high contrast. Some behaviour, like navigating by keyboard, can be observed directly. Those are the raw material.
What you can’t measure is disability, and you shouldn’t try. Plenty of people use large text because their phone is small, and plenty of disabled people use no setting at all. Settings tell you how someone is using your product, which is what a fix needs to know.
| Setting | Where | How it’s detected |
|---|---|---|
| Keyboard navigation | Web, iOS, Android | Web: five Tab presses, once Tab outnumbers pointer presses. iOS: a hardware keyboard or Switch Control. Android: a hardware keyboard or Switch Access |
| Zoomed in | Web | Page pinch-zoomed past 105% |
| Large text | Web, mobile | Browser default font above 16px; system text size above the default |
| High contrast | Web, mobile | prefers-contrast, or the system setting |
| Forced colours | Web | forced-colors: active, such as Windows contrast themes |
| Reduced motion | Web, mobile | prefers-reduced-motion, or the system setting |
| Inverted colours | Web, mobile | A media query, or the system setting |
| Reduced transparency | Web, iOS | A media query, or the system setting |
| Bold text | Mobile | The system setting |
| Greyscale | iOS | The system setting |
| Screen reader | iOS and Android apps only | VoiceOver and TalkBack state. Browsers don’t expose it |
Browsers deliberately hide whether a screen reader is running, because exposing it would single out disabled visitors. Don’t try to infer it. Sustained keyboard navigation on the web covers many people using a screen reader and many who don’t use one.
An accessibility gap is a difference between groups, so the comparison matters more than any single number.
Choose something with a clear start and finish that matters to the business: sign up, check out, book, finish onboarding. Give it a time window, like 30 minutes.
Measure success rate and time on task for each setting, and for people using no accessibility settings. Compare each group with them, not with the overall average, which already includes the groups you’re testing.
A handful of attempts is noise. By default Metrickle won’t give a verdict on a group until 15 different people have tried, judges small groups with an exact test so only an unmistakable gap turns red, and shows the count so nobody reads too much into a small one.
Filter the funnel to the group that falls behind. The step where their drop-off departs from that of people using none is where the barrier is. Friction hotspots on that step usually name the element.
Read barrier reports from that page, and show a one-question survey only to people with that setting. Ask about the task, never about disability.
Accessibility numbers get quoted in planning meetings and sometimes in legal correspondence, so they need to survive scrutiny.
| Setting | Attempts | Result |
|---|---|---|
| Reduced motion | 236 | No gap |
| Large text | 448 | Early signal |
| Forced colours | 12 | Too few attempts |
| Keyboard navigation | 342 | Gap found |
Forced colours has 12 attempts. It isn’t green. By default it stays unjudged until 15 different people have tried.
Backlogs are ordered by impact, and accessibility work often loses that argument because nobody has the number. The gap gives you one.
Say 1,000 people using keyboard navigation start checkout each month, and 40% finish against 70% of people using no accessibility settings. Closing the gap is worth about 300 orders a month. At a £42 average order, that’s roughly £12,600 a month: a number a product manager can weigh against anything else on the list.
Regulation adds to it. The European Accessibility Act has applied to many consumer products and services since June 2025, and the ADA and Section 508 apply in the US. Evidence of how disabled people actually get through your product, release after release, is stronger than a single audit PDF. Ask your legal advisers what you need for your situation.
Scanners produce long lists, and teams struggle to know which violation matters. Analytics produces gaps, and teams struggle to know which line of code causes them. Put them together and both problems shrink.
Metrickle accepts axe-core results uploaded from CI and attaches each violation to the page and element it was found on. When a friction hotspot and a violation land on the same element, the violation comes with a count of the people it’s stopping.
| Evidence | Detail |
|---|---|
| Friction | div.due-day dead clicks in 1,140 sessions |
| Who | People using keyboard navigation abandon here 3.4× as often as people using no accessibility settings |
| Scan | Serious: element is clickable but not focusable (WCAG 2.1.1) |
| Feedback | 2 reports: “Can’t pick a due date without a mouse” |
The scan found the bug. The analytics priced it. Same element, four kinds of evidence, one issue.
Record the settings a device reports. Don’t add questions, sign-up fields or surveys that ask people to disclose.
Use settings for breakdowns and filters, the way you’d use device type. Don’t build audiences or target marketing at them.
If your privacy policy needs it, Metrickle’s web SDK takes a11y: false. Cookieless mode records settings with nothing stored on the device.
Measuring how well people using accessibility settings, such as keyboard navigation, zoom, large text or a screen reader (in your iOS and Android apps), get through your product compared with people using none. It uses ordinary analytics events with the device’s settings attached.
No, and you shouldn’t try. Browsers deliberately don’t expose it. Sustained keyboard navigation is a useful, honest proxy. Mobile apps can read the VoiceOver and TalkBack setting from the operating system.
It depends on the size of the gap, but a few dozen attempts per group is a sensible floor. By default Metrickle won’t give a verdict until 15 different people have tried, and keeps the group visibly unjudged until then. Below a few dozen, only a large gap can be told apart from chance. On low-traffic flows, look at a longer period.
Settings aren’t a record of health or disability, and Metrickle never infers why a setting is on. They can still feel personal, so treat them carefully: report in groups, don’t target individuals, and check your obligations with whoever advises you on privacy law.
No. An audit tells you what fails a standard. Testing with disabled people tells you why something is hard. Analytics tells you how many people fall behind, where, and whether a fix worked. Use all three.
Keyboard navigation and large text. They’re common, and they break the most layouts: unfocusable custom controls, and text that overflows or clips at bigger sizes.
Every event carries the device’s accessibility settings, with nothing to tag. Free to start.
Start free