Skip to content

WCAG

WCAG is an international standard containing testable requirements for making web content more accessible to people with disabilities.

The Web Content Accessibility Guidelines, or WCAG, are an international standard for making web content more accessible to people with disabilities.

WCAG provides testable requirements that can be used to evaluate websites, applications, and other digital content.

What It Covers

WCAG organizes accessibility requirements around four broad principles. Content should be:

  • Perceivable: People need to be able to perceive the information being presented.
  • Operable: Interface controls and navigation need to be usable.
  • Understandable: Content and interactions need to make sense.
  • Robust: Content needs to work reliably with different browsers and assistive technologies.

Individual requirements are defined through success criteria.

How It Works

WCAG success criteria are assigned conformance levels: A, AA, or AAA.

Level A contains fundamental requirements. WCAG Level AA includes both A and AA requirements and is a common target for websites and accessibility policies. Level AAA adds further criteria but is not generally treated as a practical requirement for every page of an entire site.

The WCAG version matters too. WCAG 2.2 builds on earlier WCAG 2.x versions with additional success criteria.

Why It Matters

WCAG gives teams a shared framework for talking about accessibility.

Instead of deciding subjectively whether a website “looks accessible,” designers, developers, content teams, auditors, and organizations can evaluate specific behaviours against documented requirements.

WCAG does not eliminate the need for judgement or user testing, but it provides a dependable technical baseline.

Common Problems

Common misunderstandings include:

  • Treating WCAG as a design checklist rather than a standard
  • Assuming passing an automated accessibility test proves conformance
  • Referring to “WCAG compliance” without identifying a version or level
  • Fixing isolated criteria without considering the overall user experience
  • Assuming accessibility ends once an audit is complete

How to Improve

Define the WCAG version and target level before auditing or rebuilding a site.

Combine automated accessibility testing with manual accessibility testing, and interpret individual failures in the context of templates, components, and actual user tasks.