Every finding in the Dev Tool has a severity: error or warning. Severity indicates how critical the issue is and whether it typically affects conformance. The panel uses it for filtering, counts, and badges so you can prioritize what to fix first.
The two severity levels
Error — Failures that violate the rule and must be fixed for conformance. In the panel they appear with an error badge and are counted as “Errors.” Examples include missing alternative text, insufficient color contrast, or keyboard traps.
Warning — Issues that are recommended to fix or need manual review. They appear with a warning badge and are counted as “Warnings.” The audit reports these so you can improve accessibility and catch edge cases that automated rules can’t fully judge.
Using severity in the panel
The Dev Tool shows total error and warning counts (e.g. “12 Errors, 5 Warnings”). Use the severity filter to show all findings, only errors, or only warnings. Each finding row shows a severity badge (error or warning) plus the rule ID, message, and fix guidance so you can address errors first, then warnings.
For the TypeScript type and how severity appears in programmatic audit results, see the TypeScript page (e.g. AccessKitSeverity, AccessKitAuditFinding.severity).