Accessibility and WCAG

Design Systems & Engineering • Product Strategy & Growth

Web accessibility means designing and building websites and tools that people with disabilities can use. The Web Content Accessibility Guidelines (WCAG), developed through the W3C Web Accessibility Initiative, provide testable requirements for making web content more accessible.

Accessibility addresses visual, auditory, motor, cognitive, and other access needs. WCAG provides a technical baseline; usability testing with people with disabilities helps teams understand barriers in real tasks.

What are the four WCAG principles?

WCAG organizes its requirements under four principles, often abbreviated POUR:

Principle What it means in practice
Perceivable Provide information people can perceive, such as text alternatives for meaningful images and captions for video.
Operable Make controls usable with different input methods, including a keyboard.
Understandable Use clear instructions, predictable behavior, and helpful error messages.
Robust Expose content and controls so browsers and assistive technologies can interpret them.

What do A, AA, and AAA mean?

These are cumulative conformance levels. A covers Level A criteria; AA includes A and AA; AAA includes all three levels. A conformance claim records the version, level, scope, date, and technologies relied upon. It applies to full pages and complete processes, such as every step of checkout.

WCAG 2.2 is a W3C Recommendation. WCAG 3 remains a draft. WCAG conformance does not establish compliance with every applicable accessibility law.

Which WCAG 2.2 checks matter in everyday design?

These examples are a starting point, not a complete audit:

An accessible form example

Consider a quote-request form with an email field. A persistent label is programmatically associated with the field. Keyboard users can reach it and see focus. If the address is incomplete, the form displays “Enter an email address in the format name@example.com” and programmatically associates that message with the field.

The error message explains the problem without relying on color alone. Previously entered values remain available, and the submission confirmation is perceivable with assistive technology. Test the full submission flow, including errors and confirmation.

How should teams test accessibility?

Combine automated checks with manual keyboard, zoom, and screen-reader testing. Include people with disabilities in usability research, and evaluate complete tasks as well as individual components. Automated tools can identify some failures; a clean scan does not prove WCAG conformance.

Sources