- WCAG
- accessibility
- small business
- ADA compliance
WCAG 2.1 AA Explained for Small Business Owners
A plain-English guide to WCAG 2.1 Level AA: the four POUR principles, what levels A, AA and AAA mean, and real examples of what AA asks for.
On this page
If you have read anything about website accessibility, you have seen the phrase "WCAG 2.1 AA." Web designers say it, scanners report against it, and demand letters sometimes mention it. But what does it actually mean?
This guide explains WCAG in plain English, without the jargon, so you can have a useful conversation with your web person and understand your scan results.
This is not legal advice. WCAG is a technical standard, not a law. How it relates to your legal obligations depends on your situation, so talk to an attorney if you have a specific legal question.
What WCAG is
WCAG stands for the Web Content Accessibility Guidelines. It is published by the World Wide Web Consortium (W3C), the international organization that develops standards for the web.
WCAG is a set of testable rules, called success criteria, for making websites usable by people with disabilities. That includes people who are blind or have low vision, people who are deaf or hard of hearing, and people with motor, cognitive, or learning disabilities. In practice, many of the fixes make sites easier for everyone.
Why small businesses hear about it
For private businesses, the U.S. Justice Department's web accessibility guidance says it "does not have a regulation setting out detailed standards," and points to WCAG as helpful guidance. For state and local governments, the Department's 2024 Title II rule adopted WCAG 2.1 Level AA as the technical standard. That is a big reason WCAG 2.1 AA has become the common benchmark people use. For more on how the ADA applies to businesses, see Does my small business website need to be ADA accessible?
The four principles: POUR
Every WCAG rule falls under one of four principles. The W3C's WCAG 2.1 standard describes them, and they are often remembered by the acronym POUR.
Perceivable
WCAG says: "Information and user interface components must be presentable to users in ways they can perceive."
In plain English: people need to be able to take in your content, whether they see it, hear it, or use a screen reader. That means text descriptions for images, captions for video, and enough contrast to read text.
Operable
WCAG says: "User interface components and navigation must be operable."
In plain English: people need to be able to use your site, including with only a keyboard. Menus, buttons, and forms all need to work without a mouse, and nothing should trap the visitor.
Understandable
WCAG says: "Information and the operation of the user interface must be understandable."
In plain English: your site should be clear and predictable. Pages declare their language, forms explain what they need, and error messages say what went wrong.
Robust
WCAG says content "must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies."
In plain English: your site's code should be built correctly, so browsers, screen readers, and other tools can understand it now and in the future.
What levels A, AA and AAA mean
WCAG groups its success criteria into three levels: A (the lowest), AA, and AAA (the highest). The levels build on each other:
- Level A is the minimum. A page meets Level A when it satisfies all the Level A success criteria.
- Level AA means a page satisfies all the Level A and Level AA success criteria.
- Level AAA means a page satisfies all of A, AA, and AAA.
So "WCAG 2.1 AA" means meeting every Level A and Level AA rule in WCAG version 2.1.
Why not aim for AAA?
The W3C itself says, in the WCAG 2.1 standard, that "it is not recommended that Level AAA conformance be required as a general policy for entire sites," because "it is not possible to satisfy all Level AAA success criteria for some content." That is why AA is the usual target.
Examples of what WCAG 2.1 AA asks for
WCAG 2.1 has dozens of success criteria. Here are some you are likely to run into, translated into plain English. The number is how WCAG refers to each one.
Level A examples (part of AA too)
- 1.1.1 Non-text Content: Images and other non-text content need a text alternative, like alt text.
- 1.2.2 Captions (Prerecorded): Prerecorded videos with sound need captions.
- 1.3.1 Info and Relationships: Structure that you can see (headings, lists, tables, form labels) must also be in the code.
- 2.1.1 Keyboard: Everything must work with a keyboard.
- 2.1.2 No Keyboard Trap: Keyboard users must never get stuck in one part of the page.
- 2.4.1 Bypass Blocks: There should be a way to skip repeated content, like a "skip to main content" link.
- 2.4.2 Page Titled: Every page needs a descriptive title.
- 2.4.4 Link Purpose (In Context): Link text should make clear where the link goes.
- 3.1.1 Language of Page: The page declares its language in the code.
- 3.3.2 Labels or Instructions: Form fields have labels or instructions.
- 4.1.2 Name, Role, Value: Buttons, links, and controls expose a name and role that assistive technology can read.
Level AA examples
- 1.4.3 Contrast (Minimum): Text needs a contrast ratio of at least 4.5:1 against its background, or 3:1 for large text.
- 1.4.4 Resize Text: Text can be zoomed up to 200% without breaking the page.
- 1.4.10 Reflow: Content works on a narrow screen without scrolling sideways (an AA rule added in WCAG 2.1).
- 1.4.11 Non-text Contrast: Buttons, form field borders, and important icons need enough contrast too (also added in 2.1).
- 1.2.4 Captions (Live): Live video with audio needs captions.
- 2.4.6 Headings and Labels: Headings and labels describe the topic or purpose.
- 2.4.7 Focus Visible: Keyboard users can see where they are on the page.
- 3.3.3 Error Suggestion: If a form detects an error and knows how to fix it, it tells the user.
Many of these show up in our list of the 10 most common website accessibility problems, with simple before-and-after code examples.
What about WCAG 2.2?
WCAG 2.2 is the newer W3C Recommendation. It was published on 5 October 2023, and the W3C says it "encourages you to use the latest version of WCAG."
The good news is that it builds on 2.1. According to the W3C, "content that meets WCAG 2.2 also meets WCAG 2.1 and WCAG 2.0." WCAG 2.2 adds nine new success criteria, including these at Level A and AA:
- 2.4.11 Focus Not Obscured (Minimum), AA: Sticky headers or pop-ups shouldn't completely hide the item a keyboard user is on.
- 2.5.7 Dragging Movements, AA: Anything that requires dragging also needs a simpler alternative, like a click.
- 2.5.8 Target Size (Minimum), AA: Buttons and links need to be big enough, or spaced far enough apart, to tap reliably.
- 3.2.6 Consistent Help, A: Help options, like a contact link, appear in a consistent place.
- 3.3.7 Redundant Entry, A: Don't make people type the same information twice in one process.
- 3.3.8 Accessible Authentication (Minimum), AA: Logging in shouldn't depend on a memory or puzzle test without an alternative.
WCAG 2.2 also removed one older criterion, 4.1.1 Parsing, as obsolete. If you are fixing your site now, meeting 2.2 AA covers 2.1 AA as well.
How to check your site against WCAG
- Run an automated scan to catch common, detectable failures. The W3C notes that tools "can not determine accessibility, they can only assist", so a scan is a starting point, not a verdict.
- Test with a keyboard yourself. Try your key pages using only Tab, Shift+Tab, Enter, and Escape.
- Get a manual review from an accessibility professional for your most important pages and flows.
- Keep monitoring as your site changes.
Be wary of any product promising instant WCAG compliance. The FTC took action against one company over exactly that claim; we explain it in Do accessibility overlay widgets make your website ADA compliant?
See how your site measures up
Run a free scan of your homepage to see detectable accessibility problems, explained in plain English. ComplyKit can't certify your site as compliant (no automated tool honestly can), but it can show you where to start.
If you have received an ADA demand letter, read Got an ADA Website Demand Letter? What Small Business Owners Should Do First and talk to an attorney. ComplyKit's Demand Letter Response Kit ($199 one time) includes a full scan of up to 5 pages, a dated PDF report, a fix guide, and 30 days of monitoring, then $29/month. Cancel anytime.