The demand letter arrived three weeks after the store launched a new checkout theme. The violation cited: unlabeled form fields in the address entry step, making the checkout inaccessible to screen reader users. The settlement request was $18,500. The store ran PrestaShop with a premium theme from a well-known marketplace vendor.
**PrestaShop itself does not guarantee ADA or WCAG compliance, and neither does any theme sold in the PrestaShop Addons marketplace.** The platform gives you the engine; what you build with it — and what you install on it — is your compliance responsibility. In 2025, more than 5,100 ADA federal accessibility lawsuits were filed in the United States, a 37% year-over-year increase according to UsableNet, and e-commerce checkout flows are among the most frequently cited failure points.
For PrestaShop's 300,000+ global merchants, many of them selling into both US and EU markets, the risk in 2026 is no longer theoretical.
## Why Checkout Is the Highest-Risk Area on PrestaShop Sites
ADA complaints against e-commerce merchants concentrate heavily on the checkout flow — not because the homepage is less important, but because checkout failure is the clearest argument for denial of access. A blind user who cannot complete a purchase has been denied the same commercial opportunity as a sighted user. That's the core legal theory, and it applies to every unlabeled field in a PrestaShop address form.
PrestaShop's default checkout modules have improved over time, but the default theme's form implementation has historically relied on placeholder text to communicate field purpose — a pattern that fails WCAG 1.3.1 (Info and Relationships). Placeholder text disappears when a user begins typing and is not reliably announced by screen readers as a form label.
Custom themes compound this. Most third-party PrestaShop themes are designed visually first and accessibility last — or not at all. A theme that looks beautiful in a browser may present a completely unlabeled form to a screen reader user.
## The Most Common WCAG Failures in PrestaShop Checkout
These are the violations a JavaScript-rendering website accessibility checker consistently finds across PrestaShop storefronts, particularly in the checkout flow:
| Element | Common Failure | WCAG Criterion | Fix Effort |
|---------|---------------|----------------|-----------|
| Address form inputs | Placeholder text used as label; `` not associated | 1.3.1 Info and Relationships | Low — add `` to each input |
| Email / phone fields | Input purpose not declared via `autocomplete` attribute | 1.3.5 Identify Input Purpose | Low — add autocomplete values |
| Checkout step indicators | Progress steps are visual-only, no screen reader announcement | 1.3.3 Sensory Characteristics | Medium — add aria-label or aria-current |
| Error messages (validation) | Errors appear visually but not announced to screen readers | 4.1.3 Status Messages | Medium — wrap in `aria-live="polite"` region |
| "Confirm Order" button | Button text identical across multiple steps (no context) | 2.4.6 Headings and Labels | Low — add aria-label with step context |
| Quantity input in cart | No label programmatically associated with quantity field | 1.3.1 Info and Relationships | Low — add `` or aria-label |
| Product images (listing) | Alt text missing or set to filename / SKU | 1.1.1 Non-text Content | Low — populate alt attribute from catalog |
| Payment method selector | Radio buttons lack visible focus indicator | 2.4.11 Focus Appearance (WCAG 2.2) | Medium — add CSS focus styles |
| Carrier selection step | Custom styled radio buttons not keyboard-operable | 2.1.1 Keyboard | High — custom keyboard handler required |
| Module-injected pop-ups | Focus not trapped inside modal; no keyboard close | 2.1.2 No Keyboard Trap | High — JS focus management required |
| Cookie consent banner | Banner not keyboard-accessible; focus not set on open | 2.1.1 Keyboard | Medium — vendor-dependent |
| Breadcrumb navigation | Current page not marked with `aria-current="page"` | 4.1.2 Name, Role, Value | Low — add aria attribute to breadcrumb |
## The Module Marketplace Blind Spot
PrestaShop's strength is its module ecosystem — over 4,000 modules covering everything from payments to product reviews to loyalty programs. That ecosystem is also its biggest accessibility liability.
Modules are developed independently, and PrestaShop does not audit modules in the Addons marketplace for WCAG compliance. A payment gateway module may inject a form with no accessible labels. A loyalty points module may add interactive elements with no keyboard support. A newsletter pop-up module may render a modal that traps keyboard users indefinitely — the precise failure that WCAG 2.1.2 (No Keyboard Trap) was written to prohibit.
When modules inject content into the PrestaShop DOM at runtime, static HTML scanners miss it entirely. The failure only appears when the live JavaScript-rendered page is evaluated — the way a browser (and a screen reader) actually experiences it.
ADAGuard renders your full PrestaShop storefront with a complete JavaScript engine before scanning, catching violations in dynamically loaded module output. This is where many tools fall short: they check what was in the initial HTML, not what ended up in the DOM after all modules ran.
## The EAA Risk for EU-Facing PrestaShop Merchants
PrestaShop is particularly popular in France, Spain, and other EU markets — and the European Accessibility Act (EAA), which entered full enforcement on June 28, 2025, applies directly to these merchants.
The EAA requires e-commerce websites selling to EU consumers to meet EN 301 549, which incorporates WCAG 2.1 Level AA. The stakes are significant. France — where PrestaShop originated and has its largest user base — has already issued formal notices to major retailers including Carrefour, Auchan, and Leclerc for inaccessible e-commerce platforms. France's maximum fine for repeat violations is €250,000, with a base fine of €7,500 per violation for legal entities.
Spain's maximum fine for very serious EAA violations is €1,000,000. Germany's BFSG law, which transposed the EAA, enables private Abmahnungen — competitors can initiate legal action against each other for accessibility failures — with private warning letters beginning in August 2025.
For a PrestaShop merchant based in France or Spain, or any merchant selling into those markets, the EAA is not a future concern. It is an active compliance obligation with real enforcement already underway.
ADAGuard scans against both ADA and EAA requirements simultaneously, since both reference WCAG 2.1 AA as the compliance standard. One scan covers both jurisdictions.
## Testing PrestaShop Checkout Correctly
Most free accessibility tools — browser extensions, bookmarklets, and basic online scanners — test the page the tool can see, which is usually just the publicly accessible homepage and product pages. They cannot test checkout.
PrestaShop's checkout is session-gated: you must add a product to the cart and begin the checkout process before the address, carrier, and payment steps appear. A scanner that can't navigate the checkout flow will never evaluate the steps where accessibility failures are most legally consequential.
ADAGuard's authenticated scanning is designed exactly for this. It connects to your live PrestaShop store, adds a product, navigates through the checkout flow as a real user would, and checks every step — address entry, shipping selection, payment, confirmation — against the full WCAG 2.1 AA standard. The free scan at [adaguard.io](https://www.adaguard.io) covers your public-facing pages with no signup; authenticated checkout scanning is available on paid plans.
For the checkout-specific fixes, the scan output identifies each failing element with its CSS selector, the WCAG criterion violated, and specific fix guidance — so a developer can go directly to the right template file.
## What the FTC's 2025 accessiBe Ruling Means for PrestaShop Merchants
In 2025, the FTC fined accessiBe $1 million for misleading claims about its overlay widget's ability to make websites WCAG compliant. The DOJ has separately stated that overlays alone do not constitute WCAG compliance.
Many PrestaShop merchants have installed accessibility overlay modules — accessiBe, UserWay, or similar products available in the Addons marketplace — believing they transfer accessibility compliance responsibility to the vendor. They don't. The accessibility widget does not make your checkout forms labeled. It does not fix your module-injected keyboard traps. It does not write alt text for your product images.
Installing an overlay module does not reduce your legal exposure under the ADA or EAA. In some cases, it may increase it, by creating a false record of "attempted compliance" that plaintiff attorneys use to argue bad faith.
The only defensible approach is identifying your actual violations, fixing them in the code, and maintaining a monitoring program that catches regressions as modules update and themes change.
## Priority Fixes for PrestaShop Merchants
If you're starting a WCAG remediation effort on a PrestaShop store, work in this order:
**1. Checkout form label associations** — review every input in the address, carrier, and payment steps. Each must have a `` element with a `for` attribute matching the input's `id`, or an `aria-label` directly on the input. Remove any case where placeholder text is the only field identifier.
**2. Error message live regions** — wrap all client-side validation error containers in an `aria-live="polite"` region so screen readers announce errors when they appear. In PrestaShop's default checkout, this typically requires modifying the checkout JavaScript controller.
**3. Product image alt text** — address this in the catalog data, not template-by-template. Ensure the `alt` attribute for every product image pulls from a catalog field that's consistently populated with descriptive text.
**4. Focus management in module-injected modals** — audit every module that adds a modal or overlay. Each must trap focus inside the dialog when open and return focus to the trigger element on close. Module-by-module, this is a JavaScript fix in the module's front controller.
**5. Autocomplete attributes on checkout form** — add `autocomplete="given-name"`, `autocomplete="family-name"`, `autocomplete="street-address"`, `autocomplete="postal-code"`, `autocomplete="email"` to the relevant checkout inputs. This is a low-effort fix that satisfies WCAG 1.3.5 and also improves form completion rates.
## The 30-Second Fix
The violations that cost PrestaShop merchants $15,000–$50,000 in demand letter settlements are the same violations a proper website accessibility checker catches in under 60 seconds.
Paste your PrestaShop store URL at [adaguard.io](https://www.adaguard.io) — free, no signup — and get a complete WCAG 2.1 AA scan of your live site, including module-injected content, rendered in a real JavaScript environment. ADAGuard checks 19 violation categories covering 50+ criteria, flags every failing element with its exact location and fix guidance, and covers both ADA and EAA requirements in a single scan.
For EU-facing stores, that single scan may be the most important compliance step you take in 2026.
