Skip to Content

Blog > Measuring What Matters

Measuring What Matters

Karl Groves. - 29/04/2026

How to Turn Accessibility Work Into Evidence-Based Progress

Digital accessibility programs often begin with good intentions: an audit, a backlog of issues, a remediation plan, maybe a few training sessions. But sooner or later, leadership asks a harder question:

Are we actually getting better?

For many organizations, that question is difficult to answer. Accessibility work is often tracked inconsistently, reported anecdotally, or treated as a compliance exercise rather than a measurable business and user experience discipline. Teams may know they are fixing issues, but they struggle to show whether risk is decreasing, whether defects are being prevented, or whether accessibility is becoming part of normal operations.

That is the problem addressed in AFixt’s white paper, Measuring What Matters: A Practitioner’s Guide to Tracking Accessibility Metrics Using Issue Tracking Data and the W3C Accessibility Maturity Model.  

Why accessibility metrics matter

Accessibility cannot mature if it cannot be measured.

Without clear metrics, organizations often rely on snapshots: a single audit result, a list of open defects, or a general statement that accessibility is “important.” Those snapshots may be useful, but they do not show whether accessibility is improving over time.

The white paper explains how organizations can move beyond anecdotal reporting by using data they already have in issue tracking systems such as Jira. With the right structure, accessibility defects can become a source of program intelligence: severity trends, resolution rates, affected user groups, recurring WCAG failures, component-level risk, testing coverage, and more.

What the white paper covers

This guide is designed for accessibility leaders, product teams, engineering managers, compliance teams, and executives who need a practical way to connect accessibility activity to measurable outcomes.

Inside the white paper, you will learn how to:

  • Use the W3C Accessibility Maturity Model as a framework for measuring organizational progress.
  • Structure Jira to capture accessibility-specific data, including WCAG success criteria, severity, affected user groups, discovery methods, remediation complexity, and testing status.
  • Build accessibility workflows that track issues from discovery through verified resolution.
  • Create metrics that map to maturity across development, culture, leadership, knowledge, support, procurement, communications, and personnel.
  • Use ready-to-adapt JQL queries for executive dashboards, development team views, program management, and compliance reporting.
  • Build stakeholder-specific dashboards for executives, developers, accessibility program managers, and compliance teams.
  • Automate metric collection through Jira automation, CI/CD integrations, scheduled reporting, and stakeholder communications.
  • Avoid common measurement pitfalls such as vanity metrics, over-reporting, excessive deferral, and confusing test coverage with actual accessibility.

From defect tracking to maturity tracking

Most organizations already have accessibility data. The problem is that the data is often not structured in a way that supports decision-making.

A Jira backlog full of accessibility bugs can tell you what is broken. A properly configured accessibility metrics system can tell you much more:

  • Which types of issues are recurring?
  • Which teams or components need additional support?
  • Are critical issues being resolved fast enough?
  • Are new defects being prevented?
  • Are user-reported barriers decreasing?
  • Is accessibility being integrated into the development lifecycle?
  • Can leadership see measurable progress quarter over quarter?

The white paper shows how to answer those questions using practical configurations, dashboard designs, and reporting patterns.

Who should download it

This white paper is especially useful for organizations that:

  • Have completed accessibility audits but struggle to track remediation progress.
  • Use Jira or another issue tracking system to manage accessibility defects.
  • Need better executive reporting on accessibility risk and progress.
  • Want to align accessibility work with the W3C Accessibility Maturity Model.
  • Are trying to move from reactive remediation to proactive accessibility governance.
  • Need defensible proof points for compliance, procurement, leadership, or maturity reviews.

Download the white paper

Accessibility maturity requires more than fixing defects. It requires evidence, structure, accountability, and continuous improvement. Download Measuring What Matters to learn how to turn accessibility issue tracking data into meaningful metrics, executive dashboards, and maturity proof points.

This field is for validation purposes and should be left unchanged.
Name(Required)
Subscribe

Related Blog Posts

The major technical reasons why accessibility overlays don’t work

The Overlay Factsheet describes an accessibility overlay as follows: The fundamental constraint you will notice as you dive into the details below is that post-rendered remediation is working against the framework, not with it. React (and similar frameworks) own the DOM. The framework expects to be the single source of truth for element structure, attributes, […]

Karl Groves - 10/04/2026

VPAT Quality: How to Spot a VPAT That Wasn’t Properly Tested

A VPAT that claims “Supports” across the board is a red flag, not a success. I’ve reviewed hundreds of VPATs—Voluntary Product Accessibility Templates—over the years, and the pattern is unmistakable: many are filed without substantive testing. Organizations create them to satisfy procurement…

Karl Groves - 07/04/2026

Beware of “AI” accessibility audits

And, even moreso: beware of companies who sell them. I performed my first professional accessibility audit in 2006. Since that time, I’ve performed hundreds of accessibility audits for everything from small websites to massive standalone kiosks in Manhattan. I’ve done audits for small one-person e-commerce stores and massive software companies like Google, Adobe, Microsoft, and […]

Karl Groves - 27/03/2026

Introducing AFixt Accessibility Program Management

A Complete Solution Built on the W3C Accessibility Maturity Model Being successful in accessibility isn’t a one-off project. Like all compliance domains, it’s an organizational capability that must be built, measured, and sustained across every function of a business, ranging from how you recruit employees to how you procure software and from how your developers […]

Karl Groves - 20/03/2026

What I Like About WCAG 3.0

The W3C published an updated Working Draft of WCAG 3.0 on September 4, 2025, and I’ve spent considerable time pulling it apart. The accessibility community has been tracking this specification since the first public working draft dropped in January 2021, and after years of watching the sausage get made this latest draft finally feels like […]

Karl Groves - 03/03/2026