The Ultimate Website Accessibility Testing Checklist for 2026
The Ultimate Website Accessibility Testing Checklist for 2026
Understanding the Foundations of a WCAG 2.0 AA Checklist
A WCAG 2.0 AA checklist is the structured set of 38 success criteria your website must meet to conform to Level AA of the Web Content Accessibility Guidelines — the standard referenced by the ADA, Section 508, and most other accessibility laws worldwide.
Here’s a quick reference of the core WCAG 2.0 AA checklist categories:
| Principle | Key AA Requirements |
|---|---|
| Perceivable | Alt text, captions, 4.5:1 contrast ratio, text resize to 200% |
| Operable | Keyboard access, skip links, visible focus, adjustable time limits |
| Understandable | Page language, consistent navigation, error suggestions, form labels |
| Robust | Valid semantic markup, name/role/value for UI components |
These 38 criteria build on the Level A foundation — together they form the complete AA conformance requirement that courts and regulators look for when evaluating ADA compliance.
WCAG 2.0 was released in 2008 and remains the baseline standard that nearly every accessibility law references. And while newer versions (2.1 and 2.2) add more criteria on top, meeting WCAG 2.0 AA is still the minimum benchmark for avoiding legal exposure.
I’m Matthew Post, web developer and accessibility specialist with nearly 30 years of experience building and auditing websites — and co-founder of WCAG Pros, where I’ve personally overseen hundreds of WCAG 2.0 AA checklist audits and remediations for businesses facing exactly this kind of legal pressure. Below, I’ll walk you through every requirement you need to know.
When we talk about a WCAG 2.0 AA checklist, we are diving into a technical standard developed by the World Wide Web Consortium (W3C). Think of WCAG as the “building code” for the internet. Just as a physical store needs ramps and wide aisles, a website needs specific digital features to be usable by everyone.
WCAG is organized into three levels of conformance:
- Level A: The most basic web accessibility features. If you don’t meet these, your site is likely unusable for many people with disabilities.
- Level AA: This is the “Gold Standard.” It includes all Level A criteria plus additional requirements that address the most common barriers for users with vision, hearing, and cognitive impairments. This is the level most often cited in legal settlements.
- Level AAA: The most rigorous level. While admirable, it is often difficult or impossible to achieve for all types of content.
To reach Level AA, you must meet a total of 38 success criteria from the 2.0 version. It’s a bit like a video game—you can’t beat the “AA” level until you’ve cleared all the “A” level hurdles first. If you’re wondering where your site stands, learning how to tell your website is ADA compliant is a great first step. For the official technical deep dive, you can always visit the Web Content Accessibility Guidelines (WCAG) Overview.
The Four POUR Principles Explained
The entire WCAG 2.0 AA checklist is built upon four foundational pillars known as the POUR principles. If your site doesn’t follow these, it’s like trying to bake a cake without flour—something is going to fall flat.
- Perceivable: Information and user interface components must be presentable to users in ways they can perceive. This means users must be able to “see” or “hear” the content (even if they are using a screen reader).
- Operable: User interface components and navigation must be operable. The site shouldn’t require interactions that a user cannot perform (like requiring a mouse for someone who can only use a keyboard).
- Understandable: Information and the operation of the user interface must be understandable. Users need to be able to comprehend the text and know how to use the menus without getting a headache.
- Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. Essentially, your code shouldn’t break when a screen reader tries to read it.
Legal Requirements and Global Standards
Why does everyone care so much about Level AA? Because it’s the law. In the United States, the Department of Justice (DOJ) has made it clear that Title II of the Americans with Disabilities Act (ADA) applies to web content. Furthermore, Section 508 of the Rehabilitation Act requires federal agencies to make their electronic and information technology accessible to people with disabilities, specifically referencing WCAG 2.0 AA.
Internationally, standards like the Accessibility for Ontarians with Disabilities Act (AODA) in Canada also lean heavily on these guidelines. For us at WCAG Pros, helping clients navigate these waters is about legal risk mitigation. A solid WCAG 2.0 AA checklist isn’t just a “nice to have”—it’s a shield against lawsuits. For those running smaller operations, we recommend checking out our ADA Compliance for Small Businesses in 2025: A Complete Guide.
Principle 1: Perceivable Content and Media Requirements
The first principle is all about making sure nothing is “hidden” from a user because of their disability. The biggest heavy hitter here is 1.1.1 Non-text Content. This requires that any non-text content (like images, charts, or icons) has a text alternative.
If you have a picture of a “Golden Retriever playing in the park,” the alt text shouldn’t just be “image123.jpg.” It needs to describe the content. However, if an image is purely decorative (like a swirl in the background), we use a “null alt” (alt="") so screen readers know to skip it. You can find more details on this in our guide on WCAG Guideline 1.1.1 Non-text Content.
Visual and Media Success Criteria for WCAG 2.0 AA Checklist
Media accessibility is where many sites stumble. Under the wcag 2.0 aa checklist, prerecorded video and audio have strict rules:
- Captions (1.2.2): All prerecorded video with audio must have synchronized captions. This isn’t just for the deaf community; it’s for the person watching your video in a noisy coffee shop without headphones, too! See our breakdown of WCAG 1.2.2 Captions (Prerecorded) Explained.
- Audio Description (1.2.3 & 1.2.5): If a video has important visual information that isn’t conveyed in the audio (like a silent scene where a character signs a contract), you need an audio description or a text alternative.
- Live Captions (1.2.4): For AA conformance, even live broadcasts need captions. WCAG 1.2.4 Captions (Live) Explained covers how to handle these real-time requirements.
Another critical AA requirement is 1.4.4 Resize Text. Your website must remain functional and readable even when the text is zoomed to 200%. If your layout “explodes” or text overlaps when someone zooms in, you’ve got a problem. Yale University provides a great WCAG 2 A and AA Checklist that highlights these visual requirements.
Distinguishable Interface Elements
To make content “Distinguishable,” we have to talk about color contrast.
- 1.4.3 Contrast (Minimum): Standard text must have a contrast ratio of at least 4.5:1 against its background.
- Large Text: For larger text (18pt or 14pt bold), the ratio can be 3:1.
We also have to ensure that color isn’t the only way we convey information. If an error message just turns a form field red without adding an icon or text saying “Error,” a colorblind user might never know they missed a spot. Additionally, for those using audio, WCAG 1.2.1 Audio-only and Video-only (Prerecorded) Explained ensures that users have alternatives for media that doesn’t have a visual or audio counterpart.
Principle 2: Operable Interfaces and Site Navigation
If a user can’t move around your site, they can’t buy your products or read your blog. The cornerstone of the Operable principle is 2.1.1 Keyboard Accessibility. Every single link, button, and form field must be reachable and usable using only the Tab key and Enter/Space keys.
We often tell our clients: “Unplug your mouse for ten minutes and try to use your site.” If you get stuck in a “keyboard trap” (where you can get into a menu but can’t get out), you’re failing a major part of the WCAG 2.0 AA checklist. For more common pitfalls, read about 5 Common Accessibility Issues on Small Business Websites and How to Fix Them.
Navigation and Interaction in the WCAG 2.0 AA Checklist
Navigating a site shouldn’t be a marathon.
- Bypass Blocks (2.4.1): You need a “Skip to Main Content” link. This allows keyboard users to jump over the massive header navigation and get straight to the meat of the page.
- Page Titles (2.4.2): Every page needs a unique, descriptive title in the
tag. “Home” isn’t enough; “Home | WCAG Pros Compliance Services” is much better. - Focus Visible (2.4.7): This is a Level AA requirement. When you Tab through a site, there must be a visual “ring” or highlight showing where you are. If the focus indicator is hidden, the user is effectively flying blind.
We also look at Link Purpose (2.4.4). Links like “Click Here” or “Read More” are accessibility nightmares. If a screen reader pulls up a list of links, seeing twenty “Click Here” links provides zero context. Instead, use descriptive text like “Read more about our WCAG remediation services.” For more on media alternatives, check WCAG 1.2.3 Audio Description or Media Alternative (Prerecorded) Explained.
Managing Time Limits and Interruptions
Time limits can be a huge barrier for people with cognitive disabilities or those who use assistive technology slowly. 2.2.1 Timing Adjustable requires that if you have a timeout (like on a bank site), you must give the user a way to turn it off, adjust it, or extend it.
The rule of thumb? Give them at least a 20-second warning before the time runs out and allow them to extend that time at least ten times the default length. There are exceptions for “real-time events” like auctions or competitive gaming, but for most business sites, the user should be in control of the clock. Also, make sure nothing flashes more than three times per second (2.3.1 Three Flashes) to prevent seizures.
Principles 3 & 4: Understandable Design and Robust Systems
| Level A Requirements | Level AA Additions |
|---|---|
| 3.1.1 Language of Page | 3.1.2 Language of Parts |
| 3.2.1 On Focus | 3.2.3 Consistent Navigation |
| 3.2.2 On Input | 3.2.4 Consistent Identification |
| 3.3.1 Error Identification | 3.3.3 Error Suggestion |
| 3.3.2 Labels or Instructions | 3.3.4 Error Prevention (Legal/Financial) |
Making your site “Understandable” means removing the guesswork. It starts with 3.1.1 Language of Page, where you programmatically declare the language (e.g., ). This tells screen readers which accent and dictionary to use.
Level AA also demands Consistent Navigation (3.2.3). If your “Search” button is at the top right on the homepage, it shouldn’t move to the bottom left on the “About Us” page. Consistency is key for users who rely on muscle memory or screen magnification. You can find a full list of these requirements in our ADA Website Compliance 2025 Accessibility Checklist.
Input Assistance and Error Handling
Forms are where the most “user friction” happens. Under 3.3 Input Assistance, we must ensure that forms have clear labels and that errors are easy to fix.
- Error Identification (3.3.1): If a user forgets a field, tell them exactly which one it was in text.
- Error Suggestion (3.3.3): If a user enters a date in the wrong format, provide a suggestion like “Please use MM/DD/YYYY.”
- Error Prevention (3.3.4): For legal or financial transactions, allow the user to review, confirm, or reverse their submission before it becomes final. This is a critical Level AA safety net.
If you find your forms are failing, our WCAG Remediation services can help you fix these code-level issues.
Maximizing Compatibility and Robustness
The “Robust” principle is the developer’s playground. 4.1.2 Name, Role, Value ensures that every interactive component (like a custom-built dropdown menu) has the correct ARIA labels so assistive technology knows what it is and what it’s doing.
While 4.1.1 Parsing (validating HTML) was recently marked as “obsolete” in WCAG 2.2 because browsers have gotten better at handling bad code, it was a staple of the wcag 2.0 aa checklist for years. We still recommend clean, semantic markup because it’s the best way to ensure your site works with future technologies. To see how your current code stacks up, you might consider an Automated Tools Audit, though remember that automated tools only catch about 30-40% of issues!
Frequently Asked Questions about WCAG Conformance
How many success criteria are included in WCAG 2.0 AA?
There are 38 success criteria in the full WCAG 2.0 AA conformance level. This includes 25 criteria from Level A and 13 additional criteria specifically for Level AA. When people ask for a WCAG 2.0 AA checklist, they are looking for this combined set of 38 points that form the baseline for modern digital accessibility.
Is WCAG 2.0 AA still the standard for legal compliance?
Yes. While WCAG 2.1 and 2.2 have been released, WCAG 2.0 AA remains the foundational baseline referenced in major laws like ADA Title II and Section 508. Because WCAG is “backwards compatible,” if you meet the 2.1 or 2.2 standards, you are automatically meeting the 2.0 standard as well. However, 2.0 AA is usually the minimum requirement cited in courtrooms.
What roles are responsible for meeting WCAG 2.0 AA?
Accessibility is a team sport!
- Designers handle color contrast, layout, and focus indicators.
- Developers write the semantic HTML, manage keyboard focus, and implement ARIA roles.
- Content Editors are responsible for alt text, descriptive link text, and video captions. Without all three groups working together, a site will almost always have gaps in its WCAG 2.0 AA checklist.
Conclusion: Implementing Your Accessibility Strategy
Meeting a WCAG 2.0 AA checklist is not a one-and-done project; it’s an ongoing commitment to your users. While automated tools are a great starting point for catching low-hanging fruit, they are no substitute for the real thing.
At WCAG Pros, we believe the only way to be truly sure of your compliance is through a combination of expert manual testing and real-world feedback. We offer comprehensive page-by-page audits of all success criteria, providing you with actual code fixes—not just a list of problems. We even offer free re-audits to ensure you can proudly display your compliance badge.
If you want to see how your site performs in the hands of the people who matter most, check out our guide on How to Test Your Website’s Accessibility Using Real Users. Ready to get serious about your digital inclusivity? Let us help you with a professional WCAG Audit today. We’re based in Norco, CA, and we’re ready to help you make the web a better place for everyone.
Read more website accessibility articles
Get Help With Your Website
We'll follow up with info about:
- The process
- Cost
- Timeline
We promise to respect your privacy, and never abuse the information you provide. We will not sell or rent your information to any third party.
By submitting this form, you consent to receive SMS messages and/or emails from SEM Dynamics LLC, dba WCAG Pros. To unsubscribe, follow the instructions provided in our communications. Msg & data rates may apply for SMS. Your information is secure and will not be sold to third parties.

