WCAG 2.1 AA Compliance Checklist for Small Businesses
WCAG 2.1 Level AA has 78 success criteria, and the full specification can feel overwhelming. This checklist cuts through the complexity and focuses on the criteria that matter most for small business websites — the issues most likely to trigger lawsuits and the fixes that have the greatest impact.
Before You Start: Run an Automated Scan
Before working through this checklist manually, run a free automated scan of your website. Automated tools catch approximately 30–50% of WCAG violations instantly, giving you a prioritized starting point. Use this checklist to cover what automated tools miss.
Perceivable: Can Users See and Hear Your Content?
Images and Alt Text (1.1.1)
- Every informational image has descriptive alt text that conveys its purpose.
- Decorative images use empty alt attributes (alt="") so screen readers skip them.
- Complex images (charts, infographics) have extended descriptions either in surrounding text or via aria-describedby.
- Image buttons (like a search magnifying glass) have alt text describing the action, not the image.
Video and Audio (1.2.x)
- Pre-recorded videos have synchronized captions.
- Pre-recorded audio-only content has a text transcript.
- Pre-recorded video has audio description for visual-only information.
Color Contrast (1.4.3, 1.4.11)
- Normal text has a contrast ratio of at least 4.5:1 against its background.
- Large text (18pt or 14pt bold) has a contrast ratio of at least 3:1.
- UI components and graphical objects have at least 3:1 contrast ratio (1.4.11, new in WCAG 2.1).
- Color is never the sole way to convey information (e.g., error fields should not rely on red color alone).
Responsive Design and Reflow (1.4.10)
- Content reflows at 320px width without horizontal scrolling (new in WCAG 2.1).
- Text can be resized up to 200% without loss of content or functionality (1.4.4).
- Text spacing can be adjusted without breaking layout (1.4.12, new in WCAG 2.1).
Operable: Can Users Navigate and Interact?
Keyboard Access (2.1.1, 2.1.2)
- Every interactive element (links, buttons, form fields, menus) is reachable via Tab key.
- No keyboard traps — users can always Tab away from any element.
- Focus order follows a logical, visual reading sequence (2.4.3).
- Focus indicators are visible on all interactive elements (2.4.7).
Navigation and Wayfinding (2.4.x)
- Pages have descriptive, unique title tags (2.4.2).
- A skip-to-content link is available at the top of each page (2.4.1).
- Headings are used properly (h1 through h6) to create a logical outline (2.4.6).
- Link text is descriptive — no “click here” or “read more” without context (2.4.4).
Input Modalities (2.5.x — New in WCAG 2.1)
- Touch targets are at least 44x44 CSS pixels.
- Functionality that uses motion (shake, tilt) has a non-motion alternative (2.5.4).
- Pointer gestures (pinch, swipe) have single-pointer alternatives (2.5.1).
Understandable: Can Users Comprehend Your Content?
Language and Readability (3.1.x)
- The page language is declared in the HTML lang attribute (3.1.1).
- Changes in language within the page are marked with lang attributes (3.1.2).
Forms and Error Handling (3.3.x)
- All form fields have visible labels programmatically associated with the input.
- Required fields are clearly identified before submission.
- Error messages identify the field in error and describe the problem in text (3.3.1).
- Error suggestions provide guidance on how to fix the input (3.3.3).
- Forms that submit legal or financial data can be reviewed, corrected, or reversed (3.3.4).
Robust: Does Your Code Work with Assistive Technology?
- HTML is valid with proper opening and closing tags, no duplicate IDs (4.1.1).
- All custom UI components have appropriate ARIA roles, states, and properties (4.1.2).
- Status messages (success alerts, error notifications) are announced by screen readers without receiving focus (4.1.3, new in WCAG 2.1).
Priority Fixes for Small Businesses
If you cannot address everything at once, focus on these high-impact items first. They represent the violations most commonly cited in ADA lawsuits:
- Missing alt text on images
- Insufficient color contrast
- Missing form labels
- Keyboard navigation failures
- Missing page titles and heading structure
- Missing skip navigation links
Small businesses may also qualify for an ADA tax credit of up to $5,000 to offset the cost of making accessibility improvements.
Keep Your Site Compliant Over Time
Accessibility is not a one-time project. New content, design changes, and plugin updates can reintroduce violations. Set up continuous monitoring to catch regressions automatically and maintain compliance.
Start Your WCAG 2.1 AA Audit
Get an instant report of your website's WCAG 2.1 AA violations with severity ratings and fix guidance. Free, no account required.
Scan Your Website Free