What Is WCAG?
WCAG (Web Content Accessibility Guidelines) is the internationally recognized technical standard, published by the World Wide Web Consortium (W3C), that defines how to make web content usable by people with disabilities. It organizes requirements under four principles — perceivable, operable, understandable, and robust — and sets three conformance levels (A, AA, AAA). WCAG 2.1 Level AA is the benchmark most US courts, agencies, and businesses treat as the practical target for an accessible website.
- Published by
- World Wide Web Consortium (W3C) / Web Accessibility Initiative (WAI)
- Current versions
- WCAG 2.0 (2008), 2.1 (2018), 2.2 (2023); WCAG 3.0 in draft (W3C)
- Conformance levels
- A (minimum), AA (standard target), AAA (highest) (W3C)
- Legal benchmark
- WCAG 2.1 AA is the de facto US reference for ADA and Section 508 claims (industry-typical)
What does WCAG actually cover? #
WCAG is a set of testable success criteria that describe what accessible web content looks like, not how to code it in any single framework. The guidelines apply to text, images, audio, video, forms, navigation, and interactive components across websites, web apps, and increasingly mobile experiences. Each success criterion is written so a human or automated tool can verify pass or fail. For a local business, that means WCAG governs everything from whether your phone number is announced correctly by a screen reader to whether a customer can complete a booking form without a mouse. Because WCAG is technology-neutral, it stays relevant as tools change — the same criterion about text alternatives applies whether you build on /services/wordpress-development or a custom stack. Understanding the scope matters because accessibility is not a plugin you install once; it is a property of the content and interface itself. Our overview of /wiki/what-is-ada-website-compliance explains how these technical rules connect to US law.
The four POUR principles #
WCAG groups every requirement under four principles remembered by the acronym POUR. Perceivable means information must be presentable in ways users can sense — captions for video, text alternatives for images, sufficient /wiki/what-is-color-contrast-ratio isn't listed but color contrast for low-vision users. Operable means all functionality works through a keyboard, users have enough time, and nothing triggers seizures. Understandable means text is readable, pages behave predictably, and forms help users avoid and fix mistakes. Robust means content works reliably with current and future assistive technologies, including screen readers, by using valid, well-structured code. These principles are the backbone of the standard: if you cannot map a fix to one of the four, it probably is not a WCAG issue. Designers and developers use them as a mental checklist during builds, and our team applies them throughout /services/ui-ux-design so accessibility is designed in rather than retrofitted after launch.
What do A, AA, and AAA mean? #
WCAG defines three conformance levels reflecting increasing strictness. Level A covers the most basic requirements; failing them makes content impossible or extremely difficult for some users. Level AA adds the criteria most people consider essential — adequate contrast, resizable text, consistent navigation, and clear error handling. Level AAA is the most demanding and is rarely required for an entire site because some criteria cannot be met for all content types. In the United States, WCAG 2.1 Level AA is the practical target: it is what the Department of Justice references, what Section 508 adopts, and what settlement agreements typically require. Aiming for AA gives a local business strong legal footing and genuinely usable pages without chasing AAA criteria that may be impractical. When we scope an accessibility remediation through /services/web-design, AA is almost always the agreed conformance goal, with select AAA wins where they are easy and high-value.
How WCAG versions differ (2.0 to 2.2) #
WCAG 2.0 launched in 2008 and remains the legal baseline in some regulations. WCAG 2.1, published in 2018, added seventeen success criteria addressing mobile devices, touch input, low vision, and cognitive disabilities — things like orientation, pointer gestures, and reflow at high zoom. WCAG 2.2, finalized in 2023, added nine more criteria, including stronger focus-appearance rules, accessible authentication, and consistent help placement, while removing one criterion (parsing) that modern browsers made obsolete. Each version is backward compatible: meeting 2.2 AA means you also meet 2.1 AA and 2.0 AA. For most US local businesses, targeting WCAG 2.1 AA satisfies current legal expectations, while adopting 2.2 improvements future-proofs the site. WCAG 3.0 is a longer-term rewrite still in draft and should not drive today's decisions. During a /services/website-redesign we typically build to 2.2 where practical.
Is WCAG legally required in the US? #
WCAG itself is a voluntary technical standard, but US law repeatedly points to it. The Americans with Disabilities Act (ADA) does not name WCAG in its text, yet federal courts and the Department of Justice have consistently treated WCAG 2.1 AA as the reasonable measure of an accessible website for businesses open to the public. Section 508 of the Rehabilitation Act formally incorporates WCAG 2.0 AA for federal agencies and many contractors. State laws such as California's Unruh Act and various procurement rules also lean on WCAG. Practically, this means a plumber, dentist, or law firm sued over an inaccessible site will be judged against WCAG criteria even though no statute lists them one by one. Meeting WCAG 2.1 AA is the strongest defensible position. Our /wiki/website-privacy-laws-explained entry covers adjacent US compliance obligations that often surface in the same legal reviews.
Who benefits from WCAG conformance? #
The obvious beneficiaries are people with disabilities: blind and low-vision users relying on screen readers or magnification, people with motor impairments using keyboards or switch devices, deaf and hard-of-hearing users needing captions, and people with cognitive or learning differences who need clear structure. But WCAG improvements help far more visitors than that. Captions help anyone in a noisy waiting room. High contrast helps users on a phone in bright sunlight. Keyboard support helps power users and people with temporary injuries. Clear form errors help everyone check out faster, which is why accessibility and /services/conversion-optimization overlap so heavily. Older adults — a large share of many local customer bases — benefit from larger targets and readable text. There is also a substantial SEO overlap: the same semantic structure, descriptive headings, meaningful link text, and image alternatives that WCAG demands also help search engines understand your pages, so accessibility work quietly supports your /services/local-seo results. Framing WCAG as usability for the widest possible audience, rather than a niche compliance chore, is how successful businesses justify the investment and get compounding returns that touch traffic, trust, and revenue alike.
How is WCAG conformance tested? #
Testing WCAG combines automated scanning and manual evaluation. Automated tools quickly flag missing alt text, low contrast, empty links, and structural errors, and our free /tools/website-grader and /tools/ada-compliance-checker give a fast first read. However, automation catches only a portion of criteria — studies suggest roughly a third to half. The rest require human judgment: does the alt text actually describe the image's purpose, is the keyboard focus order logical, does the page make sense when read aloud by a screen reader. A proper evaluation includes testing with real assistive technology, keyboard-only navigation, and zoom. Because a single criterion can pass automatically yet fail in practice, credible conformance claims come from combined testing documented in a report. Our detailed /wiki/what-is-an-accessibility-audit covers this, and our /services/care-plans include recurring checks so a site stays conformant as content changes.
How do you keep a site WCAG-conformant over time? #
Conformance is a moving target because websites change constantly — new blog posts, uploaded PDFs, swapped images, third-party widgets, and plugin updates can all introduce violations. A site that passed at launch can drift out of compliance within months if no one is watching. The practical answer is process: give content editors simple rules (always add meaningful alt text, use built-in heading styles, never rely on color alone), run periodic automated scans, and schedule manual spot checks after major changes. Embedding accessibility into your publishing workflow costs far less than a full remediation later. For businesses without in-house expertise, ongoing /services/care-plans and managed monitoring keep accessibility from silently degrading. Pair that with training so your staff understand the basics. Treating WCAG as a maintained property of the site, not a one-time certificate, is what protects both your users and your legal position long term. Many businesses also publish an accessibility statement describing their conformance target and how users can report problems, which signals good faith and gives visitors a clear path to raise issues before they escalate.
FAQ
Does WCAG apply to small local businesses?
Yes. US courts have applied ADA website-accessibility expectations to businesses of all sizes, including small local shops, service providers, and restaurants. While enforcement risk varies, any business serving the public benefits from meeting WCAG 2.1 AA. Small businesses are frequent targets of demand letters, so conformance is both a legal safeguard and a way to serve more customers.
What is the difference between WCAG and the ADA?
The ADA is a US civil-rights law prohibiting disability discrimination; WCAG is a technical standard describing accessible web content. The ADA does not name WCAG, but courts and the Department of Justice treat WCAG 2.1 AA as the practical measure of whether a website meets ADA obligations. In short, WCAG is the yardstick used to judge ADA compliance online.
Which WCAG version and level should I target?
For nearly all US businesses, WCAG 2.1 Level AA is the right target. It matches the benchmark referenced in legal settlements and federal guidance while remaining achievable. Adopting the newer 2.2 AA criteria where practical future-proofs your site. Full AAA conformance is rarely required and often impossible across all content types.
Can an automated tool confirm WCAG conformance?
No. Automated scanners catch only part of WCAG success criteria — commonly a third to half. They excel at missing alt text, contrast, and structural errors but cannot judge whether alt text is meaningful, whether focus order is logical, or whether a page makes sense aloud. Reliable conformance claims combine automated tools with manual and assistive-technology testing.
How long does it take to make a site WCAG-conformant?
It depends on site size, complexity, and current state. A small brochure site with a few templates might reach WCAG 2.1 AA in a couple of weeks; a large site with custom apps, PDFs, and third-party widgets can take months. Remediation is faster when accessibility is built into a redesign rather than bolted onto an aging codebase.
Does WCAG cover PDFs and mobile apps?
WCAG applies to web content broadly, including PDFs delivered through a website, and its 2.1 and 2.2 additions specifically address mobile and touch interfaces. Native mobile apps often reference WCAG alongside platform-specific guidelines. For most local businesses, the priority is the public website and any downloadable documents, since those are the most common sources of accessibility complaints.
Was this helpful?