Blank checklist, printable form
E-Commerce Accessibility Checklist
EAA Annex I Section IX, E-Commerce Services
Blank checklist for offline completion.
Tick one box per row. Add comments and evidence references in the Notes column as needed.
Product Browsing & Discovery
EAA Annex I §IX, Product listings, search, and filtering must be accessible to all users.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| WCAG 1.1.1 | Critical | Product images have descriptive alt text, not just the product name.Alt text should describe what the image shows: 'Blue cotton crew-neck t-shirt, front view' not just 'T-shirt'. Multiple images need distinct descriptions. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Critical | Product information (price, availability, specifications) is available in text, not image-only.Pricing in images cannot be read by screen readers. All product data must be real text or have programmatic alternatives. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Critical | Pricing is programmatically determinable, not embedded in images.Screen readers must be able to announce the price. Use text or aria-label, never price as part of a product image. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 2.1.1 | Critical | Filtering and sorting controls are keyboard-operable.Category filters, price sliders, sort dropdowns, all must work with keyboard alone. Sliders need arrow key support. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 4.1.3 | Major | Search results count is announced to screen readers.When results update after filtering or searching, announce 'Showing 24 results for blue shirts' via aria-live region. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Product Detail Pages
Individual product pages must present all information accessibly.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| WCAG 2.1.1 | Critical | Size, colour, and variant selectors are keyboard-operable and labelled.Dropdown menus, colour swatches, and size buttons must have accessible names and be operable with keyboard. Colour swatches need text labels, not just colour. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 4.1.2 | Critical | Interactive elements (add to cart, wishlist, compare) have accessible names.Icon-only buttons like a heart icon must have aria-label='Add to wishlist'. The cart button must clearly announce its purpose. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.2.2 | Major | Product videos have captions.Demo videos, unboxing videos, and product walkthroughs must have synchronised captions. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Major | Product specifications are presented in an accessible table with headers.Spec tables (dimensions, materials, weight) must use proper <th> headers so screen readers can announce column/row associations. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Cart & Checkout
The purchase flow from cart to payment confirmation must be fully accessible.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| WCAG 4.1.3 | Critical | Cart contents are announced to screen readers when updated (aria-live).When a user adds or removes an item, the cart count and summary must be announced, 'Item added. Cart: 3 items, €45.00'. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 3.3.2 | Critical | All checkout form fields have visible, persistent labels, not just placeholders.Name, address, payment fields all need <label> elements. Placeholder text disappears on input and is not a substitute. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 3.3.1 | Critical | Checkout form errors are identified in text and describe the specific problem.'Please enter a valid email address' not just 'Error in field 3'. Error messages must appear adjacent to the field. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.5 | Major | Address fields use correct autocomplete attributes.Use autocomplete='shipping address-line1', autocomplete='cc-number' etc. This helps autofill tools and assistive technology. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 2.1.1 | Critical | All payment methods offered are keyboard-accessible.Credit card forms, PayPal redirects, Apple Pay buttons, all must be reachable and activatable with keyboard. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 3.3.4 | Critical | Order review step is provided before final submission.For financial transactions, users must be able to review their order, correct errors, and confirm before the charge is processed. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Post-Purchase & Account
Order confirmations, account management, and returns must also be accessible.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| EAA Art. 4 + WCAG 1.3.1 | Critical | Order confirmation is available in text (HTML email), not just a visual receipt image.Confirmation emails must be HTML with proper structure, not just a screenshot of the receipt. PDF receipts must be tagged. Under the EAA, the entire service, including post-purchase communications, must be accessible. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 2.1.1 | Critical | Account creation and login are keyboard-accessible.Registration forms, password fields, 'show password' toggles, and social login buttons must all be keyboard-operable. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 3.3.8 | Major | Account creation does not require CAPTCHA without an accessible alternative.Image CAPTCHAs exclude blind users. Use invisible CAPTCHA, email verification, or phone verification instead. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Art. 4 + WCAG 2.1.1 | Major | Returns and refund process is accessible end-to-end.The return request form, shipping label download, and refund status page must all be accessible. The EAA's general accessibility obligation covers the full service lifecycle, don't make returns harder than purchasing. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Minor | Customer reviews section is accessible (submission form + display).Review star ratings need text alternatives. The review submission form needs labels. Reviews must be navigable by heading. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Cookie Consent & Legal
Cookie banners and legal notices must not block accessibility.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| WCAG 2.1.1 | Critical | Cookie consent banner is keyboard-operable.Users must be able to Tab to the banner, activate Accept/Reject, and dismiss it entirely with keyboard. It must not trap focus. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 4.1.2 | Major | Cookie consent controls have accessible names and roles.Buttons must be <button> elements with clear text. Custom-styled divs acting as buttons need role='button' and aria-label. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 2.4.3 | Major | Cookie banner does not break focus order for the rest of the page.After dismissing the banner, focus should return to a logical position in the page, not jump to the end or get lost. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |