Skip to content

Audits

WCAG audit for ecommerce: product pages, cart and checkout

How to audit an online shop against WCAG 2.2 AA: which templates to test first, the criteria for each shop component, third-party payment and an example.

Your UX Agent teamProduct
15 min read

A WCAG audit of an online shop tests its page templates and its purchase journey against WCAG 2.2 Level A and AA: 55 success criteria. In the EU, the European Accessibility Act covers e-commerce services offered to consumers. The Act names neither WCAG nor a standard: EN 301 549, which adopts WCAG, gives a presumption of conformity only once it is cited under the Act, and no version is cited yet.

Testing WCAG 2.2 Level AA, with 4.1.1 Parsing kept on the list, covers the web-page WCAG rows of both EN 301 549 V3.2.1 and V4.1.1.

Audit a shop by template and by journey. Product pages built from one template mostly share their issues, so test a few and fix the template once. The purchase is one process, and if any step from the product to the checkout fails, no page in it conforms. So the checkout comes first.

Our five-step audit method covers scope, sampling and reporting for any site. This post applies it to a shop: the order to test templates in, the criteria to check each shop component against, third-party payment and chat, and one finding written out in full.

Which law covers a shop

The European Accessibility Act (Directive (EU) 2019/882) applies to e-commerce services provided to consumers after 28 June 2025 (Article 2(2)(f)), through the national law of each member state. Article 3(30) defines e-commerce as services provided at a distance, through websites and mobile device-based services, “at the individual request of a consumer with a view to concluding a consumer contract”. If consumers in the EU can buy from your shop, it is very likely covered wherever you are based, unless you are a micro-enterprise (below).

Micro-enterprises providing services are exempt from the service requirements (Article 4(5)). A micro-enterprise employs fewer than 10 persons and has an annual turnover or an annual balance sheet total of no more than EUR 2 million (Article 3(23)). Under the EU’s SME Recommendation, which the Act’s recital 53 points to, the figures of linked and partner enterprises are added in, and your national law may word the test differently; the micro-enterprise test, worked through, shows how.

For a shop, Annex I, Section IV, point (g) adds three requirements to the general one that websites be perceivable, operable, understandable and robust:

  1. provide the accessibility information about the products and services you sell, when the responsible economic operator gives it to you;
  2. make identification, security and payment functionality, when it is part of the service, perceivable, operable, understandable and robust;
  3. provide identification methods, electronic signatures and payment services that are perceivable, operable, understandable and robust.

Sign-in and payment are named, which is why they lead the order below. We go through the Directive’s articles in the Act’s requirements for websites and online shops. National law transposes the Act and may add to it, so check the law of each country you sell to. If you also sell in the US or Ontario, see the EU, US and Ontario rules side by side.

The order to audit a shop’s templates in

Order the work by what blocks a purchase, then by reach. A failure in the checkout can stop someone buying at all; a failure in the product template repeats on every product. Test each template in its states too: empty and filled, with errors shown, signed in and out, at a phone width and a desktop width.

  1. Checkout and payment. The money path, and the steps the Act names. Include every step from the basket (the cart) to the order confirmation, the payment step even if another company runs it, and the error states: a declined card, a postcode in the wrong format, a missing field. WCAG’s own example of a complete process is an online store, from selecting products to the checkout.
  2. Basket. Every purchase passes through it: quantity changes, remove buttons, a discount-code field and totals that update.
  3. Product page. One template serves every product, so one fix reaches all of them. Images and zoom, variant pickers, the add-to-basket button and its confirmation, size guides and other dialogs.
  4. Category and search results, with filters. This is how people find products. Filters, sorting, pagination or “load more”, and where focus goes when the results change.
  5. Home page. The way in for many visitors. Most of it is shared header, menu and footer, already tested with the templates above, so test its carousel and promotional blocks.
  6. Account and sign-in. Sign-in during checkout belongs to step 1. Then registration, password reset, order history and returns. Signed-in pages need a test account.
  7. The cookie banner and site-wide widgets. The consent banner, a chat launcher, a newsletter pop-up. They sit on top of every template, so test them as a layer over the pages above. At a phone width, check that none of them covers a checkout field or button.

Then add pages chosen at random, about 10% of the structured sample, as W3C’s evaluation methodology requires, to check that the templates you picked were the right ones.

Shop components and the WCAG criteria to check

Each component below appears on most shops. The table names the WCAG 2.2 criteria to check it against, with their levels; the list under it says what to look for.

ComponentWCAG 2.2 criteria
Product images and zoom1.1.1 Non-text Content (A); 2.1.1 Keyboard (A)
Colour and size swatches1.4.1 Use of Color (A); 4.1.2 Name, Role, Value (A); 1.4.11 Non-text Contrast (AA)
Variant selects1.3.1 Info and Relationships (A); 3.3.2 Labels or Instructions (A)
Quantity steppers2.5.8 Target Size (Minimum) (AA); 4.1.2 (A)
“Added to basket”4.1.3 Status Messages (AA)
Filters and sorting3.2.2 On Input (A); 4.1.3 (AA)
Carousels2.2.2 Pause, Stop, Hide (A); 2.1.1 (A)
Address and payment fields1.3.5 Identify Input Purpose (AA); 3.3.1 Error Identification (A); 3.3.3 Error Suggestion (AA)
Billing address3.3.7 Redundant Entry (A)
Order review3.3.4 Error Prevention (Legal, Financial, Data) (AA)
Sign-in at checkout3.3.8 Accessible Authentication (Minimum) (AA)
Sticky headers, cookie banners, chat launchers2.4.11 Focus Not Obscured (Minimum) (AA)
Error summaries3.3.1 (A)
Shop components and the WCAG 2.2 success criteria to check each one against, with their levels.

What to look for on each:

  • Product images and zoom. Each image has a text alternative that says what the picture shows and the text does not, such as the colour or the back of the item. The gallery and the zoom work with a keyboard, not only on hover.
  • Swatches. Each swatch has a name, such as “Navy” or “Size 42”, and exposes which one is selected. The selected state has a cue besides colour, and its outline has 3:1 contrast against what is next to it.
  • Variant selects. Each select or group of options has a visible label, and a group of radio buttons is grouped under its name.
  • Quantity steppers. The minus and plus buttons are at least 24 by 24 CSS pixels, or spaced so they pass, and have names such as “Decrease quantity”. The new value is exposed when it changes.
  • “Added to basket”. If the confirmation does not take focus, it is exposed through a status role or a live region. W3C’s own example of a status message is a basket count that changes after “Add to Shopping Cart”.
  • Filters and sorting. Either an Apply button makes the change, or ticking a filter does not reload the page or move focus unless people are told beforehand. When a filter applies as it is ticked and people were not told beforehand, focus stays on it, because moving focus is itself a change of context, and a result count that appears is announced.
  • Carousels. A carousel that moves on its own for more than five seconds can be paused, stopped or hidden, and its controls work with a keyboard.
  • Address and payment fields. Fields for the customer’s own details carry autocomplete values such as postal-code and cc-number. Each error is described in text and names its field, with a suggested fix where one is known.
  • Billing address. The delivery address is offered again, for example with a “same as delivery address” checkbox, instead of being typed twice. W3C uses that checkbox as its own example.
  • Order review. Before the order is placed, the customer can review and correct it, or the order can be cancelled afterwards, or the entries are checked and errors offered for correction.
  • Sign-in at checkout. Password and code fields accept paste and password managers, and a sign-in step that asks people to transcribe distorted text offers another way through that does not ask them to remember, transcribe or solve anything, or replaces it with one that only asks them to recognise objects, which Level AA allows.
  • Sticky headers and overlays. A focused field or button is never entirely hidden behind a sticky header, an unanswered cookie banner or a chat launcher.
  • Error summaries. 3.3.1 needs each error identified and described in text, in no particular form. A linked summary above the form plus a message beside each field is a common way to meet it.

Payment, chat, reviews and consent: third-party steps

Part of a shop is often built by someone else: a hosted payment form in an iframe, a chat widget, a reviews widget, a consent banner. To the person buying, they are part of your page, and three things point the same way:

  • WCAG’s complete-process rule. Every page in the process must conform for any of them to. W3C’s guidance on 3.3.7 says a process can run across domains, so a checkout that includes a third-party payment provider is one process.
  • The Act names payment. Annex I, Section IV, point (g)(ii) and (iii) cover payment functionality and payment services.
  • The exclusion is narrow. Article 2(4)(d) excludes third-party content “that is neither funded, developed by, or under the control of” you. In our reading, a checkout, chat or review tool you pay for, embed or configure is part of how you provide the service, so treat it as in scope unless you are sure it is not.

WCAG’s statement of partial conformance, for parts “from uncontrolled sources”, does not change this: it begins “This page does not conform”.

In practice:

  • Test the whole journey, through the third-party steps. Tab into the payment iframe and out again, check what a screen reader announces for each card field, and trigger the provider’s own errors, such as a declined card.
  • Ask each supplier for its accessibility information: which standard and version it was tested against, when, and its known issues. Some publish it as an Accessibility Conformance Report.
  • Configure what you control. Labels, colours, language and where a chat launcher sits are often settings. A launcher that entirely covers the “Pay” button when the button takes focus fails 2.4.11, and moving it is up to you.
  • Record what you cannot fix, with the supplier’s answer and the date, so the next audit starts from it.

One finding from a checkout, written out

This finding is made up, on example.com, to show what a usable finding holds. It uses the fields of the report template linked below.

Example finding F-12, a checkout error not tied to its field, Markdown
### F-12: Checkout error does not say which field is wrong​- Criterion: WCAG 2.2 3.3.1 Error Identification, Level A  (related: 1.4.1 Use of Color)- Where: https://shop.example.com/checkout/delivery  (checkout, step 2 of 4), at 390 and 1280 px wide- Element: the message above the form, selector #checkout-alert,  from the CheckoutForm component; the field #postcode- Evidence: after "Continue to payment" with the postcode "SW1A",  the page shows only "Some of your details are not valid.  Please check and try again." above the form. The postcode  field gets a red border and no text. A screen reader does not  announce the message, and announces the field as  "Postcode, edit text", with no error.- Found by: manual check, submitting each step with wrong values,  then with a keyboard and a screen reader and browser pair- Reproduce: add any item to the basket, go to checkout, enter  "SW1A" as the postcode and select "Continue to payment".- Who it affects: screen reader users, who are not told that the  step failed or where; people who cannot tell the red border  apart; anyone searching a long form for the field in error.- Severity: critical. A screen reader user is not told which  field to correct, so they may not get past this step.- Instances: one component, on two checkout steps  (delivery and billing)- Fix: name the field and the problem in a message next to it;  add a summary above the form that links to each field in  error, and move focus to it after a failed submit.- Status: open

The fix, before and after:

Fails: 3.3.1 Error Identification, HTML
<div id="checkout-alert" class="alert">  Some of your details are not valid. Please check and try again.</div>​<label for="postcode">Postcode</label><input id="postcode" name="postcode" autocomplete="postal-code"       class="is-invalid"><!-- the only sign on the field is a red border -->
Passes: 3.3.1 Error Identification, HTML
<div id="checkout-alert" class="error-summary" tabindex="-1">  <h2>There is a problem</h2>  <ul>    <li><a href="#postcode">Postcode: enter a full postcode, like SW1A 1AA</a></li>  </ul></div>​<label for="postcode">Postcode</label><p id="postcode-error" class="field-error">Enter a full postcode, like SW1A 1AA</p><input id="postcode" name="postcode" autocomplete="postal-code"       class="is-invalid"       aria-invalid="true" aria-describedby="postcode-error">​<script>  // after a failed submit, once the summary is shown  document.getElementById("checkout-alert").focus();</script>

Why it works. The message names the field and says in words what is wrong, which is what 3.3.1 asks, and how to correct it, which is what 3.3.3 asks. The summary’s link takes a keyboard user straight to the field, and moving focus to the summary lets a screen reader read it out, starting with its heading. aria-invalid and aria-describedby make a screen reader announce the error with the field; they are good practice, though W3C’s guidance says 3.3.1 does not require that link; 1.3.1 and 4.1.2 can. The red border can stay, now with text next to it.

Can automated tools catch this? No. axe-core has no rule for 3.3.1, and no check of ours decides it: whether a message identifies its field is a judgment, and the message only appears after a submit. Submit each checkout step empty and with wrong values, including errors the server and the payment provider return.

What it costs, and what you get back

Templates and states move the price more than the number of products does: a checkout of four steps, each with its error states, is many views to test. We compare published prices, with their sources, in our guide to what an audit costs and why.

What you get back should be a report that lists the sample by template and checkout step, every failure with its evidence, and the criteria nobody tested: a report template you can download, with a sample report, sets that out.

To see what our checks find on one of your product pages, scan a page of your shop for free, without signing up.

This is general information, not legal advice: check the national law of each country you sell to.

Frequently asked questions

Which WCAG level should an ecommerce website meet?

Aim for Level AA, which includes every Level A criterion: 55 success criteria in WCAG 2.2. In the EU, no harmonised standard is cited under the European Accessibility Act yet. EN 301 549 V3.2.1, cited under the Web Accessibility Directive for public-sector sites, adopts WCAG 2.1 Level AA, and V4.1.1, which awaits citation, adopts WCAG 2.2 Level AA, so testing WCAG 2.2 Level AA with 4.1.1 Parsing covers the web-page WCAG rows of both. Your national law may say more, so check it.

Which pages of an online shop should an accessibility audit include?

A representative page of each template, such as the product page, a category page, search results, the basket, the home page and the account pages, plus every step of the checkout, including the payment step and its error states. Test site-wide widgets such as the cookie banner and a chat launcher on top of those pages, at a phone width and a desktop width.

Does a third-party payment form count as part of the shop?

For testing, yes. WCAG treats every step of a purchase as one process, which can run across domains, and the European Accessibility Act names payment functionality and payment services in Annex I. Its exclusion for third-party content covers only content you neither fund, develop nor control. Test the payment step with the rest of the checkout, and ask the supplier for its accessibility information.

Can an automated tool audit a checkout?

Only part of it. Automated rules can find, for example, fields with no accessible name, low contrast and small targets on the pages they load. Whether an error message names its field, what happens after a card is declined and what a screen reader announces at each step need a person, and a tool that does not submit the form never sees the errors that follow.