Definition
WCAG (Web Content Accessibility Guidelines) is the international standard for digital accessibility, published by the World Wide Web Consortium (W3C). It defines testable success criteria organized around four principles: Perceivable (information must be presentable in ways users can perceive), Operable (interface components must be navigable and usable), Understandable (content and controls must be readable and predictable), and the fourth principle requiring content to work reliably with assistive technologies like screen readers.
Each success criterion has a conformance level (A, AA, or AAA) and a testable definition. For example, WCAG 2.2 Success Criterion 1.4.3 requires a contrast ratio of at least 4.5:1 between text and its background (Level AA). Criterion 2.4.7 requires that keyboard focus is visible (Level AA). Criterion 1.1.1 requires that all non-text content has a text alternative (Level A). These are not vague guidelines. They are specific, measurable requirements that automated tools (axe, Lighthouse, WAVE) can partially verify and manual testing can fully validate.
The broader accessibility entry covers the general concept of inclusive design. This entry focuses specifically on the WCAG standard as a specification that PMs, designers, and engineers use to define, implement, and validate accessibility requirements. Understanding WCAG is essential for any team building products that serve the public, government agencies, educational institutions, or regulated industries. Heuristic evaluation methods can be adapted to audit WCAG compliance across your product.
Why It Matters for Product Managers
WCAG compliance is increasingly a legal requirement, not just a best practice. In the United States, courts have ruled that the ADA applies to websites and mobile apps. The European Accessibility Act mandates WCAG 2.1 Level AA compliance for most digital products sold in the EU starting June 2025. Failure to comply creates both legal liability and reputational risk. Beyond compliance, accessible products reach a larger market. Over 15% of the global population has some form of disability, and temporary or situational disabilities (a broken arm, bright sunlight on a screen, a noisy environment) affect nearly everyone.
For PMs, WCAG provides a clear acceptance criteria framework. Instead of vague stories like "make the feature accessible," you can write specific requirements: "all interactive elements must have visible focus indicators (WCAG 2.4.7 Level AA)" or "form error messages must be programmatically associated with their fields (WCAG 1.3.1 Level A)." This specificity makes accessibility testable, reviewable, and shippable, just like any other product requirement.
How to Apply It
Integrate WCAG into your development process rather than treating it as a post-launch audit. During design review, check color contrast ratios, touch target sizes, and text readability against WCAG criteria. During development, require that automated accessibility checks (axe-core in CI, Lighthouse audits) pass before merging. During QA, include manual keyboard navigation testing and screen reader testing (VoiceOver on Mac, NVDA on Windows) in your usability testing protocol. The WCAG Quick Reference (w3.org/WAI/WCAG22/quickref) is the best starting point for understanding which criteria apply to your product. Start with Level AA conformance and treat each criterion as a user story in your backlog. Use the decision matrix approach to prioritize which accessibility gaps to address first based on severity and affected user population.