The Dev Tool runs automated checks based on the Web Content Accessibility Guidelines (WCAG). By default it uses success criteria from WCAG 2.0, 2.1, and 2.2 at Level A, Level AA, and Level AAA. Each finding is tied to a specific criterion (e.g. “WCAG 1.1.1”) and, when applicable, to a conformance level so you can see what you need to fix for a given target (e.g. AA).
Conformance levels (A, AA, AAA)
WCAG defines three levels of conformance:
- Level A — Minimum requirements. Failures affect many users and must be fixed for any claim of conformance.
- Level AA — Common target for legal and policy requirements. Addresses the most common barriers.
- Level AAA — Strongest level. Often used for critical content or when you want to go beyond AA.
The Dev Tool shows the level next to each finding when the rule maps to a WCAG success criterion (e.g. “WCAG 1.1.1 (A)” or “WCAG 1.4.3 (AA)”). That lets you prioritize Level A and AA first if you’re aiming for AA compliance, and treat AAA findings as enhancements.
Rule IDs and what they mean
Each finding includes a rule ID (e.g. “WCAG 1.1.1”, “WCAG 2.4.7”). The number matches the WCAG success criterion (e.g. 1.1.1 Non-text Content, 2.4.7 Focus Visible). The panel shows this ID, the level when available, a short message, fix guidance, and a link to more documentation so you can resolve the issue and understand the requirement.
Filtering by WCAG level in the panel
Use the level filter in the Dev Tool to narrow results by conformance level. Choose “All” to see every finding, or “A”, “AA”, or “AAA” to see only findings for that level. “Other” shows findings that come from rule sets that don’t map to a WCAG level (e.g. best-practice or other standards you’ve enabled). Combining the level filter with the severity filter (errors vs. warnings) helps you focus on the issues that matter most for your target level.
Default rules and additional rule sets
Out of the box, the Dev Tool runs WCAG 2.0, 2.1, and 2.2 rules at Level A, AA, and AAA. You can enable extra rule sets (e.g. best-practice or Section 508) via the additionalRules option when you configure the Dev Tool. Those findings may show a rule ID and category but no WCAG level; they still appear in the list and can be filtered with “Other” for level. For configuration details, see Configuration.
For the TypeScript type used for levels (e.g. AccessKitWcagLevel) and how levels appear on findings, see the TypeScript page.