Web accessibility — making websites usable by people with disabilities — has moved from a nice-to-have to a near-requirement, driven by both ethics and legal exposure. WCAG 2.1 AA is the standard most commonly referenced. This article explains what WCAG 2.1 AA requires, why it matters legally and practically, and how to approach accessibility. It is general information, not legal advice.

What WCAG 2.1 AA is

WCAG (Web Content Accessibility Guidelines) is the internationally recognized standard for web accessibility, published by the W3C. It defines how to make web content accessible to people with a wide range of disabilities — visual, auditory, motor, cognitive, and others. WCAG 2.1 is a version of the guidelines, and AA is a conformance level (the middle level, between A and AAA) that’s the most commonly targeted and referenced standard for compliance. WCAG organizes its requirements around four principles, often summarized as POUR: content must be Perceivable (users can perceive it — e.g., text alternatives for images, captions for audio), Operable (users can operate it — e.g., keyboard accessibility, enough time to interact), Understandable (users can understand it — e.g., readable text, predictable behavior), and Robust (content works across assistive technologies and devices). Under these principles, AA conformance involves specific success criteria — things like sufficient color contrast, text alternatives for non-text content, keyboard accessibility, captions for video, clear navigation, properly labeled forms, and content that works with screen readers and other assistive technologies. WCAG 2.1 AA matters for two reasons: it’s the right thing to do (making your site usable by everyone, including the substantial population with disabilities), and it’s increasingly tied to legal exposure, as accessibility-related legal claims have grown and standards like WCAG 2.1 AA are commonly referenced as the benchmark. This is general information; consult an attorney about your specific legal obligations.

Common questions

What does WCAG 2.1 AA actually require?

Conformance with specific success criteria organized under the POUR principles — Perceivable, Operable, Understandable, Robust. In practice this includes things like sufficient color contrast between text and background, text alternatives (alt text) for images, captions for video, full keyboard accessibility (usable without a mouse), clear and consistent navigation, properly labeled and accessible forms, and content that works with assistive technologies like screen readers. AA is the middle conformance level and the commonly-targeted standard. Meeting it means addressing the range of criteria that make a site usable across the spectrum of disabilities, not just one or two accommodations.

Why does web accessibility matter legally?

Because accessibility-related legal claims have grown, and standards like WCAG 2.1 AA are commonly referenced as the benchmark for what’s expected. Inaccessible websites have increasingly been the subject of legal complaints, and meeting a recognized standard like WCAG 2.1 AA is a common way to demonstrate a good-faith accessibility effort. The legal landscape is complex and varies by jurisdiction and situation, so the specifics require legal counsel — but the general trend is that web accessibility carries real legal exposure, making WCAG 2.1 AA conformance a meaningful risk-reduction measure. Consult an attorney about your specific obligations.

What are the POUR principles?

The four principles WCAG is organized around: Perceivable (users can perceive the content — text alternatives for images, captions, sufficient contrast), Operable (users can operate the interface — keyboard accessibility, adequate time, navigable structure), Understandable (users can understand the content and interface — readable text, predictable behavior, clear instructions), and Robust (content works reliably across assistive technologies and devices). Together, POUR captures the dimensions of accessibility — perceiving, operating, understanding, and reliably accessing content. WCAG’s specific success criteria fall under these four principles, making POUR a useful framework for understanding what accessibility requires.

What are the most common accessibility failures?

Frequent issues include insufficient color contrast (text hard to read against its background), missing alt text on images (screen readers can’t describe them), lack of keyboard accessibility (the site can’t be used without a mouse), missing video captions, poorly-labeled forms (assistive technology can’t identify fields), and content that doesn’t work with screen readers. Many sites fail on these common, addressable points. Auditing against WCAG 2.1 AA typically surfaces these recurring failures, which are then fixable through specific remediation — contrast adjustments, adding alt text, ensuring keyboard operability, labeling forms properly, and testing with assistive technologies.

How do I know if my site is accessible?

Through accessibility auditing — combining automated testing tools (which catch many issues like contrast and missing alt text) with manual testing (keyboard navigation, screen reader testing, and human review, which catch issues automated tools miss). Automated tools alone aren’t sufficient because accessibility involves aspects only human testing reveals, so a thorough assessment combines both. An audit against WCAG 2.1 AA identifies where your site falls short and what needs remediation. Don’t assume accessibility without testing — many sites fail without their owners realizing it, because accessibility issues aren’t visible to users without disabilities.

Is accessibility just about legal compliance?

No — it’s also the right thing to do and has practical benefits. Beyond legal risk reduction, accessibility makes your site usable by the substantial population with disabilities (expanding your reachable audience), and many accessibility practices (clear structure, good contrast, proper labeling) improve usability for everyone and can benefit SEO. So accessibility is simultaneously ethical (inclusive of all users), practical (better usability and reach), and legally prudent (reducing exposure). Framing it solely as legal compliance undersells it — accessibility is good practice that happens to also reduce legal risk, benefiting your users, your reach, and your risk posture together.

Can I retrofit accessibility, or must I build it in?

Both are possible, but building accessibility in from the start is far more efficient than retrofitting. Designing and developing with accessibility in mind — proper structure, contrast, keyboard support, labeling — produces an accessible site naturally, while retrofitting an inaccessible site requires identifying and fixing numerous issues after the fact, which is more work. For new sites, build accessibility in. For existing sites, retrofitting through an audit and remediation is necessary and worthwhile despite being more effort. The lesson for any future development is that accessibility built in from the start is cheaper and better than accessibility bolted on later.

How this applies to your business

Treat WCAG 2.1 AA as both an ethical standard and a legal risk-reduction measure. Meeting it makes your site usable by the substantial population with disabilities — the right thing to do and a reach benefit — while also addressing the growing legal exposure around web accessibility, since WCAG 2.1 AA is the commonly-referenced benchmark. Approaching accessibility as good practice that also reduces legal risk captures its full value. Consult an attorney about your specific legal obligations, as the legal landscape is complex; this article is general guidance. Audit your site against WCAG 2.1 AA to know where you stand, combining automated and manual testing. Many sites fail common, addressable accessibility criteria — insufficient contrast, missing alt text, lack of keyboard accessibility, poorly-labeled forms — without their owners realizing, because these issues aren’t visible to users without disabilities. A thorough audit combining automated tools (for issues like contrast) and manual testing (keyboard, screen reader, human review) identifies your gaps and what needs remediation. Don’t assume accessibility without testing; audit to find the real state of your site. Build accessibility in for new development and remediate existing sites through audit and fixes. Building accessibility in from the start — proper structure, contrast, keyboard support, labeling — is far more efficient than retrofitting and produces a naturally accessible site. For existing sites, retrofitting through an audit and remediation is necessary and worthwhile. Either way, accessibility benefits your users, expands your reach, can help SEO, and reduces legal exposure simultaneously — making it a high-value investment whether built in or retrofitted. Iscope Digital’s Creative & Web Development service builds sites to WCAG 2.1 AA standards and audits/remediates existing sites for accessibility. For the broader quality standards good development meets, see Core Web Vitals in 2026, and for the structured data that complements accessible markup, JSON-LD schema for B2B websites.