How to Audit an E-Commerce Site for ADA Compliance
To audit an e-commerce site for ADA compliance, an accessibility professional evaluates the storefront against WCAG 2.1 AA using screen reader testing, keyboard testing, visual inspection, code inspection, and an automated scan as a review component. The audit covers the user paths that matter most for online retail: product discovery, product detail pages, cart, checkout, account creation, and order management. The deliverable is a report that identifies issues by location, references the relevant success criteria, and provides remediation guidance.
| Element | What It Covers |
|---|---|
| Standard | WCAG 2.1 AA, the standard referenced by the ADA Title II rule and used as the benchmark in Title III matters. |
| Scope | Representative templates plus full transactional paths from product discovery through order confirmation. |
| Methods | Screen reader testing, keyboard testing, visual inspection, code inspection, and an automated scan as a review component. |
| Cost | Most accessibility audits start at $1,000 and range to $3,000, with per-page pricing of $100 to $250. |
| Output | An audit report identifying issues with location, success criteria reference, severity, and remediation guidance. |
Define the Scope
An e-commerce site has hundreds or thousands of pages, but most are generated from a small set of templates. The scope of an audit should reflect that structure rather than every individual URL.
Representative coverage typically includes the homepage, a category or collection page, a product detail page, the cart, the multi-step checkout, account login and registration, the order history view, search results, and any custom page types such as a store locator or gift card flow. Auditing one product detail page evaluates the template that powers every product, so coverage scales without scanning every record.
Identify the Critical Transactional Paths
An online store stands or falls on whether a customer can complete a purchase. The audit should follow the full path a shopper takes, end to end, with a screen reader and with keyboard only.
That path includes navigating from the homepage to a product, selecting variants such as size or color, adding to cart, applying a discount code, entering shipping and billing information, selecting a payment method, and reaching the order confirmation. Every interactive control along that path is evaluated for accessible name, role, state, focus management, and error handling.
Use the Right Evaluation Methods
An automated scan loads pages and checks HTML, CSS, and ARIA against a subset of WCAG success criteria. Scans flag approximately 25% of accessibility issues, which means a scan alone leaves the majority of conformance unverified.
The remaining 75% requires human evaluation. A professional auditor uses NVDA, JAWS, and VoiceOver across Chrome and Safari, evaluates keyboard operation without a mouse, inspects code for semantic structure and ARIA usage, and checks browser zoom at 200% and 400%. The automated scan supplements this work as a review component, not as a substitute.
What the Audit Identifies on E-Commerce Sites
Certain issue patterns appear repeatedly across online retail. A thorough audit identifies them with specificity rather than flagging vague themes.
- Product imagery with missing or unhelpful alternative text on primary, gallery, and zoom views.
- Variant selectors for size, color, and style that lack accessible names or do not announce state changes.
- Add-to-cart confirmations that appear visually but are not announced to screen readers.
- Mini cart and slide-out drawers with focus management issues or missing close controls accessible by keyboard.
- Checkout form fields without programmatic labels, error identification, or error suggestion.
- Modals and overlays for newsletter signup, age verification, and shipping notices that trap focus or cannot be dismissed by keyboard.
- Filter and sort controls on category pages that rely on hover or do not communicate selected state.
Review the Audit Report
The audit report should list each issue with its page or template location, the WCAG success criterion violated, the conformance level, a severity or user impact rating, and remediation guidance specific enough for a developer to act on. Generic findings such as “improve form accessibility” indicate an inadequate audit. Specific findings name the element, the behavior, and the fix.
For an e-commerce site, prioritization should weigh both user impact and risk factor. Issues in checkout and cart carry higher weight than issues on a press release page, because a blocked checkout prevents the core function of the site.
Plan for Remediation and Re-Evaluation
The audit is the starting point. After the report is delivered, the development team works through the findings, typically in priority order, and the auditor validates the fixes. Validation confirms that each issue has been resolved without introducing new ones.
E-commerce platforms release frequent updates to themes, apps, and storefront code. A one-time audit reflects a single point in time. Ongoing monitoring through scheduled scans, paired with periodic re-evaluation of changed areas, keeps conformance current as the site changes.
An e-commerce audit done well produces a report a developer can work from and a record an organization can point to as evidence of a deliberate accessibility program.