How should a Shopify team measure accessibility progress?

Track confirmed issues by severity, affected template, owner, and status, plus the time from detection to verified repair. Report clean purchase-path coverage and regressions introduced by releases. Avoid relying on one score, because a high average can hide a single critical blocker. Progress means fewer blockers, faster verified fixes, and stable conformance over time.

Metrics that guide work

Count open critical and serious issues, repeated instances, overdue repairs, and regressions by release. Separate automated findings from manual keyboard and screen reader findings so the report does not imply coverage it did not perform.

Evidence behind the trend

Every closed issue should link to the original failure and passing rescan. Monthly summaries can then show what changed, who repaired it, and whether the same component failed again.