WCAG A, AA, and AAA: What Teams Should Scope

#a11y #wcag #digitalaccessibility #accessibilityaudit

When a team says "we need a WCAG audit", the next question should be:

Which version, which level, and which scope?

WCAG levels are cumulative. Level AA includes Level A and Level AA requirements. Level AAA includes A, AA, and AAA requirements.

That affects what gets tested and what appears in the report.

Why this matters for implementation

If the target level is unclear, engineering and QA teams can end up with ambiguous findings.

A report should say whether a defect maps to Level A, Level AA, or Level AAA. It should also explain whether AAA checks were part of formal scope or included only as advisory recommendations.

Level A: baseline access

Level A issues are often blockers.

Think about:

Keyboard access
Missing labels
Missing text alternatives
Broken structure
Blocking interaction patterns
Assistive technology incompatibility

These are not small polish issues. They can prevent task completion.

Level AA: common audit target

AA is usually the right target for production audit work.

It includes Level A and adds important requirements around contrast, focus, navigation, input assistance, resizing, labels, and interaction behavior.

For developers and QA teams, AA findings usually become practical remediation tickets with clear expected behavior and retest conditions.

Level AAA: selective deeper coverage

AAA is the highest conformance level.

It can be valuable, but it is not always a realistic whole-product requirement.

Use selected AAA checks when the content or journey justifies deeper accessibility support. Examples may include education, healthcare, public information, financial disclosure, or critical service journeys.