What Is WCAG?
WCAG organizes web accessibility needs into testable success criteria. Learn its four principles, cumulative A/AA/AAA levels, the differences between 2.1 and 2.2, and why scans cannot replace a complete evaluation.
Last updated:
Key Takeaways
- WCAG stands for Web Content Accessibility Guidelines.
- It is not a single tool or an automated scan report. It is a set of international guidelines for making web content easier to perceive, operate, understand, and use with assistive technologies.
- Identify the standard version, level, pages, and complete processes being evaluated; do not infer every requirement from the site’s location.
A plain-language way to understand WCAG
If you are working on web accessibility, think of WCAG as a shared language. It helps product, design, engineering, QA, and site owners decide whether a website can actually be used by people in different situations.
WCAG is not only an engineering checklist. It affects button design, error messages, form labels, content structure, keyboard interaction, and whether users can complete tasks without unnecessary barriers.
What does WCAG mean?
WCAG is developed by the W3C Web Accessibility Initiative. It organizes requirements for web content, interactive components, forms, images, video, keyboard operation, and assistive technology support into testable success criteria.
In practice, WCAG is used as the foundation for web accessibility testing, accessibility audits, procurement requirements, and internal product quality standards.
Who needs to understand WCAG?
Product managers need WCAG because accessibility issues can become abandoned flows, support costs, and acceptance risks. Designers need WCAG because contrast, focus states, touch targets, error messages, and information hierarchy affect accessibility before code is written.
Frontend engineers and QA teams need WCAG because many issues appear in component states, keyboard behavior, ARIA, form validation, dynamic content, and real browser flows. Site owners need the basics so they can interpret audits, claims, and remediation work.
The four WCAG principles: POUR
WCAG groups its requirements under four principles: Perceivable, Operable, Understandable, and Robust, often shortened to POUR.
Perceivable means information should not rely on a single sense. Operable means users should be able to interact without a mouse. Understandable means labels, instructions, errors, and flows should be clear. Robust means content should work reliably with browsers and assistive technologies.
WCAG is not only an engineering issue
Some WCAG issues can be fixed in code, such as missing form labels, incorrect ARIA, focus order problems, or keyboard traps. Many others come from content and design: vague link text, unclear errors, weak alt text, or color being the only cue.
A mature accessibility workflow connects design review, content review, frontend implementation, automated checks, manual review, and QA acceptance instead of treating accessibility as a last-minute cleanup task.
What is the difference between A, AA, and AAA?
Success criteria have three cumulative levels: A, AA, and AAA. Conformance to AA in a specified version requires all applicable A and AA criteria in the evaluated scope, not just the AA criteria. AAA adds the AAA criteria.
Conformance also involves requirements such as full pages and complete processes. A passing component, a few sampled pages, or a scan with no findings does not establish site-wide AA conformance. Even a specified conformance level does not cover every user need.
Start with a real task
For example, try a contact form: identify field labels, fill it with a keyboard, submit incomplete data, understand the errors, correct them, and submit again. Map findings to applicable criteria and record the page and state.
This is a starting exercise, not a complete AA checklist. The related WCAG checklist offers a review sequence; a full evaluation must still cover the specified standard and scope.
How are WCAG 2.1 and WCAG 2.2 different?
WCAG 2.2 adds nine success criteria, including focus obstruction, alternatives to dragging, target size, and accessible authentication, and removes 4.1.1 Parsing. It is not an unchanged superset of every 2.1 criterion.
New criteria have different levels: 2.4.11 Focus Not Obscured (Minimum) is AA, while 2.4.13 Focus Appearance is AAA. Check the version and level you are using; separately verify any document specified by a local standard, procurement process, or badge scheme.
How do you check whether a website meets WCAG?
WCAG cannot be fully checked with automation alone. Automated scans are useful for issues such as missing alt text, form labels, ARIA errors, and detectable contrast failures. Human review is still needed for keyboard flow, meaningful error messages, reading order, and task completion.
Combine findings from automation, keyboard use, actual assistive technologies, zoom, and task testing. Record the applicable criterion, reproduction steps, and retest outcome. Simulations can supplement this work, not replace real experience testing.
How WCAG relates to DevCheck
Accesserty DevCheck is not legal advice, and a scan is not a full compliance guarantee. Its role is to help PMs, design, QA, engineering, content, and operations roles find WCAG-related risks faster inside the browser, including local pages, staging sites, authenticated flows, interactive states, focus paths, and PDF structure signals.
In practice, DevCheck can be the first layer of a WCAG improvement workflow: identify clear, reproducible, fixable issues, then combine that with manual testing for a more complete accessibility review.
Frequently Asked Questions
Is WCAG a law?
WCAG is a W3C technical standard, not a jurisdiction’s law in itself. Procurement rules, policies, or laws may reference it; this overview does not determine your site’s legal obligations.
Does passing an automated scan mean a site meets WCAG?
No. Automated tools only check part of WCAG. Keyboard operation, screen reader experience, form guidance, content context, and real task flows still require human review.
How do I choose between WCAG 2.1 and 2.2?
Identify the version and level specified for the project, evaluation, procurement, or applicable requirement, then map the differences. Distinguish W3C versions from locally adopted documents rather than choosing solely by the site’s language.
What are the four WCAG principles?
The four WCAG principles are Perceivable, Operable, Understandable, and Robust. Levels A, AA, AAA, testing codes, tool names, and accessibility badges are not the principles themselves.
What does WCAG Level AA mean?
AA in a specified version requires all applicable A and AA success criteria in scope, together with conformance requirements such as full pages and complete processes. It is not just passing the AA criteria or one automated scan.
Which WCAG version does Taiwan’s 110.07 document reference?
The MODA-published document references WCAG 2.1 and uses testing codes, audit evaluation codes, and testing levels. For a badge application or official assessment, also check the authority’s applicable announcements and process.