Can we count your visit?

Our analytics service records the pages you view, so we can see which ones are useful. It saves a random ID in your browser, and we never use it for advertising. Read our privacy policy.

Know the standard

The Web Content Accessibility Guidelines (WCAG) explain how to make web content more accessible to people with disabilities. Here is what the standard asks for and how to use it.

WCAG is developed by the World Wide Web Consortium (W3C). This is Standard Access’s explanation. W3C’s published WCAG standard is the source of truth for the requirements.

Read W3C’s WCAG 2.2 standard

The four principles

WCAG groups its requirements under four principles. These examples show what they mean in everyday use. They are not a complete checklist.

Perceivable

People can get the information in a way they can perceive.

A delivery chart needs its findings in text or a table. A demonstration video needs captions for speech and meaningful sounds. Text must remain available when enlarged.

Operable

People can use the controls and move through the content.

A customer must be able to choose a booking date and submit the form using a keyboard. Keep focus visible and provide a way to leave open menus and dialogs.

Understandable

People can understand the information and how the page behaves.

A form must say which date format it accepts before someone types. If an answer is wrong, the form must identify the field and explain how to correct it.

Robust

Content works with browsers and assistive technology.

A screen reader needs to identify a button and whether it is expanded or pressed. After a form is sent, make the confirmation available without requiring someone to see it.

W3C explains the accessibility principles.

What A, AA, and AAA mean

Each testable requirement, called a success criterion, has a level. The levels build on one another.

Level A
The first set of requirements. Meeting A alone leaves barriers that AA addresses.
Level AA
All Level A and AA requirements. WCAG 2.2 AA is the target we use for this website.
Level AAA
All A, AA, and AAA requirements. Individual AAA requirements can improve access, but W3C does not recommend requiring AAA for every site.

These are conformance levels, not scores or service packages. Passing most checks does not mean a page meets the level. Read W3C’s explanation of conformance.

Which version to use

W3C recommends WCAG 2.2 for new and updated work. WCAG 2.0 and 2.1 remain published standards, and a law, contract, or procurement policy may name one of those versions.

Version 2.2 adds requirements for areas such as visible keyboard focus, alternatives to dragging, target size, consistent help, repeated information, and sign-in. It also removes the obsolete Parsing criterion.

See what changed in WCAG 2.2.

Confirm the version and level your work needs to meet. Meeting WCAG does not, by itself, establish that you meet every legal obligation. Browse our summaries of accessibility laws.

What meeting WCAG means

Conformance means satisfying the standard’s requirements. It covers full pages and complete processes. A working product page cannot make up for a checkout that someone cannot finish.

The ways you provide content must work with assistive technology. Other content on the page must not interfere with access. W3C sets out five conformance requirements, including the level, full pages, and complete processes.

An evaluation needs to name the version, level, pages and tasks checked, testing methods, date, and findings. A review of a sample describes that sample. It does not show that every page works.

Read the five WCAG conformance requirements.

How to check your website

Start with a task your customers need to finish, such as booking, buying, or asking for help. Follow it from beginning to end.

  • Use the keyboard to reach controls, see where you are, and complete the task.
  • Review labels, image descriptions, instructions, and error messages in context.
  • Check small screens, enlarged text, and the assistive technology your audience uses.
  • Record barriers, fix them, and test the same task again. Include people with disabilities in the review.

Automated tools find some problems. A person needs to judge the rest. WCAG also does not cover every access need, so listening to people remains part of the work. Read W3C’s guidance on evaluation.

Choose tools for a first check

Follow our guide to finding and fixing common accessibility barriers.

Read the official sources

Use the standard for the exact requirements, including exceptions. W3C’s supporting explanations and techniques help you apply them. This overview does not replace them.

Last reviewed . This is general information, not legal advice. Which laws apply depends on where you operate and who you serve.