What Is a Website Accessibility Audit and What Can Automated Testing Find?

A website accessibility audit evaluates whether people with disabilities can perceive, navigate, understand, and operate a website. Automated testing can reliably flag some code-based problems, including missing alternative text, insufficient color contrast, unlabeled controls, and heading errors. However, it cannot determine full WCAG conformance or ADA compliance. A meaningful evaluation also requires keyboard, screen-reader, zoom, form, and user-journey testing.

By Sebastian Pincetti, Partner, Digital Marketing Specialist, and AI Developer at SRP Communication & Brand Design. Published October 1, 2026. Last updated October 10, 2026.

Your next step: get started with SRP's free online Website Accessibility Audit for an automated home-page baseline. Then contact SRP if you need help interpreting the findings or planning broader manual testing.

What Is a Website Accessibility Audit?

A website accessibility audit is a structured evaluation of barriers that can prevent people with disabilities from using a website. A complete audit combines automated checks with manual review of representative pages, templates, and interactive components. It also tests important tasks such as finding information, completing a form, making a purchase, or contacting the business.

This guide is built for business owners, CEOs, managers, and marketing decision makers at companies with approximately 5 to 250 employees.

Why Does Website Accessibility Matter to a Business?

Website accessibility matters to a business because customers need to reach information, products, services, and support regardless of how they see, hear, move, or process information. Accessible design can reduce frustration, improve usability, and help more people complete important tasks.

However, accessibility barriers are still common. In 2026, detected WCAG 2 failures appeared on 95.9 percent of one million home pages, according to WebAIM (2026). In our own data, low color contrast was the most common issue, affecting 67 percent of the sites we scanned, according to SRP (212 scans, May to September 2026).

Legal responsibilities also matter. Businesses open to the public must provide people with disabilities equal access to the goods and services they offer, including online, according to U.S. Department of Justice guidance (2026). However, legal obligations depend on the organization, jurisdiction, and facts, so technical findings should not be treated as legal advice.

What Can Automated Accessibility Testing Find?

Automated accessibility testing can find objective problems that software can identify consistently on the home page or pages included in the scan. Common checks include the following.

• Alternative-text errors. The scan can identify images that lack an alt attribute, although it cannot decide whether existing alternative text is useful or accurate.
• Color-contrast failures. The scan can calculate whether supported text and background combinations meet defined contrast thresholds.
• Missing accessible names. The scan can flag links, buttons, form fields, and other controls that do not expose a usable name to assistive technology.
• Heading and document-structure errors. The scan can identify missing headings, multiple or empty headings, skipped levels, absent page-language attributes, and some landmark problems.
• Certain HTML and ARIA errors. The scan can detect some invalid roles, prohibited attributes, duplicate identifiers, and relationships that are missing in the code.

However, automated test rules are partial checks, according to W3C (2026). So passing a rule means the tool did not detect that specific failure. It does not mean the page satisfies every part of the related WCAG success criterion.

What Can Automated Accessibility Testing Not Determine?

Automated accessibility testing cannot determine whether the complete experience is understandable and usable. Human judgment is required for issues that depend on meaning, sequence, interaction, or context.

• Alternative-text quality. A tool may confirm that alt text exists but cannot reliably judge whether it communicates the image's purpose in context.
• Keyboard usability. A person must verify focus order, visible focus, keyboard traps, menus, dialogs, and whether every important task can be completed without a mouse.
• Screen-reader experience. Manual testing is needed to confirm announcements, reading order, status messages, form instructions, and changes in dynamic content.
• Form recovery and instructions. A reviewer must determine whether errors are clearly explained and whether users can correct them successfully.
• Media quality and complex content. Software cannot reliably confirm the accuracy of captions, transcripts, audio descriptions, charts, maps, PDFs, and other context-dependent content.
• Real task completion. Only human testing can show whether a person can understand the experience and complete an important journey without unnecessary barriers.

How Do Automated Scanning, Manual Review, and User Testing Differ?

Automated scanning, manual expert review, and user testing answer different questions. A responsible accessibility program uses each method for the work it can perform best.

Does Passing an Automated Audit Mean a Website Is ADA Compliant?

Passing an automated audit does not mean a website is ADA compliant. An automated score only reports the rules and pages the tool tested. It does not cover every WCAG criterion, every page, every user journey, or the legal facts that determine an organization's obligations.

However, private businesses and government entities should not be treated as one legal category. The detailed web rule for state and local governments adopts WCAG 2.1 Level AA, according to U.S. Department of Justice rules (2024 and 2026). Its compliance dates fall in April 2027 or April 2028, depending on population and entity type. Private businesses open to the public remain subject to the ADA's general requirements. The Department's current business guidance does not prescribe one detailed web standard for every Title III website.

What Does the SRP Accessibility Score Mean?

The SRP accessibility score summarizes the automated checks performed on the submitted website's home page. A higher score means the scan detected fewer of the tested code-based problems. Unlike accessibility overlay widgets, which add a layer on top of a page, the audit points to the code that needs to be fixed. The score does not certify the home page, represent the entire website, or prove WCAG or ADA compliance.

How Does a Complete Accessibility Review Work?

A complete accessibility review begins with automated testing and then expands into human evaluation, in six steps. The scope should reflect the website's risk, complexity, templates, content types, and most important user journeys.

1. Step 1, define the scope: List critical pages, templates, forms, documents, media, and tasks. Include authenticated areas and mobile experiences when relevant.
2. Step 2, run automated checks: Use scanning to find repeatable technical errors and establish a baseline for retesting.
3. Step 3, test without a mouse: Review focus order, keyboard access, menus, dialogs, forms, and visible focus across representative pages.
4. Step 4, test with assistive technology: Use screen readers, zoom, text resizing, and other relevant tools to evaluate content and interactions.
5. Step 5, prioritize and remediate: Address blockers in critical journeys first, then repair repeated component and template problems.
6. Step 6, retest and maintain: Verify fixes and include accessibility in content, design, development, and quality-assurance workflows.

What Accessibility Problems Should a Business Fix First?

A business should fix problems that block important tasks before addressing lower-impact defects. Priorities depend on the website, but a practical sequence follows.

1. Keyboard blockers and inaccessible forms. Remove keyboard traps, restore focus visibility, label controls, and make errors understandable.
2. Controls without accessible names. Repair buttons, links, menus, and interactive elements that assistive technology cannot identify.
3. Contrast and visual barriers. Correct text contrast, instructions that rely only on color, and content that breaks when enlarged.
4. Informative and functional images. Add accurate alternative text or equivalent accessible information based on the image's purpose.
5. Repeated structural problems. Fix shared headings, landmarks, navigation, templates, and components so one repair improves many pages.

How Can You Check Your Website?

You can check your home page with SRP's free online Website Accessibility Audit. The read-only scan reviews common automated checks and sends a prioritized PDF report by email. Use the result as a baseline, not a compliance certificate. So broader testing is needed for the rest of the website and for issues that require human judgment.

Frequently Asked Questions

What is a website accessibility audit?

A website accessibility audit is a structured review of barriers that can prevent people with disabilities from perceiving content, navigating pages, understanding information, or completing tasks. A complete audit combines automated and manual evaluation.

What can an automated accessibility scan find?

An automated accessibility scan can find specific code-based failures such as missing alternative-text attributes, some contrast problems, unlabeled controls, heading errors, and certain invalid HTML or ARIA patterns.

Can an automated tool certify ADA compliance?

An automated tool cannot certify ADA compliance. Legal compliance depends on the applicable law and facts, while technical conformance requires more evaluation than an automated scan can provide.

Why does SRP's free audit scan only the home page?

SRP's free audit scans the home page to provide a fast baseline for common, detectable problems. A full-site evaluation must examine representative templates, important content, interactive components, documents, and critical user journeys.

How often should a website be tested for accessibility?

A website should be tested after major redesigns, new templates, significant feature releases, or changes to important forms and customer journeys. Automated regression checks can run more frequently, while manual testing should be scheduled periodically and after material changes.

Methodology and Limitations

We built SRP's free Website Accessibility Audit to perform a read-only automated evaluation of the submitted website's public home page. It reviews selected indicators related to alternative text, contrast, headings, accessible names, forms, semantic HTML, and ARIA. The scan does not evaluate every WCAG success criterion, every page, or private content. It also does not cover mobile apps, all downloadable documents, or the lived experience of every user.

W3C's WCAG 2.2 provides current technical accessibility guidance. However, the Department of Justice's Title II web rule for state and local governments specifically references WCAG 2.1 Level AA. The article provides general educational information, not legal advice or certification.

About the Author

Primary Sources

• World Wide Web Consortium. Web Content Accessibility Guidelines 2.2. Accessed October 2026.
• World Wide Web Consortium. Understanding Test Rules for WCAG 2.2 Success Criteria. Accessed October 2026.
• World Wide Web Consortium. WCAG Evaluation Methodology 2.0. Accessed October 2026.
• U.S. Department of Justice. Guidance on Web Accessibility and the ADA. Accessed October 2026.
• U.S. Department of Justice. New Rule on the Accessibility of Web Content and Mobile Apps. Accessed October 2026.
• WebAIM. The WebAIM Million 2026. Accessed October 2026.