What is WCAG 2.1 Level AA?

WCAG 2.1 Level AA is a set of accessibility success criteria published by the W3C at https://www.w3.org/WAI/WCAG21/. Level AA is the conformance level most regulators and courts reference. The Department of Justice has treated it as a functional benchmark for Title III compliance even without formal regulation mandating it for private businesses.

Does my small business legally have to meet WCAG 2.1 AA?

There is no federal regulation that mandates WCAG 2.1 AA for private businesses today. In practice, plaintiff firms, courts, and the DOJ use WCAG 2.1 AA as the de facto compliance benchmark under Title III of the ADA. A business that meaningfully conforms to WCAG 2.1 AA on revenue-carrying pages has a strong defensive position.

Which WCAG 2.1 AA criteria come up most often in ADA demand letters?

Five dominate the automated scanner findings: images without alt text (1.1.1), links without descriptive text (2.4.4), form inputs without labels (1.3.1 and 4.1.2), color contrast below 4.5:1 (1.4.3), and missing or incorrect heading structure (1.3.1 and 2.4.6). Fixing these removes you from the scanner lists plaintiff firms use.

How do I test my website for WCAG 2.1 AA?

Three-step minimum viable audit. Run axe DevTools or WAVE on your revenue-carrying pages. Tab through those same pages with keyboard only. Use NVDA or VoiceOver to confirm a screen reader can complete key flows. Zero critical findings from all three passes is meaningful compliance for the purposes of most demand letters.

Compliance Basics

WCAG 2.1 AA Requirements for Small Business Websites

WCAG 2.1 Level AA is the standard most ADA demand letters cite. Here is the plain-English version of what small businesses actually have to do.

Published by Startvest LLC SDVOSBApril 15, 20267 min read

WCAG 2.1 Level AA is the standard almost every ADA website demand letter cites. It is also the standard most small business owners have never read.

This article gives you the plain-English version. Not all of WCAG. Just the parts that come up in Title III demand letters, organized by where the violations usually are.

What WCAG is, in one paragraph

The Web Content Accessibility Guidelines are a set of success criteria published by the World Wide Web Consortium. WCAG 2.1 is the most current commonly-cited version. Level AA is the conformance level most regulators and most courts reference. WCAG 2.1 AA is the standard the Department of Justice has treated as a functional benchmark even though DOJ has not formally adopted a regulation mandating it for private businesses.

WCAG is organized around four principles. Perceivable. Operable. Understandable. Robust. The success criteria under each principle tell you how to make your site satisfy that principle.

The violations that show up in demand letters

Automated scanners flag a small subset of WCAG criteria reliably. This small subset is what most demand letters cite. Fixing these reduces your exposure more than any other single effort.

Images without alt text

WCAG 1.1.1 Non-text Content. Every image that conveys information needs an alt attribute describing it. Decorative images get alt="". A carousel with six promotional images without alt text is six violations in one scan.

Fix. Audit your image inventory. For each image, either write an alt that describes what the image says or means, or mark it as decorative with an empty alt.

Links without descriptive text

WCAG 2.4.4 Link Purpose. "Click here" and "Read more" violate this when the link target is not clear from context. A screen reader user navigating by links hears a list of "read more, read more, read more" with no context.

Fix. Every link's text should describe what happens when you click it. If the design requires "Read more," add a visually-hidden span that describes the specific destination.

Form inputs without labels

WCAG 1.3.1 Info and Relationships, and 4.1.2 Name, Role, Value. Every input needs a programmatically associated label. A form with a checkout flow that uses placeholder text as a visual label is almost always a violation.

Fix. Every input gets a <label for="id"> or an aria-label. Placeholder text is not a label substitute. This is one of the most common findings.

Color contrast failures

WCAG 1.4.3 Contrast Minimum. Text must have a contrast ratio of at least 4.5 to 1 against its background for normal-size text, and 3 to 1 for large text. Designers love light gray text on white. It is almost always a violation.

Fix. Run a contrast checker on your site. Raise the darkness of any text that fails. This is the WCAG criterion with the highest signal-to-noise ratio in automated scans.

Missing or incorrect heading structure

WCAG 1.3.1 and 2.4.6 Headings and Labels. Every page needs a logical heading hierarchy. H1 for the page title. H2 for sections. H3 inside H2 sections. Skipping levels, using headings for visual styling, or omitting the H1 are all findings.

Fix. Your page template enforces heading structure. Do not use headings as a styling tool. Use them to describe structure.

Keyboard-only inoperability

WCAG 2.1.1 Keyboard and 2.4.7 Focus Visible. Every interactive element must be operable with a keyboard. The focus state must be visible. A custom dropdown that only responds to mouse, or a focus ring that has been styled away with outline: none, are both violations.

Fix. Tab through your entire site without a mouse. You should be able to complete every transaction. Every focused element should show a visible ring. If a designer has removed the focus ring, restore it.

WCAG 2.4.1 Bypass Blocks. Every page needs a way to skip the navigation and jump to the main content. Usually implemented as a link that appears on keyboard focus.

Fix. Add a "skip to content" link as the first focusable element on the page. Have it hidden until focused.

The ones that do not show up in automated scans but appear in demand letters

Some WCAG criteria cannot be scanned automatically. Plaintiff declarations sometimes cite them anyway. Preparing for these is part of a thorough compliance effort.

Content that changes without user action

WCAG 2.2.2 Pause, Stop, Hide. Auto-playing carousels, auto-rotating testimonials, background animations. If content moves or updates on its own for more than five seconds, users need a way to pause or stop it.

Fix. Add a pause control to any auto-moving content. Or make it move slowly enough that five seconds elapse before the first automatic change.

Error identification in forms

WCAG 3.3.1 Error Identification and 3.3.3 Error Suggestion. A form that rejects input must explain what went wrong and how to fix it. A checkout that returns "Invalid input" without specifying which field and what rule it violated is a finding.

Fix. Every form error is text. Every error identifies the field. Every error suggests how to correct. Errors are programmatically associated with their fields using aria-describedby or similar.

Video without captions

WCAG 1.2.2 Captions. Every prerecorded video needs captions. Live video needs them as well at AA level.

Fix. Captions on every video. If your video is hosted on YouTube and you use auto-generated captions, review and correct them. Auto-generated captions alone are usually not enough.

Language declaration

WCAG 3.1.1 Language of Page. The <html> element needs a lang attribute. It is a one-character fix that is missing on a surprising number of sites.

Fix. <html lang="en"> on every page. If your site supports multiple languages, set the attribute dynamically.

What WCAG does not require

Some common misconceptions.

It does not require a separate accessible version of your site. A "view accessible version" link is usually a sign of a site that would rather not do the real work.

It does not require an accessibility overlay widget. Overlays do not satisfy WCAG and do not satisfy the ADA.

It does not require fonts of a specific size. It requires contrast and scalability. Text should reflow when zoomed to 200%. That is separate from base font size.

It does not require captions on every audio file. Captions at AA level apply to video. Audio-only content has different criteria, mostly around transcripts.

How to know if you are passing

A three-step minimum viable audit. For the priority-ordered checklist of exactly which criteria to test, see our free WCAG 2.1 AA checklist.

Run axe DevTools or WAVE on the pages that handle your primary business transactions. Homepage. Contact page. Checkout. Whatever the key pages are. Save the reports.
Tab through those same pages with a keyboard only. Note every place you get stuck or lose the focus ring.
Turn on a screen reader — NVDA on Windows is free — and work through the same pages. Listen for unlabeled form fields, images without alt text, and headings that do not match structure.

If all three passes produce zero critical findings, you are meaningfully compliant for the purposes of most demand letters. If any pass produces critical findings, fix them and document the fix in a remediation log — see the full documentation checklist for the complete record-keeping framework.

The realistic target

A site that is one hundred percent WCAG 2.1 AA conformant on every page of every state does not exist. Not at Google. Not at Amazon. Not at any site you have ever used.

The realistic target is this. Your revenue-carrying pages pass automated scans with zero critical findings. Keyboard users can complete a purchase. Screen reader users can find the checkout and submit a form. Your accessibility statement is honest about what you do and do not support. Your remediation log shows ongoing work.

If those four things are true, you have a defensible position. That is what WCAG 2.1 AA actually requires of a small business in practice.

Your accessibility statement is the public-facing half of this. Use the accessibility statement template as a starting point — one that does not overpromise.

This is not legal advice. For compliance questions specific to your business, consult a licensed attorney.

Get the documentation a judge will ask for.

Nine documents that courts have accepted as good-faith effort. With owner, review cadence, and fillable fields.

One email. The download link. No newsletter until you opt in.

Don't want to share your email? Read the template online →

Frequently asked questions

What is WCAG 2.1 Level AA?: WCAG 2.1 Level AA is a set of accessibility success criteria published by the W3C at https://www.w3.org/WAI/WCAG21/. Level AA is the conformance level most regulators and courts reference. The Department of Justice has treated it as a functional benchmark for Title III compliance even without formal regulation mandating it for private businesses.
Does my small business legally have to meet WCAG 2.1 AA?: There is no federal regulation that mandates WCAG 2.1 AA for private businesses today. In practice, plaintiff firms, courts, and the DOJ use WCAG 2.1 AA as the de facto compliance benchmark under Title III of the ADA. A business that meaningfully conforms to WCAG 2.1 AA on revenue-carrying pages has a strong defensive position.
Which WCAG 2.1 AA criteria come up most often in ADA demand letters?: Five dominate the automated scanner findings: images without alt text (1.1.1), links without descriptive text (2.4.4), form inputs without labels (1.3.1 and 4.1.2), color contrast below 4.5:1 (1.4.3), and missing or incorrect heading structure (1.3.1 and 2.4.6). Fixing these removes you from the scanner lists plaintiff firms use.
How do I test my website for WCAG 2.1 AA?: Three-step minimum viable audit. Run axe DevTools or WAVE on your revenue-carrying pages. Tab through those same pages with keyboard only. Use NVDA or VoiceOver to confirm a screen reader can complete key flows. Zero critical findings from all three passes is meaningful compliance for the purposes of most demand letters.
Do I need perfect WCAG 2.1 AA conformance?: No site has it. Not Amazon, not Google, not the DOJ. The realistic target is this: your revenue-carrying pages pass automated scans with zero critical findings, keyboard users can complete a purchase, screen reader users can find the checkout, and your accessibility statement is honest. Those four are defensible.