WCAG 2.1 AA Explained for Website Owners
WCAG 2.1 AA is a widely used technical benchmark for web accessibility. It organizes requirements around four principles: perceivable, operable, understandable, and robust.
Updated 2026-07-07
Perceivable
Users need ways to perceive content through different senses and technologies. Examples include text alternatives for images, captions where appropriate, readable contrast, and content that adapts to different viewport sizes.
Operable
Interfaces should work without requiring a mouse. Keyboard focus, visible focus indicators, bypass links, predictable controls, and enough time to complete tasks all matter.
Understandable
Pages should be titled clearly, use the correct language metadata, label forms, explain errors, and avoid unexpected behavior that makes tasks harder to complete.
Robust
Markup should support browsers and assistive technologies. Valid semantics, appropriate ARIA, accessible names, and programmatically determinable states help technology interpret the page.
Why scans cover only part of WCAG
Automated tools can detect many objective technical failures, but they cannot fully judge meaningful alt text, screen reader experience, keyboard task completion, content clarity, or legal interpretation.
Important note
This guide is educational and supports technical accessibility planning. It is not legal advice, does not certify compliance, and should be paired with manual review where risk matters.