Roughly one in six people worldwide lives with a significant disability, and for them an inaccessible interface is not an inconvenience, it is a locked door. WCAG exists so that teams do not have to rediscover accessibility from scratch: it turns decades of research into checkable requirements. WCAG is the closest thing digital accessibility has to a building code.
In this glossary topic:
What is WCAG?
The Web Content Accessibility Guidelines (WCAG) are the international standard for making digital content usable by people with disabilities, covering vision, hearing, motor, and cognitive needs. They are developed by the W3C's Web Accessibility Initiative and organized around 4 principles: content must be perceivable, operable, understandable, and robust. WCAG 2.2 is the current version, and version 3.0 is in long-term development with a broader scoring model.
Why does WCAG matter?
Two reasons, one ethical and one legal. The ethical case is reach: accessible products work for the full audience, including situational limitations every user experiences, from bright sunlight to a broken arm. The legal case is that WCAG is the reference standard behind most accessibility regulation, including the ADA's application to the web in the United States and the European Accessibility Act. Teams rarely get to choose whether WCAG applies to them; they only choose when to find out.
How do teams use WCAG in practice?
In practice WCAG functions as a checklist with three conformance levels, and most organizations target level AA. The guidelines translate directly into design and engineering decisions: color contrast ratios, keyboard navigation, focus states, alt text, and error handling. Mature teams bake the criteria into design reviews and automated testing rather than auditing at the end, since retrofitting accessibility costs multiples of building it in. The Introduction to Accessibility lesson covers how the principles map to everyday design work.
