Metrickle

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.

Task: Send an invoicequillmere.example · last 30 days
Attempts9,862
Success rate74%
Median time1m 38s
Send an invoice: success rate and median time on task by accessibility setting, compared with people using no accessibility settings
SettingChartSuccessMedian time
No accessibility settings78%1m 31s
Reduced motion76%1m 35s
Zoomed in64%2m 20s
Large text61%2m 07s
Keyboard navigation44%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.

  1. 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.

  2. 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.

  3. 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: false to 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.
Friction and conversion by settingQuillmere for iOS · last 30 days
Sessions, share of sessions with friction, and conversion rate for each accessibility setting
SettingSessionsFrictionConversion
No accessibility settings41,73012%9.4%
Bold text3,11514%8.9%
Large text4,48021%6.8%
Screen reader1,26233%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.
Funnel: Send an invoice · Keyboard navigationquillmere.example · last 30 days
Entered1,120
Conversion44%
No accessibility settings78%
New invoice100%
Line items84%
Due date52%
Sent44%

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.

Start measuring barriers

Feedback: Accessibility barrierquillmere.example · last 30 days
Reports41
Accessibility12
With screenshot7
Recent accessibility barrier reports with the page they came from and the settings on the device
Report and pageSetting
“Can’t pick a due date without a mouse” /invoices/newKeyboard navigation
“The total covers the Send button when text is bigger” /invoices/newLarge text
“Selected template isn’t visible” /settings/templatesForced 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.

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