• 15+ Years of Experience
  • Built In-House
  • Official Shopify Select Agency Partners
  • Built in the USA
  • Established in 2011
  • Flexible Support & Maintenance
  • Custom Features
  • Conversion-First Development
  • 15+ Years of Experience
  • Built In-House
  • Official Shopify Select Agency Partners
  • Built in the USA
  • Established in 2011
  • Flexible Support & Maintenance
  • Custom Features
  • Conversion-First Development
  • 15+ Years of Experience
  • Built In-House
  • Official Shopify Select Agency Partners
  • Built in the USA
  • Established in 2011
  • Flexible Support & Maintenance
  • Custom Features
  • Conversion-First Development
  • 15+ Years of Experience
  • Built In-House
  • Official Shopify Select Agency Partners
  • Built in the USA
  • Established in 2011
  • Flexible Support & Maintenance
  • Custom Features
  • Conversion-First Development
  • 15+ Years of Experience
  • Built In-House
  • Official Shopify Select Agency Partners
  • Built in the USA
  • Established in 2011
  • Flexible Support & Maintenance
  • Custom Features
  • Conversion-First Development
  • 15+ Years of Experience
  • Built In-House
  • Official Shopify Select Agency Partners
  • Built in the USA
  • Established in 2011
  • Flexible Support & Maintenance
  • Custom Features
  • Conversion-First Development

How to Conduct an Effective Website Accessibility Audit

Published November 16, 2026 by Bryan Miller | Last updated November 10, 2026

A website accessibility audit is a structured review that combines automated checks, manual testing, and feedback from people with disabilities to identify barriers and plan repairs. A useful audit produces reproducible findings, clear priorities, and a way to verify fixes—not just a scanner score. The process below follows the broad approach of the W3C Website Accessibility Conformance Evaluation Methodology (WCAG-EM): define the scope, select representative content, evaluate it, and report the results.

At Bryt Designs, this is the same process we use when we audit and remediate client websites. On a recent Shopify project for Bates Nut Farm, a focused cycle of audits, manual testing, and theme improvements raised the store’s WAVE accessibility score from 4.9 to 9.5 out of 10, backed by WCAG 2.2 reporting the team can keep using. The steps below reflect what works in practice—and where automated tools fall short.

Key takeaways

  • Scanners are only a starting point. Manual keyboard and assistive technology testing find barriers that automated tools miss.
  • Set the rules first. Define the scope, target standard (typically WCAG 2.2 Level AA), and deliverables before testing begins.
  • Test whole journeys. Evaluate complete processes such as checkout or booking, not just individual pages.
  • Make findings actionable. Turn issues into prioritized, reproducible tickets and retest every fix.
  • Know the limits. An audit is a technical evaluation, not a legal certification.

What do you need before starting an accessibility audit?

Before starting, define the website areas you will evaluate, select an accessibility standard, arrange access to important features, and assign responsibility for testing and repairs. Gather a page inventory, key user journeys, test accounts, and a shared issue tracker. W3C’s methodology emphasizes scope, representative sampling, and evaluation expertise as the foundations of a meaningful review.

Person planning an accessibility audit scope with notes beside a laptop

Choose and document your target WCAG version and conformance level. WCAG 2.2 Level AA is a practical technical target for most improvement work, and W3C recommends WCAG 2.2 when developing or updating accessibility policies. Your applicable requirements may reference a different version, so confirm those separately. Our WCAG compliance guide explains the conformance levels and principles in more detail.

Keep technical testing distinct from ADA compliance. The Americans with Disabilities Act establishes legal obligations, while WCAG provides technical success criteria. An audit is not a legal certification, and your obligations depend on your organization and circumstances. For example, the Department of Justice’s Title II web accessibility rule for state and local governments specifies WCAG 2.1 Level AA, subject to its provisions—see the official ADA.gov web accessibility guidance. For private businesses, our overview of ADA-compliant websites and our website accessibility lawsuits guide cover the wider legal landscape. Seek qualified legal advice when determining your obligations.

Prepare these resources:

  • Access: Test accounts for relevant roles and permission to submit forms or complete transactions safely.
  • Testing tools: An automated checker, contrast checker, browser developer tools, and assistive technology.
  • Documentation: A shared record for evidence, affected components, owners, and retest results.
  • People: Contributors who can evaluate findings and implement content, design, or code changes.

How to conduct a website accessibility audit in eight steps

1. Define the scope and success criteria

Write down the domains, subdomains, languages, documents, and authenticated areas included in the audit. Identify essential tasks, such as requesting help, booking an appointment, or completing checkout. Document third-party services and any exclusions so readers understand the report’s limits.

Agree on the deliverables before testing: a findings register, supporting evidence, a remediation backlog, and a retest summary. Record the audit date and website version where possible. This gives your team a defined starting point instead of an open-ended instruction to “make the site accessible.”

2. Select representative pages and complete journeys

For a large website, select examples of different templates, content types, interactions, and technologies rather than reviewing only popular pages. Include shared navigation, search, forms, media, account areas, and documents where relevant. Add randomly selected pages to help uncover issues outside the planned sample.

Test complete processes, not isolated screens. A checkout review should cover product selection through confirmation, including validation errors and payment interactions. WCAG conformance requirements address complete processes; a working opening page does not establish that the entire journey conforms.

3. Run automated checks and validate the results

Use an evaluation tool that supports your selected standard and testing environment. Check whether it can access authenticated content, inspect dynamic states, and export findings. Tools vary in scope: some inspect individual pages, while others scan groups of pages or entire websites. In our client audits, we use tools such as WAVE to establish a baseline score, then confirm every flagged item by hand.

Review each finding before treating it as confirmed. Separate verified failures from items requiring human judgment, and group repeated findings by their underlying component—one faulty template can generate hundreds of identical errors. Automated tools cannot assess every accessibility requirement and can produce misleading results, so a clean scan is not proof of accessibility. Preserve the report as evidence, not as the final verdict.

4. Test navigation and interactions without a mouse

Person using a computer keyboard to test website navigation without a mouse

Put the mouse aside and complete your key journeys using only the keyboard. Use Tab and Shift+Tab to move between controls, with the appropriate activation and navigation keys for each component. Check that focus remains visible, follows a logical order, and never becomes trapped.

Open menus, dismiss dialogs, operate media controls, and submit forms. Record exactly where progress stops or becomes confusing. For example, “the booking dialog opens, but keyboard focus cannot reach its close button” is more useful than “keyboard problem.” Repeat the interaction from a fresh page load to confirm reproducibility.

5. Review content, visual presentation, and error states

Inspect headings, image alternatives, labels, instructions, contrast, and text enlargement. Check whether information remains understandable without relying on color alone. Submit forms with missing or invalid values to evaluate whether errors identify the problem and explain how to correct it.

Review captions and audio description where applicable, and check layout reflow, text spacing, and interactive target sizes against the selected criteria. For a conformance evaluation, use every applicable success criterion at your target level—not just this introductory checklist. Record pass, fail, not applicable, or not tested, with supporting evidence.

6. Evaluate with assistive technology and involve disabled users

Person reading a refreshable braille display, an assistive technology used with screen readers

Have a tester with relevant expertise review important journeys using assistive technology such as screen readers (for example, NVDA, JAWS, or VoiceOver), refreshable braille displays, screen magnification, and voice control. Define the browser, operating system, and assistive technology combinations in the test record. Include tasks that exercise navigation, forms, dynamic updates, and the information needed to complete a transaction. W3C identifies assistive technology knowledge as part of evaluation expertise.

Invite people with disabilities to attempt realistic tasks and describe the barriers they encounter. Their feedback can reveal usability problems that standards-based checks alone miss. Avoid treating one participant’s success as proof of accessibility for everyone; user evaluation complements, rather than replaces, conformance testing.

7. Document findings and prioritize repairs

Turn confirmed issues into actionable tickets. Each ticket should connect a reproducible barrier to its user impact, relevant criterion, and affected component. Include enough context for someone who did not conduct the audit to understand and verify the problem. Reporting findings is a core part of W3C’s evaluation methodology.

Use a consistent ticket structure:

  • Location: Page address, component, and interaction state.
  • Reproduction: Steps, test environment, and observed behavior.
  • Impact: Who encounters the barrier and which task it affects.
  • Evidence: Relevant criterion, screenshots, recordings, or code excerpts.
  • Resolution: Suggested approach, responsible owner, priority, and acceptance test.

As a practical starting point, prioritize barriers that prevent essential tasks, then consider reach, frequency, and severity. Keep implementation effort separate from user impact so difficult repairs do not disappear behind easier cosmetic changes. In our experience, fixing shared components first—headers, navigation, product templates, and forms—delivers the largest improvement for the least effort.

8. Verify fixes and check related components

Repeat the original reproduction steps after each repair and confirm the expected behavior. Recheck relevant automated findings and manual interactions rather than closing tickets solely because code changed. If the repair affects a shared component, include other places where that component appears in your retest plan.

Record verified, unresolved, and deferred findings separately. Assign deferred work an owner and a review date. Build these checks into ongoing quality assurance: W3C recommends evaluating early and regularly, tracking progress, and monitoring accessibility over time.

What should you do when the results are unclear?

When results are unclear, reproduce the issue, check the relevant WCAG guidance, and ask an experienced evaluator to review the evidence. Distinguish a confirmed failure from an observation that still needs investigation. Tools assist evaluation but cannot determine accessibility on their own.

For a disputed finding, record the exact page state and testing environment, then compare expected and actual behavior. If results differ across environments, document that difference rather than deleting the issue. Avoid guessing at a remedy before you understand the barrier; use the acceptance test to define what successful behavior should look like.

When should you bring in an accessibility partner?

Internal teams can handle many audits, but outside expertise is worth considering when your site is large, relies on complex custom components, or faces legal pressure. Look for evaluators who document their methodology, test manually with assistive technology, and include retesting in their scope. Our guide to enterprise digital accessibility vendors outlines what to ask before you commit.

Keep accessibility part of everyday publishing

Use the audit backlog to improve both the website and the process that produced it. Assign ongoing responsibilities, train contributors, and include accessibility checks when introducing templates, components, content, or third-party services. Maintain a way for users to report barriers, and feed those reports into your review process. W3C recommends sustained monitoring and user feedback, while DOJ guidance highlights the value of an accessibility reporting channel.

The practical goal is a repeatable cycle: identify barriers, make repairs, verify outcomes, and prevent recurrence. Keep the scope and unresolved issues visible so progress remains measurable without overstating what the audit established.

Still have questions?

Frequently Asked Questions

Bryan Miller

Bryan Miller

Owner Founder @ Bryt Designs

Bryan Miller is an entrepreneur and web tech enthusiast specializing in web design, development and digital marketing. Bryan is a recent graduate of the MBA program at the University of California, Irvine and continues to pursue tools and technologies to find success for clients across a varieties of industries.

Read more from Bryan Miller

Subscribe to our newsletter

STAY UP TO DATE WEB DESIGN, DEV, & SEARCH MARKETING INSIGHTS & TIPS

Suggested Content

Finding Top Digital Accessibility Vendors for Enterprise Websites

Published November 9, 2026 by Bryan Miller | Last updated November 2, 2026

Case Study: 25 East Washington Accessibility Overhaul

Published November 5, 2026 by Bryan Miller | Last updated November 5, 2026

Case Study: Bates Nut Farm Accessibility Overhaul

Published October 29, 2026 by Bryan Miller | Last updated October 29, 2026

Ready to make something great?

Let's chat about how we can help achieve your web goals

Let's Chat

Bryt Designs

Web Design, Development, & Search Marketing Insights

Categories

Topics