WCAG, short for the Web Content Accessibility Guidelines, is the international technical standard for making websites, apps, and digital documents usable by people with disabilities. It is published by the World Wide Web Consortium (W3C) and organized around four principles and three conformance levels that give developers testable requirements to meet. What was once a voluntary best practice now carries real legal weight in the United States: the Department of Justice enforces WCAG through the Americans with Disabilities Act, Section 508 references it for federal agencies, and civil penalties for violations reach into six figures.
The Four Principles Behind Every WCAG Requirement
Every criterion in WCAG traces back to four principles, usually shortened to POUR: perceivable, operable, understandable, and robust. The framework is meant to keep the focus on how a person actually uses a site, rather than on a checklist divorced from experience.
Perceivable
Users have to be able to sense the content with the senses available to them. Meaningful images need text alternatives so a screen reader can describe them; decorative images should use an empty alt attribute so assistive technology skips them entirely instead of reading out a file name.1Web Accessibility Initiative (WAI) | W3C. Decorative Images Video needs captions, audio needs transcripts, and information can never be conveyed through color alone, since that shuts out anyone who is colorblind.
Operable
Every interactive element has to work for people who navigate differently. Someone who cannot use a mouse needs to reach every link, button, and form field with a keyboard. Timed sessions have to give users enough time to read and respond. Content cannot flash at rates known to trigger seizures. Under WCAG 2.2, any action that relies on dragging must also work through a single click or tap, and clickable targets must be at least 24 by 24 CSS pixels so people with limited dexterity can actually hit them.2W3C. Understanding Success Criterion 2.5.8 – Target Size (Minimum)
Understandable
Content and behavior have to be predictable. Navigation stays consistent across pages. Forms give clear error messages that explain what went wrong and how to fix it. Multi-step processes cannot force users to re-enter information they have already provided; the site either auto-populates the data or lets the user select it, which helps people with cognitive disabilities and short-term memory difficulties.3W3C. Understanding Success Criterion 3.3.7 – Redundant Entry
Robust
The underlying code has to be clean enough for assistive technology to interpret reliably. That means valid HTML, properly labeled interactive elements, and no reliance on browser-specific tricks that break with a screen reader or a browser update. Poorly structured markup creates invisible barriers no visual design can overcome.
Conformance Levels: A, AA, and AAA
WCAG sorts its requirements into three tiers, and each builds on the one below it. The distinction matters because laws and contracts specify which level you have to meet.
Level A is the bare minimum. It addresses the most severe barriers, like missing text alternatives for images or content that triggers seizures. A site meeting only Level A still has significant usability problems for many people with disabilities.
Level AA is the target most people actually care about. It includes everything in Level A plus requirements like minimum color contrast ratios of 4.5:1 for normal text and 3:1 for large text, visible keyboard focus, and consistent navigation. Both the DOJ’s ADA regulations and Section 508 reference Level AA, and when someone says a site is “WCAG compliant,” they almost always mean Level AA.4W3C. Web Content Accessibility Guidelines (WCAG) 2.1
Level AAA is the most demanding tier, adding enhanced contrast, sign language interpretation for audio, and stricter focus indicators.5W3C. Understanding Success Criterion 2.4.13 – Focus Appearance Few organizations achieve full Level AAA across an entire site, and no major regulation mandates it universally. Some pursue it for specific high-traffic pages.
Which Version of WCAG Applies
WCAG has evolved through several versions, and each is backward-compatible with the last. That matters because different laws reference different versions.
WCAG 2.0 became a W3C Recommendation on December 11, 2008, and established the POUR framework and the A/AA/AAA structure still used today.6W3C. Web Content Accessibility Guidelines (WCAG) 2.0 Publication History Federal agencies still follow this version for Section 508.
WCAG 2.1, published on June 5, 2018, added 17 success criteria covering mobile accessibility, low-vision users, and cognitive disabilities, including content reflow for small screens, non-text contrast for interface components, and pointer gestures.4W3C. Web Content Accessibility Guidelines (WCAG) 2.1 This is the version the DOJ now requires for state and local government sites.
WCAG 2.2 reached Recommendation status in December 2024, adding nine more criteria on top of 2.1.7W3C. Web Content Accessibility Guidelines (WCAG) 2.2 Notable additions include Focus Not Obscured (a tabbed-to element cannot be hidden behind sticky headers or cookie banners), Target Size Minimum, Accessible Authentication (login processes cannot require memorizing passwords or solving puzzles unless an alternative is available), and Consistent Help (help features must stay in the same relative location across pages). No U.S. regulation currently mandates 2.2, but settlement agreements increasingly reference it, so organizations starting fresh are better off targeting 2.2 directly.
WCAG 3.0 remains in Working Draft status as of March 2026 and is expected to overhaul the conformance model rather than simply add criteria.8W3C. W3C Accessibility Guidelines (WCAG) 3.0 Publication History It is not replacing the 2.x series anytime soon.
When WCAG Becomes a Legal Requirement
WCAG itself is a technical standard, not a law. But three sets of U.S. rules make specific versions of it legally binding for specific organizations.
The DOJ’s 2024 Title II Rule
On April 24, 2024, the DOJ published a final rule that, for the first time, explicitly requires state and local government websites and mobile apps to conform to WCAG 2.1 Level AA.9U.S. Department of Justice. Fact Sheet – New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments Deadlines depend on population:
- April 24, 2026 for state and local governments with a total population of 50,000 or more.
- April 26, 2027 for governments under 50,000 and all special district governments.
The rule is codified at 28 CFR 35.200 and allows narrow defenses for fundamental alteration or undue financial burden, but those must be demonstrated case by case.10eCFR. 28 CFR 35.200 – Requirements for Web and Mobile Accessibility There are limited exceptions for archived content, certain preexisting documents, third-party content, password-protected individualized documents, and old social media posts, but a preexisting PDF that someone still needs to fill out to receive a government service does not qualify.
Title III and Private Businesses
ADA Title III covers private businesses that qualify as places of public accommodation, which includes most consumer-facing operations in retail, hospitality, banking, and healthcare.11eCFR. 28 CFR Part 36 – Nondiscrimination on the Basis of Disability by Public Accommodations and in Commercial Facilities No regulation yet names WCAG 2.1 as the private-sector standard, but courts and the DOJ consistently use it as the measuring stick, and settlement agreements in Title III cases almost universally require WCAG 2.1 Level AA.
Section 508 and Federal Agencies
Section 508 of the Rehabilitation Act requires federal agencies to make electronic and information technology accessible.12Office of the Law Revision Counsel. 29 USC 794d – Electronic and Information Technology The Access Board’s standards at 36 CFR Part 1194 require federal electronic content to conform to WCAG 2.0 Level A and Level AA.13eCFR. 36 CFR Part 1194 – Information and Communication Technology Standards and Guidelines Federal contractors and grant recipients must meet the same standard. Because updates are backward-compatible, meeting 2.1 automatically satisfies the 2.0 reference in Section 508.
What Non-Compliance Actually Costs
Enforcement comes from two directions.
Private plaintiffs can sue businesses under Title III for injunctive relief and attorney’s fees; monetary damages are not available in federal Title III cases.14Office of the Law Revision Counsel. 42 USC 12188 – Enforcement15Office of the Law Revision Counsel. 42 USC 12205 – Attorneys Fees Attorney’s fees in accessibility cases routinely reach tens of thousands of dollars, and remediation under court supervision costs far more. In the first half of 2025, more than 2,000 ADA website accessibility lawsuits were filed in federal courts, a 37% increase over the same period in 2024.
DOJ enforcement is more expensive. The DOJ can pursue civil penalties for Title III violations when it identifies a pattern of discrimination or an issue of general public importance. As of the July 2025 inflation adjustment, the maximum civil penalty is $118,225 for a first violation and $236,451 for subsequent violations, on top of any required remediation.16eCFR. 28 CFR Part 85 – Civil Monetary Penalties Inflation Adjustment For state and local governments, the 2024 Title II rule gives the DOJ a clear, measurable compliance standard to enforce against for the first time.
How to Test a Site Against WCAG
Automated testing tools catch roughly 30 to 40 percent of WCAG issues. They are good at flagging missing alt text, broken form labels, and insufficient color contrast. They cannot judge whether alt text actually describes an image meaningfully, whether a keyboard user can navigate a complex form logically, or whether an error message makes sense to someone with a cognitive disability. Those judgments require manual testing by someone who understands how assistive technology works.
Most compliance efforts fall short here. Organizations run an automated scan, fix the flagged issues, and assume they are done. That leaves the majority of barriers untouched. A serious effort combines automated scanning with manual expert review and testing by actual users of assistive technology.
For a practical starting point, target WCAG 2.1 Level AA, since that is what the DOJ’s Title II rule and most settlement agreements require. Address Level A criteria first to remove the worst barriers, then work through Level AA systematically. Build accessibility checks into your development process rather than treating them as a one-time project, because every new page, feature, or content update can introduce new issues.