WCAG SERIES BEGINNERS
Post 1: WCAG 508 Introduction Post 3: WCAG & Section 508 Post 4: POUR Principles Post 5: WCAG Success Criteria Post 6: Accessibility Enforcement Post 7: Bringing It All Together Post 8: WCAG & Section 508 Toolkit
The Evolution of Web Accessibility
Web accessibility did not appear fully formed. It has evolved over more than two decades in response to new technologies, broader understanding of disability, and changing legal expectations. This post traces that journey so you can see why today’s standards look the way they do.
WCAG 1.0 (1999) — The First Standard
When the World Wide Web Consortium published WCAG 1.0 in May 1999, the web was still young and mostly text-and-image based. The guidelines focused heavily on making content usable by people who were blind or had low vision.
Core ideas included:
- Providing text alternatives for images
- Making pages navigable without a mouse
- Using structural markup (headings, lists) so screen readers could make sense of the page
WCAG 1.0 was groundbreaking, but it was tightly tied to the HTML of its era and did not anticipate the explosion of JavaScript, mobile devices, or richer media that would follow.
WCAG 2.0 (2008) — The POUR Foundation
Nine years later, WCAG 2.0 introduced the four principles that still define the standard today: Perceivable, Operable, Understandable, and Robust (POUR).
This version was deliberately technology-agnostic. Instead of prescribing specific HTML techniques, it defined outcomes that could be met with any technology. It also expanded beyond visual disabilities to address a wider range of barriers.
WCAG 2.0 Level A and AA became the technical foundation for Section 508 in the United States and for many other national and international laws.
WCAG 2.1 (2018) — Mobile and Cognitive Needs
By 2018 the web had moved firmly onto phones and tablets. WCAG 2.1 added 17 new success criteria that addressed:
- Touch target size and spacing
- Orientation and reflow on small screens
- Better support for users with low vision and cognitive disabilities
- Additional requirements for motion and animation
These additions made the standard far more relevant to modern web and mobile applications while remaining fully backward-compatible with WCAG 2.0.
WCAG 2.2 (2023) — Further Cognitive and Authentication Improvements
WCAG 2.2 was published on 5 October 2023. It added nine new success criteria, most of them focused on reducing cognitive load and improving authentication and navigation for people with disabilities. Notable additions include:
- Accessible authentication (reducing reliance on memorizing passwords)
- Focus appearance and focus not obscured
- Dragging movements and target size enhancements
- Consistent help and redundant entry
Like 2.1, version 2.2 is fully backward-compatible. Meeting WCAG 2.2 Level AA also satisfies 2.1 and 2.0 requirements.
Looking Ahead: WCAG 3.0
Work continues on WCAG 3.0 (sometimes called “Silver”). Early drafts suggest a more flexible scoring model, broader coverage of emerging technologies (including immersive and voice interfaces), and language intended to be more approachable for non-specialists. It is not yet a final standard and is not required by any current regulation. Organizations should continue targeting WCAG 2.1 or 2.2 Level AA until WCAG 3.0 is finalized and adopted.
Why This History Matters
Understanding the evolution helps you make better decisions today:
- Section 508 still references WCAG 2.0, but meeting 2.1 or 2.2 satisfies that requirement.
- The DOJ’s Title II rule for state and local government websites explicitly names WCAG 2.1 Level AA.
- Many private-sector and international requirements are moving toward WCAG 2.2.
Choosing the right version is less about chasing the newest number and more about matching the legal and practical needs of your organization while keeping the door open for future updates.
Key Takeaway
WCAG has grown from a set of recommendations focused mainly on visual access into a mature, technology-neutral framework that addresses a wide range of disabilities across devices. The core POUR principles have remained stable since 2008, which is why investments in accessibility made under older versions still carry forward.
In the next post we compare WCAG and Section 508 side by side so you can see exactly where they overlap and where they differ in practice.
Next in the series: WCAG vs Section 508
Start Your Compliance Journey Today
Speak with a DHS Certified Trusted Tester about securing your Proof of Compliance Certificate (POCC). Learn how to ensure your digital assets confidently meet state, federal, and enterprise procurement requirements under ADA Title II & III, WCAG 2.2, and Section 508 Standards.
MonkeyHub
- Aticles & News — Evolving insights on digital accessibility legislation, design practices, and corporate risk mitigation from beginner to enterprise scale. Articles & News
- Learning Center —
- MonkeySupport — Have an Accessibility Question? Submit a Ticket and our team will see how we can help. Support Ticket