Skip to content

WCAG Guidelines

The Web Content Accessibility Guidelines (WCAG) are the international standard for digital accessibility. Most regulations (ADA, Section 508, EN 301 549) reference WCAG, so meeting these guidelines often means meeting legal requirements too.

WCAG is organized around four principles — often remembered as POUR:

Users must be able to perceive the content through at least one sense.

  • Provide text alternatives for images (alt text)
  • Caption videos and provide transcripts for audio
  • Don’t rely on color alone to convey meaning
  • Ensure sufficient contrast (4.5:1 for normal text, 3:1 for large text)
  • Allow text to be resized up to 200% without breaking layouts

Users must be able to operate the interface.

  • Make everything keyboard accessible — no mouse-only interactions
  • Provide visible focus indicators
  • Give users enough time to read and act
  • Don’t use content that flashes more than 3 times per second
  • Help users navigate with clear headings, skip links, and landmarks

Users must be able to understand the content and interface.

  • Use clear, simple language appropriate to your audience
  • Make navigation consistent across pages
  • Identify input errors clearly and suggest corrections
  • Label form fields clearly

Content must work reliably across different technologies.

  • Use valid, semantic HTML
  • Ensure custom components expose proper names, roles, and states
  • Test with actual assistive technologies, not just automated tools
  • Level A: Minimum accessibility — must fix these issues
  • Level AA: Standard target for most websites and apps
  • Level AAA: Enhanced accessibility — aspirational for most, required for some audiences

Most organizations aim for WCAG 2.2 AA as the baseline.

The majority of accessibility failures come from a short list of problems:

  • Missing or poor alt text
  • Low color contrast
  • Missing form labels
  • Empty links and buttons
  • Missing document language
  • Poor heading structure

Fix these first, and you’ll address most of your issues.

This trips up a lot of teams, because the version you should build to and the version that is legally required of you are usually not the same.

If you are…Legally requiredRecommended target
US state or local government (ADA Title II)WCAG 2.1 AA2.2 AA
US HHS-funded healthcare (Section 504)WCAG 2.1 AA2.2 AA
US federal agency or contractor (Section 508)WCAG 2.0 AA2.2 AA
Selling into the EU (EAA / EN 301 549 V3.2.1)WCAG 2.1 AA2.2 AA
Everyone elseNo general mandate2.2 AA

Full deadline tables, penalty ranges, and jurisdiction detail live in Standards & Guidelines.

On 21 October 2025 WCAG 2.2 was approved as ISO/IEC 40500:2025, matching the October 2023 version exactly. This matters mainly because it lets countries that adopt standards by ISO reference pick up WCAG 2.2 without writing their own. The December 2024 editorial update is expected to land as ISO/IEC 40500:2026 in late 2026.

WCAG 2.2 was published 5 October 2023 and editorially updated 12 December 2024. WCAG 2.1 received an updated Recommendation on 6 May 2025 covering minor technical issues. Its nine added criteria over 2.1 include:

  • Target Size (Minimum), 2.5.8 — tap targets at least 24×24 CSS pixels
  • Dragging Movements, 2.5.7 — a non-drag alternative for any drag operation
  • Focus Not Obscured, 2.4.11 — sticky headers must not cover the focused element
  • Accessible Authentication, 3.3.8 — no cognitive function test to log in
  • Redundant Entry, 3.3.7 — don’t ask for the same information twice in a process

Two federal deadlines moved within three weeks of each other in 2026:

  • 17 April 2026 — DOJ extended ADA Title II to 26 April 2027 (population ≥ 50,000) and 26 April 2028 (smaller entities and special districts)
  • 7 May 2026 — HHS extended Section 504 to 11 May 2027 (15+ employees) and 10 May 2028 (fewer than 15), four days before the original date

Neither extension changed the technical requirement. Both remain WCAG 2.1 AA.

Litigation has not slowed: Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, up 27% from 2,452 in 2024, and 36% of all federal ADA Title III filings.

The EAA is applicable, enforcement is uneven

Section titled “The EAA is applicable, enforcement is uneven”

The European Accessibility Act became applicable on 28 June 2025. In its first year enforcement varied widely by member state — France’s DGCCRF issued formal notices to four major retailers in November 2025, German operators saw law-firm warning letters, and Dutch enforcement is expected in the second half of 2026. As of mid-2026 no confirmed EAA fine had been publicly verified, though authorities can also order product withdrawal and mandate audits.

W3C published a new Working Draft on 3 March 2026. “Outcomes” are now requirements (174 of them), and the bronze/silver/gold conformance model has been dropped in favour of an approach still being revised. Candidate Recommendation is anticipated around Q4 2027; a final Recommendation not before 2028, and WCAG 2 will stay current for several years after that.

WCAG 3’s direction — task completion, severity, and cognitive factors over binary pass/fail — is already shaping how practitioners think. Read it for that. Do not set compliance targets against it.

Automated-detectable failures are getting worse

Section titled “Automated-detectable failures are getting worse”

The 2026 WebAIM Million found 95.9% of the top million home pages had detected WCAG 2 failures, up from 94.8% in 2025 — the first regression after six years of improvement. Average errors per page rose 10.1% to 56.1. Low contrast text alone now affects 83.9% of home pages, up 4.8 points in a single year.

The six failures listed under Common high-impact issues above account for 96% of everything detected. None of them require a redesign to fix.

Official Standards:

Recent Updates:

Regulations (primary sources):

Practical Resources: