WCAG is a web accessibility standard that defines testable requirements for making websites, web apps, and digital content usable by people with disabilities. Created by the World Wide Web Consortium, it organizes accessibility guidance around perceivable, operable, understandable, and robust experiences. WCAG is not itself a law, but it is widely used as the technical benchmark referenced by accessibility policies and regulations.
WCAG
What Is WCAG?
WCAG, or Web Content Accessibility Guidelines, is a technical standard for making websites, web apps, mobile content, and digital interfaces usable by people with disabilities. Developed by the W3C, it provides testable requirements for accessible software. WCAG is not a law itself, but regulations and organizational policies often use it as their technical benchmark.
How WCAG Works: POUR, Guidelines, and Success Criteria
WCAG organizes accessibility requirements from broad principles down to specific checks. Teams test their interface against applicable success criteria.
| Principle | Meaning | Example |
|---|---|---|
| Perceivable | Users can sense the content. | Provide useful text alternatives and captions. |
| Operable | Users can control the interface. | Support keyboard navigation and visible focus. |
| Understandable | Content and actions are clear. | Show clear form errors and instructions. |
| Robust | Technology works with assistive tools. | Use semantic HTML and correctly named controls. |
WCAG Conformance Levels: A, AA, and AAA
Conformance is not an average score. A page must meet every applicable criterion at its chosen level.
| Level | What it represents | Typical use |
|---|---|---|
| A | Essential baseline barriers addressed. | Minimum starting point. |
| AA | Addresses many common access barriers. | A common project target, including WCAG 2.2 AA. |
| AAA | Highest level with stricter requirements. | Useful selectively, but rarely practical for every page. |
WCAG 2.0, 2.1, 2.2, and WCAG 3
WCAG 2.2 is the current finalized WCAG 2 Recommendation, and it builds on 2.0 and 2.1. WCAG 3 remains under development, not a released replacement. Whether a team must use 2.1 or 2.2 depends on the applicable policy or jurisdiction, so technical conformance should be checked alongside current legal guidance.
Benefits of Building to WCAG
Accessibility practices improve the quality of digital products for many users.
- Keyboard and screen-reader users can complete core tasks more reliably.
- Clear labels, navigation, and errors reduce avoidable user mistakes.
- Semantic code improves compatibility with browsers and assistive technologies.
- Accessibility reviews often expose general usability defects early.
Practical Limits of WCAG Testing
Automated checks help, but they cannot prove a product is conformant.
- Tools cannot judge whether alt text is meaningful or instructions are understandable.
- Human testing is needed to verify focus order, zoom behavior, and task completion.
- WCAG conformance does not replace legal advice or testing with disabled users.
How to Test a Web App for WCAG
Build accessibility checks into the development process, not only a final review.
- Set a target version and level, such as WCAG 2.2 AA.
- Review reusable components during app design and development.
- Run automated accessibility checks to find common code issues.
- Complete key journeys using only a keyboard.
- Test forms and navigation with a screen reader, zoom, and reflow.
- Fix shared components before patching individual pages.
- Document findings, decisions, and remaining exceptions.
WCAG in AI-Assisted App Development
AI-generated interfaces still need accessibility review. When using an AI web app builder, specify keyboard support, semantic controls, labels, and error handling early, then test the completed journey. Emergent helps teams build and iterate on web apps quickly, while developers remain responsible for reviewing generated code and validating WCAG outcomes.
Start Building
on Emergent today
on Emergent today
Start Building
