- What Is a Website Accessibility Audit?
- Why It Matters: ADA Website Compliance Deadlines and Lawsuits
- Who Needs a Website Accessibility Audit?
- Before You Start: Understand What You're Auditing
- Step 1. Define the Audit Scope
- Step 2. Explore the Website and Identify Its Components
- Step 3. Select Representative Pages for Testing
- Step 4. Run Automated Accessibility Tests With Free Tools
- Step 5. Perform a Manual Website Accessibility Audit
- Step 6. Inspect Accessibility at the Code Level
- Step 7. Record and Document Accessibility Issues
- Step 8. Prioritize Accessibility Issues and Recommend Fixes
- Step 9. Retest After Implementation
- Step 10. Prepare the Final Website Accessibility Audit Report
- How Much Does a Website Accessibility Audit Cost?
- How to Choose a Website Accessibility Audit Company
- Website Accessibility Audit Checklist (WCAG 2.2 AA)
- Recommended Resources for Web Accessibility Auditing
- Frequently Asked Questions
- Final Thoughts
Website Accessibility Audit: 10-Step Guide, Checklist & Costs


- Start every website accessibility audit with WCAG 2.2 Level AA as your evaluation target. It gives you a clear standard for identifying barriers and covers the WCAG 2.1 AA criteria referenced by the DOJ's ADA Title II rule.
- Don't rely entirely on automated scanners. Tools like axe DevTools, WAVE, and Lighthouse catch common issues, but a manual website accessibility audit reveals problems automated tools often miss.
- Test complete user journeys, not just individual pages. A website can have accessible components but still fail when users navigate menus, submit forms, or complete checkout.
- Keyboard navigation is non-negotiable. Every interactive element should be accessible, operable, and easy to navigate without a mouse.
- Test with actual assistive technologies like NVDA, JAWS, VoiceOver, and TalkBack. Correct HTML alone doesn't guarantee a usable screen reader experience.
- Document every issue with its affected element, WCAG criterion, user impact, evidence, and recommended fix. A useful audit report tells developers exactly what needs to change.
- Budget realistically. Published prices for a manual audit range from about $1,250 for a small site to $25,000 or more for complex sites and web apps, before remediation.
Can someone navigate your website without a mouse? Can a screen reader identify your buttons, links, and form fields? Does your content remain readable when users increase the text size?
If you can't confidently answer these questions, your website may have accessibility issues you haven't discovered yet.
A website accessibility audit helps you evaluate these experiences, identify barriers, and understand where your website falls short of established accessibility standards such as WCAG 2.2. But conducting one requires more than running an automated checker. You also need manual testing, assistive technology evaluation, and a structured reporting process.
This guide walks you through the full website accessibility audit process in 10 steps. You'll also find a WCAG audit checklist, a sample report finding, typical audit costs, and questions to ask before you hire an accessibility audit service.
What Is a Website Accessibility Audit?
A website accessibility audit is a structured evaluation of a website against the Web Content Accessibility Guidelines (WCAG), usually WCAG 2.2 Level AA. It combines automated scans, manual testing, and assistive technology checks to find barriers that stop people with disabilities from using your site, then documents each issue with a recommended fix.
You may also hear it called a WCAG audit, a digital accessibility audit, or an ADA compliance audit. The method is the same. The name usually reflects the requirement the site owner needs to meet:
- ADA Title II: The DOJ's 2024 rule requires state and local government websites and mobile apps to meet WCAG 2.1 Level AA.
- ADA Title III: Covers businesses open to the public. The DOJ hasn't set a technical web standard under Title III, but settlements and court orders commonly reference WCAG 2.1 or 2.2 Level AA.
- Section 508: Requires U.S. federal agencies' information and communication technology to conform to WCAG 2.0 Level AA. Vendors usually document this in a VPAT or Accessibility Conformance Report (ACR).
- European Accessibility Act (EAA): Applies from 28 June 2025 to many digital products and services sold in the EU. Its harmonized standard, EN 301 549, incorporates WCAG 2.1 Level AA.
Because WCAG 2.2 AA includes nearly every WCAG 2.1 AA criterion, auditing against 2.2 AA covers most of these ADA website compliance requirements at once. Confirm which laws apply to your organization with legal counsel.
Why It Matters: ADA Website Compliance Deadlines and Lawsuits
Website accessibility lawsuits are rising again. According to Seyfarth Shaw, plaintiffs filed 3,117 ADA Title III website accessibility lawsuits in U.S. federal court in 2025, a 27% increase over 2024. When state court filings are included, the 2025 total exceeded 5,000 (Level Access).
Public entities face firm dates too. In April 2026, the DOJ published an interim final rule moving the ADA Title II compliance dates back by one year: April 26, 2027 for state and local governments with a population of 50,000 or more, and April 26, 2028 for smaller governments and special districts. The WCAG 2.1 AA requirement itself didn't change.
What it means: a website accessibility audit gives you a documented baseline, a prioritized fix list, and evidence of good-faith progress. It won't make a site lawsuit-proof, but it's the first step toward ADA website compliance. Check ADA.gov for the latest dates before you plan around them.
Who Needs a Website Accessibility Audit?
Any organization with a public website benefits from an accessibility audit, but some face more pressure than others.
Government and Public Sector Websites
State and local government websites, including public colleges and transit agencies, fall under ADA Title II. A government website accessibility audit should cover online services such as permit applications, payment portals, meeting agendas, and PDFs, not just the homepage. Federal agencies and their vendors also need Section 508 conformance, often documented in a VPAT/ACR.
School Districts and Universities
Public school districts are Title II entities, so their websites need to meet WCAG 2.1 AA by the DOJ deadlines. Focus the audit on enrollment forms, parent portals, calendars, lunch menus, and uploaded documents. The checklist later in this guide works as a school district website accessibility audit checklist.
Nonprofits
Nonprofits often serve people with disabilities directly, so start a nonprofit website accessibility audit with donation forms, event registration, and volunteer sign-ups. Many nonprofits run on WordPress. A WordPress website accessibility audit should also check the theme, page builder output, and plugins such as forms and sliders, since they often generate inaccessible markup.
E-Commerce Stores
Online retail has historically drawn the heaviest share of ADA website lawsuits. An e-commerce website accessibility audit checklist should cover product filters, image alt text, size and color selectors, the cart, checkout, and payment fields: the same journey used as the example throughout this guide.
SaaS Products and Web Apps
If you sell software to enterprises or government buyers, procurement teams often ask for a VPAT/ACR. A WCAG audit of your app's key flows is the evidence behind that document.
Before You Start: Understand What You're Auditing
Before running accessibility tests, you need to understand what you're auditing and what you want to evaluate. Start by defining three things:
- Website or product: What website or application are you auditing?
- Pages and user journeys: Which pages, components, and interactions need testing?
- Accessibility standard: Which guidelines will you use to evaluate the website?
For a professional website accessibility audit, use WCAG 2.2 Level AA as your evaluation target, unless the client's applicable regulations specify otherwise (for example, WCAG 2.1 AA for ADA Title II or WCAG 2.0 AA for Section 508).
Your goal is to determine whether people with different disabilities can independently access content and complete important tasks. Accessibility is one of the 7 pillars of UX design, and it is the one an audit measures directly.
For example, consider an e-commerce website. Don't limit your evaluation to checking whether its homepage has accessible images. You should also test whether someone using a keyboard or screen reader can:
- Find a product.
- Understand product information.
- Select a product variation.
- Add it to their cart.
- Complete checkout.
- Understand validation errors.
This helps you evaluate the entire user experience rather than checking isolated website elements.
Step 1. Define the Audit Scope
Start by identifying which pages and website components you'll evaluate. Rather than testing every URL individually, select representative pages that cover the website's main layouts, features, and interactions.
Start by documenting:
For an example, suppose you're auditing an online store. Your audit scope might include:
- Homepage
- Category listing page
- Product detail page
- Search results
- Shopping cart
- Checkout
- Login and registration
- Contact page
Don't forget shared components such as navigation menus, cookie banners, footers, pop-ups, and dialogs. These elements often appear across multiple pages, so an accessibility issue in one shared component can affect the entire website.
Defining these elements upfront gives you a clear testing boundary and helps ensure that important pages and interactions aren't overlooked.
Step 2. Explore the Website and Identify Its Components
Once you've defined your audit scope, explore the website as an actual visitor would. Navigate through its pages, interact with different elements, and identify the components that make up the user experience.
The goal is to understand how the website is structured, what users can interact with, and which elements require accessibility testing.
Start by creating an inventory of the components you encounter:
Next, map the important user journeys. These are sequences of actions users take to complete specific tasks on your website.
For example, consider an e-commerce purchase journey:
Open the homepage. -> Navigate to a product category. -> Filter and select a product. -> Choose a size and color. -> Add the product to the cart. -> Complete the checkout form. -> Review the order and submit payment.
Identify the interactive elements involved at each stage, including navigation menus, filters, dropdowns, buttons, and form fields.
Why does this matter? Because a website might have individually accessible buttons but still create accessibility barriers during an entire user journey. For example, a checkout modal might trap keyboard focus, preventing users from navigating to other elements or completing their purchase.
That's why you need to evaluate both individual components and how they work together throughout the user journey. This inventory will also help you determine which elements to test during the automated and manual testing stages.
Step 3. Select Representative Pages for Testing
If a website contains hundreds of URLs, manually auditing every page may not be practical. Instead, select a representative sample that covers its different page templates, content types, and functionality.
Start by grouping similar pages together. For example, an e-commerce website may have hundreds of product pages, but most follow the same layout. You don't need to audit every product URL individually. Select a few pages that represent the shared layout and interactive elements.
Use the following table to identify which page types to include:
Also, look for pages with unique functionality that may require additional testing, such as:
- Search autocomplete.
- Expandable navigation menus.
- Image galleries and carousels.
- Embedded video players.
- Interactive maps.
- Custom dropdowns and filters.
Don't rely only on representative pages. Include all common page templates and shared components, then select a few random pages to identify unexpected accessibility issues. This helps uncover problems that might not appear in your initial selection.
For a structured WCAG evaluation, the W3C's WCAG Evaluation Methodology (WCAG-EM) recommends combining structured sampling with random sampling. Its methodology provides a more systematic approach to selecting pages for evaluation.
See the W3C WCAG Evaluation Methodology for detailed sampling guidance.
Step 4. Run Automated Accessibility Tests With Free Tools
Now that you've selected the pages and identified their components, it's time to run automated accessibility tests.
Automated testing tools scan a webpage's HTML, CSS, and accessibility-related properties to identify common accessibility issues. They can help detect problems such as:
- Images missing alternative text.
- Form fields without accessible labels.
- Insufficient text color contrast.
- Missing document language.
- Invalid or incorrectly used ARIA attributes.
- Incorrect heading structures.
- Some accessibility issues with interactive elements.
For this step, use three free accessibility audit tools: Google Lighthouse, axe DevTools, and WAVE. Together they give you a free website accessibility audit baseline, but not a complete one.
Method A. Google Lighthouse Accessibility Audit
Method A. Google Lighthouse Accessibility Audit
Google Lighthouse is built into Chrome DevTools and can generate an accessibility report for an individual webpage.
How to run an accessibility test:
- Open the website in Google Chrome.
- Navigate to the page you want to audit.
- Right-click anywhere on the page and select Inspect.
- Open the Lighthouse tab in Chrome DevTools.
- Select Accessibility under the available audit categories.
- Choose the device mode, such as Mobile or Desktop, if available.
- Click Analyze page load or the equivalent audit button.
- Wait for the report to generate and review the accessibility results.
What to look for:
Lighthouse provides an accessibility score and a list of detected issues. Expand individual findings to understand which elements failed, why they failed, and which accessibility requirements they relate to.
Note: Lighthouse's accessibility score is not a WCAG compliance score. It only reflects the automated checks performed during the audit.
Method B. axe DevTools
axe DevTools is a browser extension that scans webpages for accessibility violations based on established accessibility rules, including WCAG criteria.
How to run an accessibility test:
- Install the axe DevTools browser extension.
- Open the webpage you want to evaluate.
- Right-click the page and select Inspect to open Chrome DevTools.
- Find and open the axe DevTools panel.
- Start a full-page accessibility scan.
- Wait for the scan to complete.
- Review the detected violations and expand individual results.
- Inspect the affected HTML elements, explanations, and recommended fixes.
What to look for:
axe DevTools organizes detected issues into individual violations. Each finding provides details about the affected element, the relevant accessibility rule, and guidance on resolving the problem.
Pay particular attention to the affected elements and the suggested fixes. A single violation may affect multiple elements on the same page.
Method C. WAVE Accessibility Audit
WAVE is a web accessibility evaluation tool that visually highlights accessibility issues directly on a webpage. Unlike a score-focused report, it overlays icons and annotations on the page to help you identify where potential problems occur.
How to run an accessibility test:
- Visit the WAVE evaluation tool.
- Enter the URL of the webpage you want to evaluate.
- Click the arrow to generate the report.
- Review the accessibility summary in the sidebar.
- Open the Details panel to inspect individual errors and alerts.
- Click an issue to locate the affected element on the webpage.
- Review the explanation and determine whether further manual testing is required.
What to look for:
WAVE uses different icons to categorize its findings:
For password-protected, dynamic, or locally hosted pages, use the WAVE browser extension instead of relying only on its URL-based checker.
Record the Results
After running the three tools, document the issues identified on each page. Don't rely on memory or assume that the tools will retain your findings.
For every detected issue, record:
- Affected page: URL of the page where the issue appears.
- Affected element: The specific button, image, form field, or other component.
- Issue description: What the tool detected.
- WCAG criterion: The relevant success criterion, if identified.
- Evidence: Screenshot or report showing the issue.
- Status: Needs manual verification, confirmed, or resolved.
Important: Run the tests on every representative page selected in Step 3. Also, interact with dynamic components before scanning them. For example, open dropdowns, expand accordions, trigger form errors, and display modal dialogs. Otherwise, some elements or interaction states may not be included in the scan.
A few things to remember
- Don't treat every automated finding as a confirmed accessibility violation. Review each result and verify it manually.
- Don't combine the issue counts from different tools. They may identify the same problem or use different testing rules.
- Don't assume a clean report means the page is fully accessible. Automated tools cannot evaluate every WCAG success criterion.
Recommendation: Use axe DevTools as your primary automated testing tool, Lighthouse for an additional accessibility overview, and WAVE for visual inspection. Keep the results from all three tools as supporting evidence for the next manual testing stage.
Automated testing is only one part of an accessibility audit. You'll need manual testing to evaluate keyboard navigation, screen reader compatibility, focus behavior, and other issues that automated tools cannot reliably detect.
Automated Scan vs AI Tool vs Manual Audit: What's the Difference?
Automated tools are fast, but their coverage is limited. Deque's analysis of more than 2,000 audits found its axe-core automated tests identified about 57% of issues by volume. Measured by WCAG success criteria instead, automated coverage is commonly put at 20% to 30%. AI-powered tools speed up detection, but the same AI audit gaps remain for anything that needs human judgment. Here's how the three approaches compare:
Step 5. Perform a Manual Website Accessibility Audit
Automated testing can identify many common accessibility issues, but it cannot evaluate every aspect of how people interact with a website. Some problems only become apparent when you navigate the interface, use assistive technologies, or complete actual tasks.
That's why manual testing is an essential part of a web accessibility audit. For the design principles behind these checks, see our guide to accessibility in UI/UX design.
In this step, you'll inspect the website's pages and interactive components against relevant WCAG 2.2 success criteria to identify barriers that automated tools might miss.
Work through the following testing areas, using the representative pages and user journeys selected in the previous steps.
5.1. Keyboard Navigation Testing
Some people cannot use a mouse because of motor disabilities or other physical limitations. Instead, they navigate websites using a keyboard or alternative input devices.
The goal of this test is to determine whether users can access and operate all interactive elements without a mouse. This includes links, buttons, dropdowns, menus, forms, dialogs, and other controls.
How to test:
- Open the webpage you want to evaluate.
- Put your mouse aside and use only your keyboard.
- Press Tab to move forward through interactive elements.
- Press Shift + Tab to move backward.
- Press Enter to activate links and buttons.
- Press Space to activate buttons, checkboxes, and other applicable controls.
- Use the arrow keys to navigate menus, radio groups, and other applicable components.
- Press Esc to close open menus, dialogs, or pop-ups where supported.
As you navigate, pay attention to which elements receive focus, the order in which they appear, and whether you can operate and exit every interactive component.
What to inspect:
Example of a failure:
Imagine a website with a navigation dropdown that opens when users hover over it. However, keyboard users cannot open the dropdown or access its links using the keyboard.
This creates a navigation barrier for people who cannot use a mouse. Keep a record of the affected page, the component causing the problem, the keyboard steps needed to reproduce it, and the relevant WCAG criterion.
5.2. Color Contrast Testing
People with low vision or color vision deficiencies may struggle to distinguish text and interface elements when foreground and background colors have insufficient contrast. If you are choosing a palette, these color combinations with hex codes show how to keep text contrast above 4.5:1.
During this test, check whether text, buttons, form fields, icons, and other important visual elements meet WCAG contrast requirements.
WCAG 2.2 contrast requirements:
Large text means text that is at least 18pt (24px) regular or 14pt (approximately 18.67px) bold.
How to test:
- Open the webpage and identify text, buttons, icons, and other important visual elements.
- Inspect the foreground and background colors of each element.
- Obtain their actual color values using browser developer tools or a color picker.
- Enter both color values into a contrast checker.
- Compare the calculated contrast ratio against the applicable WCAG requirements.
- Record elements that fail the required contrast ratio.
Useful tool: WebAIM Contrast Checker.
For example:
Don't use color as the only way to communicate information. For example, a form error shouldn't be indicated by a red border alone. Include a descriptive error message or another visual indicator so users can identify and understand the problem.
Document the affected element, foreground and background color values, measured contrast ratio, required ratio, and relevant WCAG criterion.
5.3. Screen Reader Testing
Screen readers convert website content into speech or braille output, allowing people who are blind or have low vision to navigate and interact with websites.
During this test, check whether a screen reader can correctly identify website content, communicate the purpose of interactive elements, and help users complete important tasks.
Common screen readers to use:
For this audit, you can start with NVDA on Windows. If possible, test with JAWS, VoiceOver, or TalkBack as well, since screen readers can behave differently across operating systems and browsers.
How to Test Using NVDA
- Download and install NVDA on a Windows computer.
- Open NVDA and launch your website in a supported browser, such as Chrome or Firefox.
- Start navigating the page using the keyboard rather than your mouse.
- Use heading navigation to move between sections and understand the page structure.
- Navigate through links, buttons, form fields, and other interactive elements.
- Listen to how the screen reader announces images, labels, roles, and available states.
- Interact with menus, forms, dialogs, and dynamic content to check whether changes are announced correctly.
- Complete an important user journey, such as searching for a product or submitting a form.
Useful NVDA keyboard shortcuts:
NVDA is the screen reader command key used with these shortcuts. Its default key is Insert, although Caps Lock can also be configured.
What to Inspect
As you navigate the website, check whether the screen reader communicates the following information correctly:
Example of a Screen Reader Accessibility Issue
Imagine an e-commerce website with a shopping cart button that only displays a cart icon.
If the button has no accessible name, NVDA might announce it simply as "Button" without explaining its purpose.
Compare the two implementations:
Incorrect:
<button>
<img src="cart-icon.svg">
</button>
Better:
<button aria-label="Open shopping cart">
<img src="cart-icon.svg" alt="">
</button>
Now, the screen reader can announce "Open shopping cart button," making its purpose clear.
What to Record
When you identify an issue, document:
- Affected element: The button, image, link, or form field.
- Screen reader announcement: What NVDA actually announces.
- Expected announcement: What users should hear.
- Issue description: What information or functionality is missing.
- WCAG criterion: The relevant accessibility requirement.
- Evidence: Screenshot, reproduction steps, or a recording where appropriate.
Don't assume that a correct screen reader announcement means the element is accessible. Test whether users can actually operate it and complete the intended task. For the strongest evidence, include people who use assistive technology in moderated usability testing.
Also, decorative images should generally be ignored by screen readers, while informative images need meaningful text alternatives. Don't listen to the entire webpage from beginning to end. Navigate using headings, landmarks, links, and form controls.
This helps you understand how someone using a screen reader would explore the website independently.
5.4. Image Alternative Text Testing
Alternative text (alt text) describes an image's content or purpose for people who cannot see it. Screen readers read this text aloud, helping users understand information communicated through images.
During this test, check whether informative images have meaningful descriptions and decorative images are correctly excluded from screen reader announcements.
How to test:
- Open the webpage and inspect its images, including product photos, illustrations, logos, icons, and charts.
- Inspect each image's HTML to find its alt attribute.
- Check whether the alternative text accurately describes the image or communicates its purpose in context.
- Verify that informative images have appropriate descriptions.
- Check whether decorative images use an empty alt attribute (alt="") so screen readers can skip them.
- Use a screen reader to verify what users actually hear when navigating the images.
What to check:
Different images require different alternative text depending on their purpose.
Example: Image with and without useful alt text
Consider a product page displaying a red running shoe.
Remember, not every image needs descriptive alt text. Decorative images should generally have an empty alternative (alt="").
For each issue, document the affected image, its existing alt text, the recommended alternative text, and the relevant WCAG criterion.
5.5. Form Accessibility Testing
Forms allow users to complete important tasks, such as creating accounts, logging in, contacting a business, or making purchases. If a form is difficult to understand or operate, users may be unable to complete these tasks. For labeling and layout patterns, see these contact form design examples.
Test the forms included in your audit scope, such as registration, login, contact, search, and checkout forms.
What to inspect:
How to test form accessibility:
- Open a form and navigate through its fields using only the keyboard.
- Check whether each field has a visible label and an accessible name.
- Identify required fields and check whether their requirements are communicated.
- Submit the form with empty or incorrect information to trigger validation errors.
- Check whether each error explains how to correct the problem.
- Use a screen reader to confirm that error messages are announced and associated with the correct fields.
- Submit the form with valid information and check whether users receive confirmation.
Example: Accessible error validation
Imagine a user enters an invalid email address and submits a registration form.
The second example explains the problem in text and makes the error available to assistive technology. In practice, the field should also expose its invalid state, and users should be able to identify and correct the error.
Relevant WCAG 2.2 criteria include:
- 1.3.1 – Info and Relationships: Labels and instructions must have programmatically determinable relationships.
- 3.3.1 – Error Identification: Input errors must be identified and described in text.
- 3.3.2 – Labels or Instructions: Provide labels or instructions when users need to enter information.
- 3.3.3 – Error Suggestion: When a correction is known, provide suggestions to help users fix the error.
5.6. Heading Structure and Content Hierarchy
Headings organize webpage content into clear sections and subsections. They help users understand how information is structured and allow screen reader users to navigate directly between sections. A clear information architecture makes a logical heading hierarchy much easier to maintain.
During the audit, check whether headings describe the content accurately and follow a logical order.
What to inspect:
- Main heading: Each page has a clear main heading that describes its primary topic.
- Descriptive headings: Headings accurately describe the content that follows.
- Logical hierarchy: Heading levels follow a meaningful structure, such as H1, H2, and H3.
- Proper heading elements: Headings use HTML heading elements (<h1> to <h6>), not just bold text or enlarged paragraphs.
- Visual and semantic consistency: Heading levels aren't chosen only to achieve a particular font size.
- Content organization: Related content is grouped under appropriate headings and subheadings.
Example: Logical heading hierarchy
H1: Web Accessibility Guide
H2: Understanding Accessibility
H3: Visual Accessibility
H3: Keyboard Accessibility
H2: Conducting an Accessibility Audit
H3: Automated Testing
H3: Manual Testing
In this example, the H1 introduces the page topic. H2 headings divide the main sections, while H3 headings organize related subsections.
How to test heading structure:
- Open the webpage and inspect its headings using browser developer tools or an accessibility inspection tool.
- Check whether the page has a meaningful main heading.
- Review the heading levels from top to bottom.
- Look for skipped levels, such as moving directly from H2 to H4 without a valid structural reason.
- Check whether each heading accurately describes the section below it.
- Use a screen reader's heading navigation to confirm users can understand and move through the page structure.
What to record: Note the affected page, incorrect heading, current heading level, recommended level, and relevant WCAG criterion.
Relevant WCAG 2.2 criteria include:
- 1.3.1 – Info and Relationships: Headings and other content relationships must be programmatically determinable.
- 2.4.6 – Headings and Labels: Headings and labels must describe their topic or purpose.
5.7. Responsive and Zoom Testing
People with low vision may increase text size or zoom in on a webpage to make content easier to read. You need to check whether the website remains usable when its content is enlarged or viewed on smaller screens.
How to test:
- Open the website in your browser.
- Increase the browser zoom to 200%.
- Check whether text, images, navigation, and interactive elements remain visible and usable.
- Look for overlapping content, clipped text, or elements that become difficult to access.
- Increase the zoom to 400% and check the layout at a viewport equivalent to 320 CSS pixels wide.
- Verify that users can access content without unnecessary horizontal scrolling.
Also, test the website on mobile devices to check whether its layout adapts to smaller screens without hiding important content or functionality. Our responsive web design best practices cover the layout patterns that hold up best.
What to check:
- Text remains readable without requiring horizontal scrolling.
- Content doesn't overlap or get cut off.
- Buttons and links remain accessible.
- Navigation menus work on smaller screens.
- Forms and interactive components remain usable.
- Content and functionality aren't lost when the layout changes.
Relevant WCAG criteria:
Responsive testing and zoom testing aren't the same. A website may adapt perfectly to mobile screens but still become difficult to use when someone zooms in. Test both to identify layout and accessibility problems.
5.8. Links, Buttons, and Interactive Components
These elements allow users to interact with a website. You need to check whether their purpose and behavior are understandable.
Test the following:
For example, a button displaying only a search icon should have an accessible name such as "Search".
Also check WCAG 2.2's minimum target size requirement (2.5.8): targets generally need to be at least 24 × 24 CSS pixels, subject to specified exceptions. iOS and Android ask for larger targets, as covered in our guide to cross-platform UX design.
5.9. Videos and Audio Accessibility
Videos and audio content should be accessible to people who cannot hear, see, or understand certain parts of multimedia content. Check whether your website provides suitable alternatives, such as captions, transcripts, and audio descriptions.
What to inspect:
Example: Imagine a tutorial video explains how to use a website but displays important instructions only through speech. Without captions, people who are deaf or hard of hearing may miss those instructions.
Provide synchronized captions so users can read the spoken information while watching the video.
How to test multimedia accessibility:
- Play each video and check whether captions are available.
- Compare captions with the actual speech and check their timing.
- Check whether meaningful sounds, such as alarms or speaker identification, are included when necessary.
- Look for transcripts for audio-only content.
- Check whether important visual information has an audio description or an equivalent alternative.
- Test whether users can pause, stop, or control automatically playing audio.
What to record: Note the affected media, missing or inaccurate alternative, how to reproduce the issue, and the relevant WCAG criterion.
Relevant WCAG 2.2 criteria include 1.2.1–1.2.5 for prerecorded and live media alternatives, and 1.4.2 – Audio Control for automatically playing audio.
5.10. Page Language and Document Structure
A website's underlying HTML structure helps browsers and assistive technologies understand its content. Incorrect language settings, document titles, or HTML attributes can make pages difficult to interpret.
Inspect the page source or use browser developer tools to check the following:
Example: Declaring the page language
<html lang="en">The lang attribute tells browsers and assistive technologies that the page's primary language is English. This helps screen readers use the appropriate pronunciation rules.
If a page contains a sentence in another language, its language can be identified separately:
<p>
Welcome to our website.
<span lang="fr">Bonjour</span>
</p>
How to test page language and structure:
- Open the webpage and inspect its HTML using browser developer tools.
- Check whether the <title> element describes the page accurately.
- Find the <html> element and verify that its lang attribute matches the primary page language.
- Look for significant language changes within the content and check whether they are identified.
- Inspect interactive elements to confirm they use appropriate HTML elements and expose their purpose and state.
- Check custom ARIA attributes for invalid values, missing required properties, or incorrect roles.
Note the affected page or element, the incorrect HTML or attribute, the expected implementation, and the relevant WCAG criterion.
Relevant WCAG 2.2 criteria include:
- 2.4.2 – Page Titled: Pages have titles that describe their topic or purpose.
- 3.1.1 – Language of Page: The default language of each webpage is programmatically determinable.
- 3.1.2 – Language of Parts: The language of passages or phrases that differ from the page's default language can be programmatically determined, with specified exceptions.
- 4.1.2 – Name, Role, Value: User interface components expose their name, role, and state or value to assistive technologies.
Step 6. Inspect Accessibility at the Code Level
Visual inspection and automated testing can identify many accessibility issues, but some problems require checking the underlying code.
In this step, inspect the HTML, accessibility tree, and ARIA implementation to understand how browsers and assistive technologies interpret website components.
This is particularly useful when auditing SaaS products with custom interfaces, interactive components, and dynamic content.
Common Implementation Issues
Example 1: Using a generic element as a button
Incorrect:
<div onclick="submitForm()">
Submit
</div>
A <div> is a generic container. Adding a click handler doesn't automatically give it button semantics or keyboard functionality.
Better:
<button type="submit">
Submit
</button>
A native <button> provides built-in keyboard interaction, focus behavior, and button semantics.
Example 2: A form field without an associated label
Incorrect:
A placeholder provides a visual hint, but it doesn't replace a properly associated label.
Better:
<label for="email">Email address</label>
<input id="email" type="email">
The for and id attributes associate the label with the input, allowing assistive technologies to identify the field.
Example 3: An image without alternative text
Incorrect:
<img src="product.jpg">Better:
<img
src="product.jpg"
alt="Red running shoe with white sole"
>
The alt attribute provides a text alternative for informative images. Decorative images should generally use an empty alternative (alt="").
Example 4: An icon-only button without an accessible name
Incorrect:
Better:
<button aria-label="Open search">
<svg aria-hidden="true">...</svg>
</button>
The aria-label provides an accessible name, while aria-hidden="true" prevents the decorative icon from being announced separately.
How to Inspect Accessibility Using Chrome DevTools
Use Chrome DevTools to inspect how individual elements are exposed to assistive technologies.
- Open the webpage in Chrome.
- Right-click the element you want to inspect and select Inspect.
- In the Elements panel, select the relevant HTML element.
- Open the Accessibility section in the element's details pane.
- Review its accessible name, role, and state.
- Check whether the element appears correctly in the accessibility tree.
- Compare the information with what the component is supposed to communicate.
For example, a search button should expose a name such as "Open search" and a role of "button". If its accessible name is missing, investigate its HTML and ARIA implementation.
Step 7. Record and Document Accessibility Issues
After completing automated, manual, and code-level testing, organize your findings into a clear audit report.
The goal is to turn accessibility problems into actionable tasks that developers and designers can understand, prioritize, and fix.
Avoid vague observations such as:
"Some buttons are inaccessible."
Instead, document exactly where the issue occurs, what causes it, who it affects, how to reproduce it, and what needs to change.
Website Accessibility Audit Example: A Documented Finding
Issue #001: Missing accessible name
- High priority
- Needs remediation
- Affected page: Product detail page
- Affected element: Shopping cart icon button
- Issue description: The shopping cart button does not have an accessible name. A screen reader may announce it as an unnamed button, leaving users unable to understand its purpose.
- WCAG criterion: 4.1.2 – Name, Role, Value (Level A)
- User impact: Screen reader users may not understand what the button does or when to use it.
- Recommendation: Provide an accessible name, such as "Open shopping cart". This can be added using visible text or an appropriate accessible label.
- Testing method: NVDA screen reader and Chrome DevTools Accessibility panel.
- Status: Open – Needs remediation
For a real audit, maintain a findings register to track every identified issue. This makes it easier to assign work, monitor progress, and verify fixes.
These priority levels are suggested project-management classifications, not official WCAG severity ratings. Consider the number of affected users, the importance of the feature, and whether a reasonable workaround exists when assigning priority.
Step 8. Prioritize Accessibility Issues and Recommend Fixes
After documenting accessibility issues, decide which ones need attention first. Not every issue has the same impact, and development teams may not be able to fix everything at once.
Prioritize issues based on:
- Severity of impact: How seriously does the issue affect users?
- Number of affected users: Does it affect one user group or multiple groups?
- Page coverage: Does it appear on one page or across the entire website?
- User journey impact: Does it prevent users from completing essential tasks?
- Frequency: How often are users likely to encounter the issue?
- Available workarounds: Can users complete the task another way, or are they completely blocked?
Example: Accessibility issue prioritization
Don't simply report that an element fails a WCAG criterion. Explain what needs to change and how the development or design team can address it.
Step 9. Retest After Implementation
An accessibility audit isn't complete when the report is delivered. You need to verify that developers have fixed the reported issues and that the changes work as expected.
A fix that looks correct in the code may still fail during actual use. That's why you should repeat the original test rather than simply checking whether the code has changed.
Follow this process:
- Revisit the affected page and component.
- Repeat the original test using the same testing method.
- Check whether the issue has been resolved.
- Test related components and interactions for new accessibility problems.
- Update the issue status in your findings register.
- Record the retest date, results, and supporting evidence.
Example: Retesting an accessible button
Imagine a developer adds an accessible name to a shopping cart button. Don't just inspect the HTML to confirm that an aria-label has been added. Instead:
- Navigate to the button using a screen reader.
- Confirm it announces the correct name and role.
- Activate it using the keyboard.
- Check whether it performs the intended action.
- Verify that its accessible name remains meaningful after the interface updates.
Update the findings register:
If a fix introduces another accessibility problem, document it as a new finding. Don't mark an issue as resolved until you've verified its actual behavior.
Step 10. Prepare the Final Website Accessibility Audit Report
Once testing, prioritization, and retesting are complete, prepare the final accessibility audit report.
The report should give stakeholders a clear understanding of the website's accessibility condition, the problems identified, and the improvements needed.
Organize your report into the following sections:
Use an established reporting framework
You don't need to create your audit report entirely from scratch. W3C provides resources that can help you structure and document your evaluation.
- W3C Accessibility Evaluation Report Template: A template for documenting accessibility evaluation results.
- W3C Website Accessibility Conformance Evaluation Methodology (WCAG-EM): A structured methodology for evaluating website conformance with WCAG.
What Is Included in a Website Accessibility Audit?
When you hire an accessibility audit service, expect these deliverables in the website accessibility audit report, and ask for any that are missing:
- Executive summary: Overall conformance, top risks, and next steps for non-technical stakeholders.
- Issue log mapped to WCAG criteria: Every finding with its page, element, success criterion, and level (A or AA).
- Severity or priority rating: So teams know what blocks users and what can wait.
- Fix guidance: Code-level recommendations developers can act on, like the examples in Step 6.
- VPAT/ACR (optional): A Voluntary Product Accessibility Template completed as an Accessibility Conformance Report, often required for government and enterprise procurement.
- Retest or validation: A follow-up check confirming fixes work, as described in Step 9.
See the sample finding in Step 7 for what a single issue entry should look like. For comparison, these UX audit report examples show how broader usability findings are presented.
How Much Does a Website Accessibility Audit Cost?
Website accessibility audit cost depends on the number of unique templates and user journeys, the complexity of components, the WCAG version, and whether you need remediation, a VPAT/ACR, or retesting. Published price ranges look like this:
The cost of a manual website accessibility audit is higher than a scan because experts test page by page with keyboards and screen readers, but it finds the issues scans miss. Get at least two quotes and compare the methodology, not just the price.
How to Choose a Website Accessibility Audit Company
If you hire out the audit, you'll find everything from automated-scan resellers to specialist WCAG audit services. Ask these five questions before you sign:
- Is the audit manual? Ask how much testing is done by people and which screen readers (NVDA, JAWS, VoiceOver) and browsers they use.
- Which standard and level? The answer should be specific, such as WCAG 2.2 Level AA, and match your legal requirements.
- How do you select pages? Look for a representative sample of templates and user journeys, ideally following W3C's WCAG-EM.
- What do the deliverables include? Expect an issue log mapped to WCAG criteria, severity ratings, fix guidance, and an optional VPAT/ACR.
- Is retesting included? A good partner verifies fixes after remediation instead of leaving you with a static PDF.
Red flags to watch for:
- Overlay-only fixes: A JavaScript widget that promises instant ADA website compliance without changing your code.
- No manual or screen reader testing: Automated scan results repackaged as an audit report.
- Compliance guarantees: Promises of "100% compliance" or protection from lawsuits.
- No retest: No validation step after your team fixes the issues.
Whether a provider calls itself an ADA website compliance consultant or a digital accessibility audit service, the best ones show you a sample report before you buy. Many teams pair it with a UX audit so accessibility and usability fixes land in the same roadmap.
Website Accessibility Audit Checklist (WCAG 2.2 AA)
Use this checklist while auditing a website. Work through each section in order and mark an item complete only after you've performed the check and recorded any issues. It also works as an ADA website compliance checklist, since WCAG 2.2 AA covers the WCAG 2.1 AA criteria referenced by the DOJ's ADA Title II rule.
1. Audit preparation
- Define WCAG version and conformance level
- Identify website pages and user journeys
- Inventory shared components
- Select representative pages
2. Automated testing
- Run axe DevTools
- Run Lighthouse accessibility audit
- Run WAVE evaluation
- Review and verify detected violations
3. Manual testing
- Test keyboard navigation
- Check focus visibility and order
- Measure color contrast
- Test screen reader compatibility
- Inspect image alternative text
- Check heading hierarchy
- Test forms and error messages
- Check buttons, links, menus and modals
- Test zoom and responsive layouts
- Inspect multimedia alternatives
4. Technical validation
- Inspect semantic HTML
- Check accessible names, roles and states
- Review ARIA implementation
- Check page language and document title
5. Reporting and verification
- Document each accessibility issue
- Map issues to WCAG criteria
- Prioritize remediation
- Provide implementation recommendations
- Retest resolved issues
- Prepare final audit report
- Reset checklist
Keep your findings register open while working through this checklist. If you discover an accessibility issue, document it with the affected page, element, WCAG criterion, evidence, and recommended fix. Don't mark a task complete just because a tool reports no errors; verify the actual user experience. Running a SaaS site? Combine this with our SaaS website audit checklist to cover performance, SEO, and conversion in the same pass.
Recommended Resources for Web Accessibility Auditing
If you want to learn more about accessibility testing and conduct more thorough evaluations, these official W3C resources are worth bookmarking:
- WCAG Evaluation Methodology (WCAG-EM) – A structured methodology for evaluating website accessibility, from defining the audit scope to reporting evaluation results.
- W3C Easy Checks – A collection of simple checks to help identify common accessibility issues, including page titles, headings, images, contrast, and keyboard access.
- WCAG 2.2 Quick Reference – A searchable reference for WCAG success criteria, conformance levels, and techniques for meeting accessibility requirements.
- W3C Accessibility Evaluation Tools – A directory of accessibility evaluation tools that can help automate checks and support manual testing.
These resources serve different purposes. WCAG-EM provides a structured evaluation methodology, Easy Checks helps identify common accessibility problems, and the Quick Reference helps you understand individual WCAG requirements.
Frequently Asked Questions
What Is a Website Accessibility Audit?
A website accessibility audit evaluates a website against accessibility standards such as WCAG 2.2 AA. It identifies barriers that prevent people with disabilities from accessing content, navigating pages, or completing tasks, and gives developers a prioritized list of fixes. It's also called a WCAG audit or an ADA compliance audit.
How Do You Perform a Website Accessibility Audit?
Start by defining the audit scope and selecting representative pages. Then run automated scans, perform manual testing, evaluate screen reader compatibility, document WCAG violations, prioritize fixes, and retest the website.
How Much Does a Website Accessibility Audit Cost?
Most manual audits of small websites cost about $1,250 to $7,000. Mid-size and e-commerce sites typically run $7,000 to $25,000, and complex enterprise sites or SaaS apps $15,000 to $75,000 or more. Automated scans range from free to a few hundred dollars a month, but they don't replace a manual audit.
How Long Does a Website Accessibility Audit Take?
A manual audit of a standard scope, around 10 to 20 pages or screens, typically takes about two weeks (Accessible.org). Larger sites and web apps can take a month or more. Remediation and retesting add time, often several weeks to a few months depending on the number of issues.
How Often Should a Website Accessibility Audit Be Performed?
Run a full manual audit at least once a year, and again after a redesign, a platform migration, or a major feature launch. Between audits, use automated monitoring and spot-check new templates so regressions don't build up.
How Do You Prepare for a Website Accessibility Audit?
List your key pages, templates, and user journeys, and choose a WCAG version and level. Set up test accounts and staging access, then gather existing documentation such as previous audits, a VPAT, or known issues. Flag third-party tools like chat widgets or payment forms so the scope is clear.
Can Automated Tools Perform a Complete Accessibility Audit?
No. Automated tools detect common technical issues, such as missing alt text and insufficient contrast. However, they cannot reliably evaluate every interaction, screen reader experience, or accessibility barrier. Manual testing is essential.
What Tools Are Used for a Website Accessibility Audit?
Popular accessibility audit tools include axe DevTools, WAVE, Google Lighthouse, and Accessibility Insights. NVDA, JAWS, and VoiceOver are used for screen reader testing, while contrast checkers help evaluate color accessibility.
Does Passing a Website Accessibility Audit Mean You're ADA Compliant?
Not necessarily. An audit evaluates accessibility against a defined standard and scope. Passing its tests does not automatically guarantee legal compliance or eliminate every accessibility barrier. Requirements also vary by jurisdiction.
Who Does ADA Website Compliance Apply To?
ADA Title II applies to state and local governments, including public schools and universities. Title III applies to businesses open to the public, such as retailers, restaurants, and service providers, and many courts have applied it to their websites. Federal agencies follow Section 508. Rules vary, so confirm your obligations with legal counsel.
Final Thoughts
A website accessibility audit helps you identify and fix barriers that prevent people with disabilities from using your website. Combine automated tools, manual testing, and assistive technologies to evaluate pages, components, and user journeys against WCAG 2.2 AA.
Don't stop at identifying issues. Prioritize critical barriers, implement fixes, and retest affected elements. Make accessibility testing part of your regular website maintenance to keep your website usable and inclusive. If you need help fixing what the audit finds, our UI/UX design team improves key user flows to support WCAG 2.2 AA.











.avif)