Accessibility findings should behave like actionable engineering work.
If the report only says "WCAG failure" without explaining impact, reproduction, priority, and retest expectations, the team still has to do discovery before remediation can begin.
Severity helps reduce that friction.
Severity answers the remediation question
For developers and QA teams, severity should clarify:
- What should be fixed first?
- Which users are blocked?
- Which journey is affected?
- Is the issue repeated across a component?
- Does the fix need design, content, document, or vendor input?
- What evidence is needed for retesting?
Severity is not a replacement for WCAG mapping. It is a layer on top of the finding that explains priority.
Critical
A critical finding usually blocks a core task.
Examples:
- Focus gets trapped in a modal or menu.
- A screen reader cannot identify a primary action.
- A required field has no usable label or error relationship.
- A document required for a service cannot be read in logical order.
- A checkout, login, support, application, or account flow cannot be completed.
Critical issues need fast triage and manual retesting.
High
High findings create serious barriers in important experiences.
Examples:
- Incorrect accessible names on repeated controls.
- Broken focus order in a multi-step workflow.
- Form errors that appear visually but are not exposed programmatically.
- Important text or controls failing contrast requirements.
- One shared component causing failures across multiple templates.
High issues often belong in the next remediation sprint or release cycle.
Medium
Medium findings create real friction but may not fully block the task.
Examples include confusing headings, unclear link purpose, inconsistent keyboard behavior, incomplete image alternatives, or instructions that are present but not robust.
Do not ignore medium findings. Repeated medium issues can still create significant user frustration.
Low and advisory
Low issues often relate to polish, consistency, or lower-risk accessibility quality gaps.
Advisory items may not be direct failures. They can document improvements, future risks, or best-practice suggestions.
The important rule: do not use advisory labels to hide real accessibility defects.
What QA should retest
Severity should influence retesting depth.
Critical and high issues generally need manual verification. That may include keyboard testing, screen reader checks, state verification, screenshots, recordings, or PDF structure review.
For closure, the retest note should connect to the original finding and confirm the expected accessible behavior.
Conclusion
Severity labels are useful when they help teams prioritize, fix, and verify accessibility issues.
The best reports combine WCAG mapping, user impact, evidence, remediation guidance, and retest status. That is what turns an audit into delivery work.
Read the original guide on IAAP Audit: https://iaapaudit.com/blog/accessibility-audit-severity-levels-explained
Top comments (0)