Web Accessibility Standards: The Current List Worth Bookmarking
The standards that actually matter (and the ones that don't anymore)
Accessibility standards change, and most resource lists online do not keep up. It is common to find pages still linking to 2021 working drafts of WCAG and ARIA that were finalized or replaced years ago. This is the current set we work from at Graceful Web Studio, checked and dated, so you can bookmark it with confidence. Every link here points to the live version of the document.
The core standard: WCAG 2.2
If you read only one thing on this page, make it this section. WCAG 2.2 is the benchmark for accessible web content, and Level AA is the target we build to on every project.
WCAG 2.2
WCAG 2.2 became a W3C Recommendation in October 2023, was updated in December 2024, and was adopted as an international standard (ISO/IEC 40500:2025) in October 2025. It adds nine success criteria to WCAG 2.1, covering focus visibility, target size, alternatives to dragging, consistent help, and accessible authentication. One older criterion, 4.1.1 Parsing, was removed.
How to Meet WCAG (Quick Reference)
The working version of the standard. You can filter the success criteria by level and technology, and each one links to techniques and common failures. This is the document we keep open during a build.
Understanding WCAG 2.2
Plain-language explanations of the intent behind each criterion, with examples. The place to go when you need to know not just what a rule says but why it exists.
WCAG 2 Overview
A short orientation to the WCAG family and how the versions relate. WCAG 2.0, 2.1, and 2.2 are all still valid standards. 2.2 is the latest and the one to use.
A note on WCAG 3.0
Worth knowing about, not worth building to yet. WCAG 3.0 (also called the W3C Accessibility Guidelines) is an early Working Draft with a new scoring model. It is years away from becoming a standard, and the W3C is clear that WCAG 2.2 remains the current benchmark. We track it. We do not test against it. If a resource tells you to build to WCAG 3.0 today, that resource is ahead of the standard.
ARIA and semantic structure
ARIA fills the gaps that plain HTML cannot, mostly for custom, interactive components. The first rule of ARIA still holds: use a native HTML element before you reach for ARIA.
WAI-ARIA Overview
The starting point. It explains what ARIA is, the suite of related documents, and when you actually need it.
WAI-ARIA 1.2
The current ARIA specification, a W3C Recommendation since June 2023. It defines the roles, states, and properties that tell assistive technology what a custom component is and what it is doing.
ARIA Authoring Practices Guide (APG)
This shows how to build common patterns (menus, tabs, dialogs, carousels) accessibly, with working examples and keyboard interaction maps. It replaces the older Authoring Practices notes and is the reference we reach for whenever a design calls for a custom component.
Open the ARIA Authoring Practices Guide
ARIA in HTML
The rulebook for using ARIA correctly inside HTML, including which roles and attributes are allowed where. It backs up that first rule: reach for a native element first.
Authoring tools and your CMS
ATAG 2.0
Guidelines for making content authoring tools accessible, both for authors with disabilities and for helping every author produce accessible content. This matters when you choose or build a CMS, because the editing interface itself should be usable by everyone. A W3C Recommendation since 2015.
Designing for everyone
Standards tell you what to meet. Universal and inclusive design tell you how to think so you meet them by default. These resources move accessibility upstream into the design phase, which is where it is cheapest and most effective to get right.
The 7 Principles of Universal Design
The foundation of designing for everyone. Developed in 1997 by Ronald Mace and a team at NC State, the seven principles (equitable use, flexibility in use, simple and intuitive use, perceptible information, tolerance for error, low physical effort, and size and space for approach) reach well beyond architecture and still guide good digital design today.
Microsoft Inclusive Design
A practical, free toolkit built around three ideas: recognize exclusion, learn from diversity, and solve for one to extend to many. The activity cards and guidebooks make it easy to bring inclusive thinking into a real design process.
Explore Microsoft Inclusive Design
Inclusive Design Principles
Seven principles written specifically for the web by the team now at TPGi: provide comparable experiences, consider situation, be consistent, give control, offer choice, prioritize content, and add value. A clear bridge between the rules and everyday design decisions.
Read the Inclusive Design Principles
Accessibility, Usability, and Inclusion
A short read from the W3C on how accessibility, usability, and inclusion overlap and differ. Useful for explaining to a client why accessible design helps everyone, not only people with disabilities.
How People with Disabilities Use the Web
Stories and examples of real people using assistive technology. The single best resource for building empathy and understanding why the standards exist in the first place.
Web Accessibility Perspectives (videos)
Ten short videos showing how accessibility features are essential for some people and useful for everyone, from captions to keyboard access. Good to share with a team or a hesitant client.
How these standards connect to SEO, AEO, and revenue
These are not just rules to satisfy. The same semantic structure a screen reader relies on is the structure search engines and AI answer engines use to understand your pages. Clear headings, real landmark regions, descriptive links, and correct ARIA make your content easier to crawl, easier to summarize, and easier to rank. Captions and alt text serve people with disabilities and give search engines content they can index. Building to WCAG 2.2 Level AA widens the audience that can actually use your site, which is the most direct line there is from accessibility to revenue.
Staying current
Standards move, and a lot of accessibility resource lists never get updated. When in doubt, the W3C technical reports index always points to the current version of any document. We re-check this list so the links here stay accurate.
Browse the W3C technical reports index
Build it in from the start
Knowing the standards is one thing. Applying them across a real site is another. We build WCAG 2.2 Level AA conformance into every project from day one, and we offer accessibility remediation and consulting for sites that need to catch up. If you want to know where your site stands, reach out for a quote or a free homepage evaluation.
Written by Crystal Scott, CPWA and Certified Webflow Expert at Graceful Web Studio
Your Website Deserves Better, Let's Team Up
We would love to meet with you face-to-face. Whether virtually or for a coffee. Book a call, and let’s find the right solution for you! We review your site, map goals, and then deliver a clear plan and quote.
