011 min
Why buyers ask for WCAG 2.1 AA
Picture a team that sells a booking tool for public swimming pools. A city wants to buy it, and the purchase form asks one question: does the product conform to WCAG 2.1 AA? Nobody on the team has read the standard, and the form does not explain it.
The city asks because of a rule from the United States Department of Justice. The rule makes WCAG 2.1 Level AA the technical standard for the web content and mobile apps of state and local governments.
The department published the rule in April 2024, and a later interim rule moved the deadlines. Governments with a population of 50,000 or more must comply by 26 April 2027, and smaller ones by 26 April 2028. The city passes this duty on to every supplier, which is why the form asks. The team now has to learn what the label means and how anyone checks it.
Content the rule leaves out
The rule has exceptions. Old web content is exempt only when all four of these conditions hold: it predates the compliance date, it is kept only for reference, it sits in a special archive area, and nobody has changed it since it was archived. The team's booking pages are in daily use, so no exception covers them.
022 min
What the name WCAG 2.1 AA means
The label has three parts. WCAG stands for Web Content Accessibility Guidelines, written by a working group of the W3C, the body that sets web standards. The number 2.1 is the version, published in June 2018. The letters AA are a conformance level.
Each rule in the guidelines is a success criterion: a statement that a tester can mark as met or not met. The criteria sit under four principles. Content must be perceivable, operable, understandable and robust.
The levels stack. Level AA means a page meets all the Level A criteria and all the Level AA criteria. In version 2.1 that is 30 criteria at Level A and 20 at Level AA, so 50 in total. Level AAA adds 28 more.
| Level | Criteria in 2.1 | What it adds |
|---|---|---|
| A | 30 | The basics without which some people cannot use a page at all, such as text for images and keyboard operation |
| AA | 20 | Contrast, zoom, consistent navigation, error help and the criteria added for mobile and low vision |
| AAA | 28 | The strictest rules, such as a contrast ratio of 7 to 1 |
W3C advises against requiring Level AAA for a whole site, because some content cannot meet every AAA criterion. AA is the level most laws and buyers name.
A conformance claim is the maker's own statement
The standard describes conformance claims as optional. A claim that a product conforms is the maker's own statement about its pages, so a buyer can ask for the evidence behind it.
032 min
How a page conforms to WCAG 2.1 AA
The team's next question is what gets tested. The standard sets five requirements for a conforming page.
- Level. The page meets every Level A and Level AA criterion, or offers a conforming alternate version.
- Full pages. Conformance applies to whole pages, including every responsive version.
- Complete processes. Every page in a multi-step process must conform.
- Accessibility-supported technology. Only ways of using technology that work with assistive technology count.
- Non-interference. Technology that does not support accessibility must not block the rest of the page.
One failing step fails the whole process
For the swimming-pool tool, a booking is a process with three pages: choose a session, enter details, pay. The standard says that when a page is one of a series presenting a process, all the pages in the process must conform at the stated level. Its own example is an online store, where every page from product selection to checkout must conform. If the payment page fails one criterion, none of the three booking pages can be called conforming at AA, even though the first two are clean.
Every screen size counts
A responsive page shows a different layout on a phone and on a desktop screen. Each layout is part of the page, so each must meet AA. A pass on the desktop view says nothing about the phone view.
Technology has to work with assistive tools
The fourth requirement is called accessibility support. A way of using a technology counts only if it works with assistive technology such as screen readers, and if browsers that support it are widely available. Plain HTML and CSS meet this test. A custom date picker built from unlabeled shapes may not.
041 min
What WCAG 2.1 added to the AA list
Version 2.0, from 2008, had 38 criteria at Levels A and AA. Version 2.1 added 12 more for those two levels, as part of 17 new criteria across all three levels. The working group aimed them at people with cognitive or learning disabilities, people with low vision, and people who use mobile devices. Seven of the new criteria sit at Level AA.
| Criterion | What it asks |
|---|---|
| 1.3.4 Orientation | Do not lock content to portrait or landscape unless one is essential |
| 1.3.5 Identify Input Purpose | Mark fields that collect personal details so software can fill them in |
| 1.4.10 Reflow | Content fits a width of 320 CSS pixels without scrolling in two directions |
| 1.4.11 Non-text Contrast | The parts of controls and graphics that people need to see have a ratio of 3 to 1 |
| 1.4.12 Text Spacing | Nothing is lost when a user widens line, paragraph, letter and word spacing |
| 1.4.13 Content on Hover or Focus | Pop-up content can be dismissed, can be hovered over, and stays until dismissed |
| 4.1.3 Status Messages | Messages such as a booking confirmation reach assistive technology without moving focus |
The next sections take these in the order a booking flow meets them.
052 min
The older AA criteria in plain words
Thirteen of the 20 AA criteria come from version 2.0, and the team may already follow some of them.
| Criterion | What it asks |
|---|---|
| 1.2.4 Captions (Live) | Live audio in video has captions |
| 1.2.5 Audio Description (Prerecorded) | Prerecorded video describes what is shown but not said |
| 1.4.3 Contrast (Minimum) | Text has a contrast ratio of at least 4.5 to 1 |
| 1.4.4 Resize Text | Text can grow to 200% without loss of content or function |
| 1.4.5 Images of Text | Use real text instead of pictures of text, with few exceptions |
| 2.4.5 Multiple Ways | A set of pages can be found in more than one way |
| 2.4.6 Headings and Labels | Headings and labels describe their topic or purpose |
| 2.4.7 Focus Visible | Keyboard focus can be seen |
| 3.1.2 Language of Parts | Passages in another language are marked |
| 3.2.3 Consistent Navigation | Repeated navigation keeps the same order |
| 3.2.4 Consistent Identification | The same function has the same name everywhere |
| 3.3.3 Error Suggestion | When the fix for an error is known, the page says it |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Important submissions can be reversed, checked or confirmed |
A page must also meet all 30 Level A criteria. They cover text alternatives for images, captions for prerecorded video, keyboard operation with no trap, skipping repeated blocks, page titles and language, color not used alone, identified errors, input labels, no dangerous flashing, adjustable time limits and switchable single-key shortcuts.
062 min
Contrast in WCAG 2.1 AA
The designer of the booking tool chose light gray for the hint text inside the form fields. Contrast is the first thing most audits measure, and criterion 1.4.3 Contrast (Minimum) sets the rule. Text needs a contrast ratio of at least 4.5 to 1 against its background. Large text needs 3 to 1.
How the ratio is calculated
The ratio compares the brightness of the two colors. Each color has a relative luminance, a number from 0 for the darkest black to 1 for the lightest white. The ratio is (L1 + 0.05) / (L2 + 0.05), where L1 is the luminance of the lighter color and L2 the luminance of the darker one. It runs from 1 to 1 for identical colors up to 21 to 1 for black on white.
Run the formula on the designer's choices. Gray #767676 on white gives about 4.54 to 1, which passes. Gray #777777, one step lighter, gives about 4.48 to 1 and fails. The hint color #999999 gives about 2.85 to 1, far below the limit.
What counts as large text
Large text means 18 point, or 14 point and bold. The standard warns that a font with very thin strokes may need more contrast than the minimum.
Controls and graphics
Criterion 1.4.11 applies a ratio of 3 to 1 to things that are not text: the edges of input fields, icons and the parts of a chart that a person needs in order to understand it. A pale gray outline on a text field can pass 1.4.3 for its label and still fail 1.4.11 for the field itself.
071 min
How often real pages miss WCAG 2.1 AA
If the swimming-pool team's first scan finds problems, that is not unusual. Every year WebAIM, an accessibility organization, tests the home pages of the top one million websites with an automated engine. Its February 2026 run found WCAG 2 failures on 95.9% of home pages. Low contrast text, below the AA limit, was the most common failure, found on 83.9% of pages and 34 times per page on average.
WebAIM tests against WCAG 2.2 A and AA, a set that contains nearly all of 2.1 AA. A scan counts only failures that a program can detect, so the share of pages that fully conform is certainly lower than the 4.1% that had no detected failure.
082 min
Zoom, reflow and text spacing in WCAG 2.1 AA
A city staff member with low vision opens the booking page and zooms the browser to 400%. Three criteria decide whether the page still works.
Criterion 1.4.4 Resize Text, from version 2.0, asks that text can grow to 200% without loss of content or function. Criterion 1.4.10 Reflow, new in 2.1, goes further: content must fit a width of 320 CSS pixels without scrolling in two directions. Criterion 1.4.12 Text Spacing asks that nothing is lost when a user changes the spacing of text.
Why 320 pixels
The number comes from zoom. A browser window 1280 CSS pixels wide, zoomed to 400%, shows a layout 320 CSS pixels wide. So a page that reflows at 320 works for a person who zooms to 400% on an ordinary laptop. Content that scrolls sideways at this size forces a reader to move back and forth along every line.
Data tables may scroll in two directions
The session grid in the booking tool is a table of pools against days. A grid like this cannot be read in one narrow column, so the standard excepts content that needs two-dimensional layout, such as data tables, maps and diagrams. The exception covers only the table. The team puts the session table in its own scrolling box, so the text around it can still reflow. W3C shows the failure too: a table placed directly in the page gives the whole page two scroll bars.
092 min
Keyboard use and focus in WCAG 2.1 AA
Next the team tries the whole booking flow without a mouse. Level A already requires that every function works from the keyboard and that focus never gets stuck. Level AA adds criterion 2.4.7 Focus Visible: a keyboard user must be able to see which element has focus.
The GOV.UK Design System, the UK government's component library, shows an applied answer. In it, a focused link has a yellow background and a black border along its bottom edge, and a focused form input has a yellow outline and a thick black border. Yellow stands out on dark backgrounds and black on light ones, so the indicator meets the 3 to 1 rule for non-text contrast on every background GOV.UK uses.
Pop-up content on hover or focus
The booking tool shows a tooltip when a person hovers over or focuses a lane-pass label. Criterion 1.4.13 sets three conditions for such content. A person can dismiss it without moving the pointer or focus. The pointer can move onto it without it vanishing. It stays visible until the person dismisses it or the trigger is removed.
A hidden focus still needs a check
Say the booking page keeps a cookie banner fixed to the bottom of the screen. A person pressing Tab down the form reaches a field, and the banner covers it. Version 2.1 has no criterion that names this case. Version 2.2 added one, 2.4.11 Focus Not Obscured (Minimum), which says a focused component must not be entirely hidden by content the author created.
Status messages
After payment the page shows a booking confirmation line. A screen reader user hears nothing if the line appears without moving focus and has no role or property that assistive technology watches. Criterion 4.1.3 requires that such messages can be identified in code, so assistive technology can announce them without taking focus.
101 min
Forms and errors in WCAG 2.1 AA
The pay page is a form. Level A requires a label or instruction on every input and an error identified in text. Level AA adds Error Suggestion: when the page knows how to fix an error, it says so.
Autofill
Criterion 1.3.5 Identify Input Purpose asks that fields collecting personal details are marked so a browser can fill them from a stored profile.
Payments need one of three safeguards
The pay page also falls under criterion 3.3.4, error prevention for legal and financial submissions. It applies to pages that create legal commitments or financial transactions, change or delete stored data, or submit test answers. Such a page must meet at least one of three conditions. The submission can be reversed. The data is checked and the person can correct it. Or the person can review, confirm and correct everything before the final step. For the booking tool, a summary page before payment satisfies the third.
111 min
Testing for WCAG 2.1 AA
The team adds an automated checker to its build and gets zero errors. Can it now answer yes on the city's form? Not on that evidence. In 2017 the UK Government Digital Service built a page with 143 deliberate accessibility failures and ran 10 automated tools against it. Of the 143 failures, 42 were missed by every tool.
WebAIM gives the same warning about its own scan: a page with no detected errors is not thereby accessible or conformant. The checks that matter are done by a person:
- Use the whole booking flow with the keyboard only, and check that focus is always visible and never trapped.
- Run it with a screen reader and listen for labels, errors and the confirmation message.
- Zoom to 400% and set the viewport to 320 CSS pixels wide.
- Apply the four text-spacing values from criterion 1.4.12 and look for clipped text.
- Measure the contrast of text, borders and focus indicators in every state.
Teams usually run these checks as an accessibility evaluation before each release and record the result for each criterion. That record is what a buyer's form is really asking for.
121 min
Wrong readings of WCAG 2.1 AA
An overlay does not make a site conform
Some vendors sell a script that promises conformance from one line of code. The US Federal Trade Commission took action against one of them, accessiBe. The company had claimed that its line of code made a site 30% compliant at once and that an AI process made the rest compliant within 48 hours. The commission found the claims unsubstantiated. The order makes accessiBe pay $1 million and bars it from saying that software alone can make a website meet WCAG.
Conforming does not mean everyone can use it
A page can meet every AA criterion and still frustrate someone. The working group says so itself: version 2.1 advances guidance for cognitive, low vision and mobile needs, but not all user needs are met by the guidelines. Inclusive design starts from the people who use a product, so testing with disabled users catches problems no criterion names.
131 min
How WCAG 2.1 AA became a legal reference
WCAG 2.0 appeared in December 2008. Version 2.1 followed in June 2018, and its authors described it as an interim step while the group worked on a larger rewrite.
In Robles v. Domino's Pizza, a blind customer sued because he could not order a pizza from the company's website and app with screen-reading software. Domino's argued that being held to WCAG would violate due process, because the Department of Justice had never said which standard applied. In January 2019 the Ninth Circuit court of appeals held that the ADA covers the website and app. A court may require a company to follow WCAG 2.0 as a remedy if its site and app are found to violate the ADA.
The 2024 rule ended that uncertainty for public bodies by naming a version and a level. It covers state and local governments. It does not name a standard for private businesses, where courts and settlements still use WCAG as the yardstick.
141 min
WCAG 2.1 AA compared with WCAG 2.2 AA
WCAG 2.2, published in October 2023, adds 9 criteria and keeps every 2.1 criterion unchanged, except that 4.1.1 Parsing is now obsolete. Because 2.2 only adds, a page that meets 2.2 AA also meets 2.1 AA. Six of the new criteria count toward AA conformance: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum) and 3.3.8 Accessible Authentication (Minimum) at Level AA, and 3.2.6 Consistent Help and 3.3.7 Redundant Entry at Level A.
ISO/IEC 40500:2025 is identical to the October 2023 version of WCAG 2.2, and the 2026 version of the European standard EN 301 549, which the European Accessibility Act relies on, uses WCAG 2.2. A team that sells in both the US and Europe can cover both by meeting 2.2 AA.
Small targets
The sharpest practical gap is button size. WCAG 2.1 has only a Level AAA criterion for target size, 2.5.5, which asks for 44 by 44 CSS pixels. WCAG 2.2 added 2.5.8 at Level AA, which asks for targets of at least 24 by 24 CSS pixels unless an exception applies. So a 2.1 AA page can pass with small, tightly packed buttons, such as Cancel placed beside Submit.
151 min
WCAG 2.1 AA vs nearby concepts
People use these terms as if they meant the same thing. The one axis that separates them is what each one is: a testable list, a goal, a law or a wider standard.
| Term | What it is | How it differs from WCAG 2.1 AA |
|---|---|---|
| Accessibility | The broad goal of making products usable by people with disabilities | WCAG 2.1 AA is one measurable standard inside that goal |
| WCAG 2.2 AA | A later version of the same guidelines | Adds six criteria and keeps all of 2.1 |
| ADA Title II rule | A US rule for state and local governments | Names WCAG 2.1 AA as its technical test |
| Section 508 | A US rule for federal agencies | In 2019 a court noted agencies using WCAG 2.0 Levels A and AA |
| EN 301 549 | A European standard for digital products | Covers more than web content, and its 2026 version uses WCAG 2.2 |
161 min
Applying WCAG 2.1 AA in a design process
The team answers the city's form with a plan.
Set the target in writing.
Name the version and level the buyer uses, and the version the team tests against.
Put the numbers in the design system.
Store text and border colors with their measured ratios, one focus style and a minimum target size, so every screen starts from a passing state.
Design for zoom first.
Check each layout at 320 CSS pixels wide before adding wide layouts.
Test every release by hand.
Use the keyboard, a screen reader, zoom and text spacing, and record the result for each criterion.
Keep a list of known gaps
with an owner and a date for each.
Checking the criteria only at the end of a project turns each one into a late redesign.
The decision to take to the buyer: say which version and level the product meets today, which criteria it does not yet meet, and the date it will. A dated list of gaps is more useful to a buyer than an unsupported yes.
?4 questions
Questions people ask
Does WCAG 2.1 AA apply to mobile apps?
Do PDFs and other documents need to meet WCAG 2.1 AA?
Can a page pass by offering a separate accessible version?
What does it mean to say a site is partly conformant?
§12 sources
Sources
Show all 12 sourcesHide sources
W3C, "Web Content Accessibility Guidelines (WCAG) 2.1", W3C Recommendation, 5 June 2018, republished 6 May 2025.
W3C WAI, "WCAG 2 Overview".
W3C WAI, "What's New in WCAG 2.1".
W3C WAI, "What's New in WCAG 2.2".
W3C WAI, "Understanding Success Criterion 1.4.10: Reflow".
US Department of Justice, "Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments", ADA.gov.
US Court of Appeals for the Ninth Circuit, Robles v. Domino's Pizza, LLC, 913 F.3d 898, opinion of 15 January 2019.
WebAIM, "The WebAIM Million: the 2026 report on the accessibility of the top 1,000,000 home pages".
GOV.UK Design System, "Understanding focus state styles".
Government Digital Service, "What we found when we tested tools on the world's least-accessible webpage", 24 February 2017.
Hunton Andrews Kurth, "AI company required to pay $1 million for falsely touting capabilities of web accessibility solution", a law firm's summary of the FTC order against accessiBe.
Accessible.org, "WCAG 2.1 AA Guide for Beginners or Experts (Plain English)".





