Yes. Accessibility compliance platforms can track issues by WCAG conformance level, organizing each finding under Level A, AA, or AAA. This lets teams filter, sort, and report on issues based on the level their organization is targeting, which for most projects is WCAG 2.1 AA or 2.2 AA. Conformance level is typically stored as a field on each issue, alongside the specific success criterion, page or screen location, severity, and status.
| Key Point | What It Means |
|---|---|
| Level Field | Each issue is tagged with its WCAG level (A, AA, or AAA) and its specific success criterion. |
| Filtering | Teams can view only Level A issues, only Level AA issues, or both, depending on the target standard. |
| Reporting | Progress reports and dashboards segment data by level, showing conformance status for each. |
| Target Standard | Most organizations track against 2.1 AA or 2.2 AA, which includes all Level A and AA criteria. |
How Software Tracks Issues by WCAG Level
When an audit report is loaded into a compliance platform, each identified issue carries metadata. That metadata includes the WCAG version (2.1 or 2.2), the conformance level (A or AA), the specific success criterion (such as 1.3.1 Info and Relationships), the location, severity, and remediation guidance.
The platform stores the level as a structured field. This makes filtering, sorting, and reporting on level a built-in capability rather than something the team has to build themselves in a spreadsheet.
Why Level Tracking Matters
Most organizations target WCAG 2.1 AA or 2.2 AA. Conformance at the AA level requires meeting all Level A and all Level AA success criteria. Tracking by level lets teams confirm they have addressed both groups, not one in isolation.
Level tracking also supports prioritization. Level A criteria represent the most fundamental requirements, and unresolved Level A issues carry the highest user impact and legal risk. Filtering by level surfaces these first.
Filtering and Views
Inside a platform, users can typically apply filters to issue lists and dashboards. Common filter options include:
- Level A only, to focus on the most fundamental criteria
- Level AA only, to review the additional criteria required for AA conformance
- Combined A and AA, the standard view for organizations targeting AA
- Open issues by level, to see what remains before AA conformance is reached
These views are useful during remediation sprints, where a team may want to clear all Level A issues before moving to Level AA work.
Reporting by Conformance Level
Progress reports and analytics dashboards segment data by level. A typical report shows the count of open and closed issues at each level, the percentage of criteria met, and the path remaining to full AA conformance. This is also how platforms feed data into VPAT and ACR generation, where each success criterion is documented with a conformance status.
For organizations managing multiple projects, level-based reporting also supports portfolio views. Leadership can see which products are close to AA conformance and which still have open Level A issues across the portfolio.
Level Tracking and Audit Data
Level tracking depends on the audit data feeding the platform. A complete audit identifies issues against specific WCAG success criteria, which means the level is inherent in the data. Scans alone produce partial data and flag only about 25% of issues, so platforms relying solely on scan output cannot give a complete picture of conformance at any level.
Audit-based tracking, where each finding is mapped to its success criterion and level by an evaluator, produces the data quality needed for accurate level reporting.
Limitations
Tracking by level is only as accurate as the underlying issue data. If issues are mislabeled or assigned to the wrong success criterion, the level filter will reflect that error. Quality control during audit ingestion matters.
Some platforms also model WCAG version differences (2.0, 2.1, 2.2) separately, so teams working across versions should confirm how the platform represents version alongside level.
Level tracking is a baseline capability for any platform built around WCAG-aligned accessibility platform features. Without it, conformance reporting becomes manual work that the platform was meant to replace.