U.S. Accessibility Testing for Small Websites: WCAG 2.2 Without False Compliance Claims

The Web Content Accessibility Guidelines (WCAG) 2.2 are technical standards published by the World Wide Web Consortium (W3C) that define how to make web content more accessible to people with disabilities. WCAG 2.2 is the current version, published in October 2023, and it builds upon WCAG 2.1 by adding new success criteria that address barriers for users with cognitive disabilities and users with visual impairments on mobile devices.

In the United States, WCAG 2.2 has become the de facto legal standard for web accessibility through a combination of existing legislation and regulatory guidance. Title III of the Americans with Disabilities Act (ADA) prohibits discrimination on the basis of disability in places of public accommodation, and courts have consistently held that websites and mobile applications are places of public accommodation. The Department of Justice (DOJ) has also issued guidance affirming that WCAG 2.1 Level AA is the appropriate standard for web accessibility under the ADA.

While the ADA does not explicitly mention WCAG, the DOJ's guidance and the consistent pattern of court decisions have made WCAG 2.1 Level AA (and increasingly WCAG 2.2 Level AA) the expected standard for businesses that want to minimize their legal risk. In recent years, there has been a significant increase in ADA-related lawsuits targeting small business websites that are alleged to be inaccessible to people with disabilities. These lawsuits often seek injunctive relief (requiring the business to make its website accessible) and attorneys' fees.

The Three Levels of WCAG Compliance

WCAG 2.2 organizes accessibility guidelines into three levels of conformance: Level A, Level AA, and Level AAA. Understanding these levels is essential for businesses that want to implement the right level of accessibility for their needs.

Level A represents the minimum level of accessibility. Meeting Level A criteria ensures that some of the most basic barriers to accessibility are removed. For example, providing text alternatives for non-text content, ensuring that keyboard navigation works for all functionality, and avoiding content that flashes more than three times per second. Level A alone is generally not considered sufficient for legal compliance in the United States.

Level AA is the standard that most businesses aim for. It includes all Level A criteria plus additional requirements that address the most common barriers for people with disabilities. Level AA requirements include sufficient color contrast for text, text resizing up to 200 percent without loss of content or functionality, and consistent navigation across web pages. The DOJ's guidance specifically references WCAG 2.1 Level AA as the appropriate standard, and Level AA is the target level for most accessibility audits and lawsuits.

Level AAA represents the highest level of accessibility. AAA criteria are not required for general compliance and may not be applicable to all websites. For example, AAA requires sign language interpretation for all pre-recorded audio content, which may not be practical for a small business website. Attempting AAA compliance can be expensive and may create accessibility barriers in other areas if implemented incorrectly.

Automated vs. Manual Testing

Accessibility testing involves both automated tools and manual evaluation. Understanding the strengths and limitations of each approach is essential for businesses that want to achieve genuine compliance without wasting resources.

Automated testing tools scan web pages for accessibility issues using predefined rulesets. These tools are fast, inexpensive, and can catch many common accessibility problems. Popular automated tools include WAVE (Web Accessibility Evaluation Tool) by WebAIM, axe DevTools browser extension, Google Lighthouse accessibility audit, and Siteimprove Accessibility Checker. Automated tools are excellent for identifying missing alt text, low color contrast, empty form labels, and missing heading structures. They can scan entire websites quickly and provide actionable reports.

However, automated tools have significant limitations. They can only detect approximately 30-40% of accessibility barriers. Automated tools cannot evaluate keyboard navigation, screen reader compatibility, the accessibility of interactive components, the clarity of link text, the logical order of content, or the accessibility of dynamic content. A website that passes all automated accessibility checks may still be completely unusable for people with disabilities. This is a critical distinction that many businesses misunderstand when they rely solely on automated testing results for compliance claims.

Manual testing involves evaluating the website using assistive technologies such as screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, and other accessibility tools. Manual testing also includes reviewing the website against the WCAG success criteria and evaluating the user experience for people with various disabilities. Manual testing catches the 60-70% of accessibility barriers that automated tools miss.

The most effective accessibility testing strategy combines automated tools for initial scanning and continuous monitoring with manual testing for deeper evaluation. A typical testing workflow involves running automated tools to identify and fix the easy problems, then conducting manual testing with screen readers and keyboard navigation to identify more complex issues.

Free Accessibility Testing Tools for Small Business Owners

Several free tools are available that can help small business owners evaluate and improve the accessibility of their websites without paying for expensive consulting services.

WAVE (Web Accessibility Evaluation Tool) is a free browser extension and online tool developed by WebAIM at Utah State University. WAVE provides visual feedback about accessibility issues directly on the web page, using icons and color coding to indicate errors, alerts, and features. The browser extension is available for Chrome, Firefox, and Edge, and the online version allows you to test any public URL. WAVE is particularly useful for identifying missing alt text, empty links, low contrast, and structural issues.

axe DevTools is a free browser extension from Deque Systems that integrates accessibility testing directly into the browser's developer tools. axe DevTools tests against WCAG 2.1 Level A and Level AA rules, provides detailed issue descriptions with suggested fixes, and includes guides for common accessibility problems. The extension is available for Chrome, Firefox, and Edge, and it works with single-page applications and dynamic content.

Lighthouse is built into Chrome's Developer Tools and provides an accessibility audit as part of its overall performance and quality assessment. Lighthouse scores accessibility on a scale of 0-100 based on weighted WCAG criteria. While Lighthouse is not as detailed as WAVE or axe, it provides a quick overview of accessibility health and is useful for monitoring improvements over time.

Practical Accessibility Checklist for Small Business Owners

For small business owners who cannot afford professional accessibility audits, the following checklist provides a practical starting point for improving website accessibility.

Content and Structure:

• Provide text alternatives for all non-text content (images, icons, videos)Use heading elements (h1-h6) in a logical order to structure contentUse semantic HTML elements (nav, main, article, aside) instead of generic divsEnsure all interactive elements are keyboard accessibleProvide skip navigation links for keyboard usersUse descriptive link text that makes sense out of context (avoid "click here")

Visual Design:

• Ensure text and background have sufficient color contrast (minimum 4.5:1 for normal text, 3:1 for large text)Do not use color as the only visual means of conveying informationEnsure the website is usable when zoomed to 200%Provide text resizing options

Forms and Interactions:

• Label all form inputs with associated labels or aria-labelsIdentify and describe all form errorsEnsure error messages are specific and helpfulProvide instructions for completing formsEnsure time limits can be extended or turned off

Multimedia:

• Provide captions for all pre-recorded video contentProvide audio descriptions for video content when visual information is importantProvide transcripts for audio content

Navigation:

• Ensure all pages have descriptive titlesEnsure consistent navigation across all pagesProvide multiple ways to find content (search, navigation menu, site map)Ensure focus indicators are visible for keyboard navigation