How to Run a Website Accessibility Audit on Your Online Store
A website accessibility audit tests your store against WCAG 2.1 or 2.2 Level AA in three passes: an automated scan for machine-detectable errors, manual keyboard and screen reader testing of key shopping journeys, and prioritization by severity and traffic. Automated checkers catch only a portion of issues, so treat their output as a starting list, not a verdict.
An ADA compliance checker is usually the first tool store owners reach for, and it is a useful first step. It is also where most audits stop too early. This guide walks through a complete accessibility audit for an online store in eight steps, using free tools, so you end with a prioritized list your team or agency can act on. It is general information, not legal advice.
Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval.
What does a website accessibility audit check?
A website accessibility audit checks whether people using assistive technology can perceive, operate, and understand your site. On a store, that means a shopper who uses a screen reader, a keyboard only, magnification, or voice control can find a product, choose options, add it to the cart, and pay.
How do you run an accessibility audit on an online store?
Run an accessibility audit on an online store in eight steps. Plan for a few hours for a small store and longer for a store with many templates or custom features.
- Define the scope by template. List one representative page for each template: home, a collection, a product with variants, search results, cart, each checkout step, account sign-in, and any custom tools such as product builders.
- Run an automated scan on each page. Use a free checker such as WAVE (WebAIM), axe DevTools (Deque), or Lighthouse in Chrome. Export the results with WCAG criteria and severity.
- Test with a keyboard only. Unplug the mouse. Use Tab, Shift+Tab, Enter, Space, arrow keys, and Escape to move through each page. Check that focus is always visible, that nothing traps focus (modals, mini-carts, cookie banners), and that you can complete a purchase.
- Test with a screen reader. Use VoiceOver on Mac or iPhone, NVDA on Windows, or TalkBack on Android. Listen for product names, prices, variant options, error messages, and button labels.
- Check forms and checkout closely. Every field needs a visible label, errors need to be announced and explained, and payment steps, including third-party payment frames, need to be reachable and usable.
- Review third-party widgets. Test reviews, live chat, pop-ups, loyalty widgets, and embedded video. They are part of your store to a shopper.
- Prioritize by severity and traffic. Rank each issue by how badly it blocks a task and how many shoppers reach that page, using the matrix below.
- Address, re-test, and schedule the next run. Assign owners, re-test each change with the same tool and method, and re-run automated scans after every release.
How should you prioritize accessibility issues?
Prioritize accessibility issues by combining severity with traffic. Automated tools such as axe classify impact as critical, serious, moderate, or minor. Traffic tells you how many shoppers meet the barrier. Start where both are high.
Why aren't automated accessibility checkers enough?
Automated accessibility checkers aren't enough because many WCAG criteria require human judgment. A tool can detect that an image has no alt text; it cannot tell whether existing alt text describes the product accurately. It can detect missing labels, but not whether an error message makes sense or whether a custom variant selector works with a screen reader.
Store teams notice the gap in practice. An ecommerce leader told Noibu in a September 2026 call that the AI compliance checker their team had used caught only about a quarter of the problems, and that they couldn't see what disabled shoppers actually experienced. Pairing automated results with manual testing, and with session data showing where shoppers struggle, closes more of that gap.
How often should you run an accessibility audit?
Run a full accessibility audit at least once a year and before major redesigns, and run automated scans after every release. Theme updates, new apps, promotional pages, and seasonal campaigns all introduce new markup, and a store that passed in spring can fail by Black Friday.
Continuous checks are where AI agents help most. Noibu's ADA Agent helps teams find and address accessibility issues against WCAG standards, surfaces them by page and journey so teams can start with the purchase path, and drafts changes that a person reviews before anything ships. It supports your audit process and manual testing; it does not certify or guarantee compliance.
Frequently asked questions
Related topics
- Noibu's ADA Agent
- ADA for ecommerce websites: what online stores need to know
- How to do an ecommerce site audit
- How to find where customers drop off in checkout
This article is general information about website accessibility and is not legal advice.
.png)