WCAG 2.1 Checklist for Small Business Websites
You have heard that your website needs to meet WCAG standards, but reading through the official Web Content Accessibility Guidelines feels like decoding a technical specification written for engineers (because, frankly, it is). The WCAG 2.1 documentation spans dozens of pages of success criteria, techniques, and failure conditions that can leave even web developers scratching their heads. Small business owners need something different: a clear, practical checklist that explains what each requirement actually means, why it matters, and exactly what you need to do about it. That is what this guide delivers. We have translated every Level AA requirement into plain language and organized them into a step-by-step checklist you can work through systematically.
Understanding the WCAG Framework
Before diving into the checklist, a brief orientation helps you understand how the guidelines are organized and what "Level AA" actually means.
WCAG 2.1 organizes its guidelines around four principles, often remembered by the acronym POUR.
Perceivable. Users must be able to perceive the information presented. Content cannot be invisible to all of their senses.
Operable. Users must be able to operate the interface. Components and navigation must be functional.
Understandable. Users must be able to understand the information and operation of the interface.
Robust. Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.
Each principle contains guidelines, and each guideline contains testable success criteria. These criteria are organized into three conformance levels.
Level A. The minimum level. Failing to meet Level A means your website has fundamental barriers that prevent some users from accessing content at all.
Level AA. The standard target for most websites and the level referenced in most legal and regulatory requirements. Meeting Level AA means your website is accessible to the vast majority of users with disabilities.
Level AAA. The highest level. While aspirational, Level AAA is not typically required or realistic as a universal standard. Some criteria are relevant to specific industries or use cases.
For your small business website, Level AA compliance is the target. This includes all Level A criteria plus the additional Level AA criteria. Our guide to making your website accessible provides detailed implementation instructions for many of these requirements.
Perceivable: Content Users Can Access
The first principle ensures that all users, regardless of their abilities, can perceive the content on your website.
Text Alternatives (Guideline 1.1)
Non-text content needs text alternatives. Every image, icon, chart, and other non-text element that conveys information needs alternative text that serves the same purpose. This is the single most common accessibility failure and one of the easiest to fix.
Checklist items:
All informational images have descriptive alt text. Product photos, infographics, charts, diagrams, and other meaningful images need alt text that describes what the image conveys. "Red running shoe with mesh upper and white sole" is useful. "Image" or "photo123.jpg" is not.
Decorative images have empty alt attributes. Images that are purely decorative (background patterns, visual dividers, stock photos used for aesthetics) should have alt="" so screen readers skip them entirely.
Complex images have extended descriptions. Charts, graphs, infographics, and other complex images need either long alt text or an adjacent text description that conveys the same data and information.
Form inputs have associated text labels. Every input field (text boxes, dropdowns, checkboxes, radio buttons) needs a programmatically associated label that describes its purpose.
CAPTCHA provides alternatives. If you use CAPTCHA, provide at least two different modalities (visual and audio, for example) and describe what the CAPTCHA requires.
Time-Based Media (Guideline 1.2)
Audio and video content needs alternatives. People who cannot hear need text alternatives for audio. People who cannot see need descriptions of important visual content.
Checklist items:
Pre-recorded audio has transcripts. Podcasts, audio clips, and other recorded audio content need text transcripts.
Pre-recorded video has captions. All video content with dialogue or narration needs synchronized closed captions.
Pre-recorded video has audio descriptions (where needed). If important visual information is not conveyed through the audio track (for example, on-screen text or visual demonstrations), audio descriptions should be provided. This is a Level AA requirement.
Live audio has captions. If you broadcast live audio content (webinars, live streams), real-time captions should be provided. This is a Level AA requirement.
Adaptable Content (Guideline 1.3)
Content structure is programmatically determinable. The visual structure of your content (headings, lists, tables, form fields) must also be represented in the underlying code so assistive technologies can interpret it.
Checklist items:
Headings use proper HTML heading tags. H1, H2, H3, and so on should be used in order to create a logical document structure. Do not use heading tags for styling purposes, and do not skip heading levels.
Lists use proper list markup. Unordered lists use ul/li tags. Ordered lists use ol/li tags. Definition lists use dl/dt/dd tags. Do not simulate lists with line breaks and dashes.
Tables use proper table markup. Data tables need proper header cells (th), caption elements, and scope attributes. Do not use tables for page layout.
Form fields are grouped logically. Related form fields (like address fields) should be grouped using fieldset and legend elements.
Content order is meaningful. The reading order of content in the underlying HTML should match the logical reading order. Content that visually appears in a certain order but is coded in a different order confuses screen reader users.
Orientation is not restricted. Your website should work in both portrait and landscape orientations. Do not lock the display to a single orientation unless it is essential for the content (like a piano keyboard application).
Input purpose is identified. For input fields that collect personal information (name, email, phone, address), use the autocomplete attribute to identify the purpose. This helps browsers and assistive technologies auto-fill forms accurately.
Distinguishable Content (Guideline 1.4)
Users can easily distinguish content. Content should be presented in ways that make it easy for all users to see and hear.
Checklist items:
Color is not the only visual means of conveying information. If you use color to indicate something (red for errors, green for success), also use text, icons, or other non-color indicators. Color-blind users cannot rely on color alone.
Audio control is available. If any audio plays automatically for more than 3 seconds, provide a way to pause, stop, or control the volume.
Text contrast meets minimum ratios (Level AA). Regular text needs at least a 4.5:1 contrast ratio with its background. Large text (18pt or 14pt bold) needs at least 3:1. This applies to all text, including text on buttons, links, form labels, and image overlays.
Text can be resized up to 200 percent. Users should be able to zoom text to 200 percent without loss of content or functionality. Nothing should get cut off, overlap, or become unusable.
Images of text are avoided. Use actual text instead of images of text whenever possible. If images of text are used, they should be customizable or essential to the information being conveyed (such as a logo).
Content reflows at 320px width (Level AA). When the viewport is reduced to 320 CSS pixels wide, content should reflow into a single column without requiring horizontal scrolling. This is essentially a responsive design requirement that benefits both accessibility and mobile usability.
Non-text contrast meets minimum ratios (Level AA). User interface components (buttons, form field borders, icons) and graphical objects essential to understanding content need at least a 3:1 contrast ratio.
Text spacing can be overridden (Level AA). Users should be able to adjust line height, paragraph spacing, letter spacing, and word spacing without loss of content or functionality.
Content on hover or focus is dismissible (Level AA). If pointing to or focusing on an element triggers additional content (tooltips, pop-ups), the user must be able to dismiss the new content, move to the new content, and the content should remain visible until dismissed or no longer relevant.
Operable: Interfaces Users Can Navigate
The second principle ensures that all users can operate your website's interface components and navigation.
Keyboard Accessible (Guideline 2.1)
Everything works with a keyboard. All functionality must be operable through a keyboard interface. This is critical for users who cannot use a mouse due to motor disabilities, visual impairments, or other conditions.
Checklist items:
All interactive elements are keyboard accessible. Links, buttons, form fields, menus, sliders, tabs, accordions, and all other interactive elements must be reachable and operable using only the keyboard (Tab, Shift+Tab, Enter, Space, Arrow keys, Escape).
No keyboard traps exist. Users must never get "stuck" in a component where they cannot move focus away using the keyboard. If a component requires non-standard keyboard interaction to exit, the user must be informed of the method.
Character key shortcuts can be reconfigured (Level AA). If your website uses single character key shortcuts (like "S" for search), users must be able to turn them off, remap them, or they should only be active when the relevant component has focus. This prevents conflicts with assistive technologies.
Enough Time (Guideline 2.2)
Users have enough time. Content should not impose time limits that prevent users with disabilities from completing tasks.
Checklist items:
Time limits are adjustable. If any activity has a time limit (session timeouts, timed forms), users must be able to turn off, adjust, or extend the time. Provide a warning at least 20 seconds before time expires and allow the user to extend.
Moving content can be paused. Any content that moves, blinks, or scrolls for more than 5 seconds (carousels, animations, auto-scrolling text) must have a mechanism to pause, stop, or hide it.
No content flashes more than 3 times per second. Flashing content can trigger seizures. Ensure no content flashes more than three times per second.
Navigable (Guideline 2.4)
Users can find content and know where they are. Navigation should be consistent, logical, and provide clear orientation cues.
Checklist items:
A skip navigation link is provided. A "skip to main content" link at the top of each page allows keyboard users to bypass repetitive navigation.
Pages have descriptive titles. Each page's title element uniquely and clearly describes the page's purpose and content.
Focus order is logical. When navigating with the keyboard, focus moves through elements in an order that preserves meaning and operability.
Link purpose is clear from context. Link text should describe where the link goes. Avoid generic links like "click here" or "read more" without surrounding context that clarifies the destination. Use descriptive link text like "read our accessibility guide" or "view pricing details."
Multiple ways to find pages. Users should have more than one way to locate pages on your website, such as a navigation menu, search function, site map, or table of contents.
Headings and labels are descriptive. Headings and labels should clearly describe the topic or purpose of the content they introduce.
Focus is visible. When an element receives keyboard focus, there must be a visible indicator (typically an outline or highlight) that shows which element is focused. Never remove the default focus outline without providing an alternative that is equally visible.
Input Modalities (Guideline 2.5)
Users can operate content through various input methods. Beyond mouse and keyboard, content should work with touch, voice, and other input methods.
Checklist items:
Pointer gestures have alternatives. If your website uses multi-point or path-based gestures (pinch to zoom, swipe), provide single-pointer alternatives (buttons) for the same functionality.
Pointer cancellation is supported. For single-pointer actions, at least one of the following is true: the down-event does not trigger the action, the action is triggered on the up-event with the ability to abort, the up-event reverses the down-event, or completing the action on the down-event is essential.
Labels match accessible names. If a button or element has visible text, the accessible name (what a screen reader reads) must contain that visible text.
Motion actuation has alternatives. If content can be operated by device motion (shaking, tilting), provide an equivalent user interface control, and allow users to disable motion actuation to prevent accidental activation.
Understandable: Content Users Can Comprehend
The third principle ensures that users can understand both the content and how the interface operates.
Readable (Guideline 3.1)
Content is readable and understandable. The text content should be written and coded in ways that maximize comprehension.
Checklist items:
Page language is set. The primary language of each page is identified in the HTML (lang="en" for English). This allows screen readers to use the correct pronunciation.
Language changes are identified (Level AA). If your page includes text in a different language (a French phrase, a Spanish testimonial), mark those sections with the appropriate lang attribute.
Predictable (Guideline 3.2)
The website behaves predictably. Users should not encounter unexpected changes in context or behavior.
Checklist items:
Focus does not trigger unexpected changes. When an element receives focus, it should not automatically change the page context (navigate to a new page, open a new window, submit a form).
Input does not trigger unexpected changes. Changing a form setting (selecting a dropdown option, checking a checkbox) should not automatically trigger a context change unless the user is warned beforehand.
Navigation is consistent. Navigation elements that appear on multiple pages should appear in the same order and position on every page.
Components are identified consistently. Elements that serve the same function across your website should be identified consistently. If your search icon is a magnifying glass on one page, do not use binoculars on another page.
Input Assistance (Guideline 3.3)
Users are helped to avoid and correct mistakes. Forms and interactive elements should minimize errors and make correction easy.
Checklist items:
Errors are identified. When an input error is detected, the error is identified and described to the user in text. Do not rely solely on color to indicate errors.
Labels and instructions are provided. When forms require user input, labels and instructions are provided. If specific formats are required (date format, phone number format), include examples or instructions.
Error suggestions are provided (Level AA). When an input error is detected and suggestions for correction are known, provide those suggestions to the user (for example, "Did you mean example@email.com?").
Error prevention for legal and financial data (Level AA). For pages that involve legal commitments or financial transactions, submissions are either reversible, data is checked for errors with an opportunity to correct, or a confirmation step is provided before final submission.
Robust: Content That Works with Assistive Technology
The fourth principle ensures that your content works reliably with current and future assistive technologies.
Compatible (Guideline 4.1)
Content is compatible with assistive technologies. Your HTML and interactive elements should be coded in ways that assistive technologies can interpret accurately.
Checklist items:
HTML is well-formed. Elements have complete start and end tags, are nested properly, do not contain duplicate attributes, and have unique IDs. Validate your HTML to catch structural errors.
Name, role, and value are provided. For all user interface components, the name, role, and current state are programmatically determinable. Custom widgets and interactive elements need appropriate ARIA attributes. Standard HTML elements (buttons, links, form fields) already provide this information when used correctly.
Status messages are announced. When a status message appears (like "item added to cart," "form submitted successfully," or "3 errors found"), it should be communicated to screen reader users through ARIA live regions without moving focus.
Testing Your Website Against This Checklist
Working through this checklist systematically is the most effective way to evaluate and improve your website's accessibility. Here is a practical testing approach.
Phase 1: Automated Scanning
Run your website through automated accessibility testing tools. These tools catch the easy-to-detect issues and give you a starting point.
WAVE browser extension. Test each key page of your site. Pay attention to errors (red flags) and alerts (yellow flags). WAVE provides clear explanations and references for each issue it identifies.
axe DevTools browser extension. Provides detailed technical information about accessibility issues, including the specific WCAG success criteria that are violated.
Google Lighthouse. Run an accessibility audit from Chrome's developer tools. The score provides a quick benchmark, but focus on the individual issues listed rather than the overall number.
Automated tools typically identify 30 to 40 percent of all accessibility issues. They excel at finding missing alt text, contrast issues, missing form labels, and structural problems. They cannot evaluate the quality of alt text, the logic of heading structures, or the usability of keyboard navigation.
Phase 2: Keyboard Testing
Put your mouse aside and navigate your website using only the keyboard.
Press Tab to move forward through interactive elements. Use Shift+Tab to move backward. Press Enter to activate links and buttons. Use Space to toggle checkboxes and buttons. Use Arrow keys to navigate within menus, radio groups, and tab panels. Press Escape to close modal dialogs.
As you navigate, check that every interactive element is reachable, that focus indicators are visible, that focus order is logical, and that no keyboard traps exist.
Phase 3: Screen Reader Testing
Testing with a screen reader provides the most authentic assessment of how users with visual impairments experience your website. VoiceOver (built into macOS and iOS) and NVDA (free for Windows) are the most commonly used screen readers.
Listen to how your page content is read. Does the heading structure make sense? Are images described appropriately? Do form fields have clear labels? Are interactive elements identified correctly? Can you complete all key tasks?
Phase 4: Visual Inspection
Review your website visually with accessibility in mind.
Check text contrast with a tool like the WebAIM Contrast Checker. Zoom your browser to 200 percent and verify that all content remains usable. View your site in grayscale to check for color-only information. Resize your browser window to 320 pixels wide and check that content reflows without horizontal scrolling.
Maintaining Compliance Over Time
Accessibility is not a one-time fix. Your website changes constantly, and each change can introduce new accessibility issues. For small businesses using the website security best practices approach, accessibility maintenance fits naturally into your regular site maintenance routine.
Add accessibility to your content publishing checklist. Before publishing any new page, post, or product listing, verify: images have alt text, headings follow a logical hierarchy, links have descriptive text, form fields have labels, and color contrast is sufficient.
Test after every design change. New themes, layout changes, and redesigns frequently introduce accessibility issues. Run automated tests and keyboard tests after any visual changes.
Schedule quarterly audits. Run automated tools across your key pages quarterly. Address any new issues promptly.
Document your accessibility policy. Create an accessibility statement for your website that describes your commitment, the standards you target, and how users can report issues. This demonstrates good faith and provides a feedback channel.
Stay current with standards. WCAG evolves. WCAG 2.2 was published in 2023, and WCAG 3.0 is in development. Follow the Web Accessibility Initiative (WAI) at w3.org/WAI for updates.
Quick Reference Summary
Here is a condensed reference you can keep handy during audits and content creation.
Images. All meaningful images have descriptive alt text. Decorative images have empty alt attributes.
Video. All videos have captions. Video-only content has audio descriptions where needed.
Audio. All audio content has transcripts.
Color. Information is never conveyed by color alone. Text contrast is at least 4.5:1 (3:1 for large text).
Text. Text can be resized to 200 percent. Content reflows at 320px wide. Proper heading hierarchy is used.
Keyboard. All interactive elements are keyboard accessible. No keyboard traps. Focus indicators are visible.
Forms. All fields have labels. Errors are described in text. Suggestions are provided when possible.
Navigation. Skip navigation link exists. Page titles are descriptive. Focus order is logical. Navigation is consistent.
Language. Page language is declared. Language changes within content are marked.
Timing. Time limits are adjustable. Auto-playing content can be paused. No content flashes more than 3 times per second.
Compatibility. HTML is valid. Custom widgets have proper ARIA attributes. Status messages are announced to screen readers.
This checklist may seem extensive, but most small business websites only need to address a subset of these criteria based on the types of content and functionality they include. Start with the areas most relevant to your site, fix the highest-impact issues first, and work through the remaining items systematically. Accessibility is a journey, not a destination, and every improvement you make benefits real people trying to use your website.