Why Prestashop and EAA
PrestaShop powers hundreds of thousands of online stores with a strong footprint among European small and mid-sized merchants — exactly the e-commerce category the European Accessibility Act regulates. Since June 2025 an inaccessible storefront is legal exposure in every EU market, and payment providers and marketplaces increasingly ask merchants for documented conformance. The typical PrestaShop store stacks a purchased theme, a dozen modules and multiple languages on top of the core — and each layer can quietly introduce the exact defects that fail WCAG 2.1 AA.
E-Commerce Is In Scope
Online shops have no micro-enterprise exemption under the EAA. If you sell to EU consumers, WCAG 2.1 AA applies to your product pages, checkout and account area.
Marketplace Themes Vary
The theme controls nearly all rendered HTML — heading hierarchy, button markup, focus styles and contrast. Quality varies wildly between marketplace themes.
Module Risk
Filter widgets, sliders, reviews and newsletter popups usually come from third-party module vendors with unknown accessibility quality. Each needs its own review.
Common Prestashop Failures
Across PrestaShop storefronts, these defects dominate:
Product Image Legends
Bulk imports routinely skip the Legend field, leaving category grids full of images with no alt text at all.
Faceted Filter Modules
Filter facets rendered as clickable divs without keyboard support or aria-expanded — screen-reader users cannot narrow a product grid.
Quantity & Variant Inputs
Custom steppers replacing native number inputs, colour swatches without labels or selected-state announcements.
Checkout Steps
Ajax-swapped checkout sections that neither move focus nor announce errors; payment fields without associated labels.
Popups & Toasts
Newsletter modals that trap keyboard focus, and "added to cart" confirmations shown visually only — no ARIA live region.
Promotional Contrast
Sale badges and banner text in brand colours below the 4.5:1 minimum — the single most common automated finding on EU shops.
Theme and Backoffice Fixes
Most fixes happen either in your theme templates or right in the back office:
Back office first: product image alt text lives in Catalog → Products → Photos (the Legend field); shop-wide language in International → Localization; colours and typography in Design → Theme & Logo. Fill these in properly before touching any code.
Theme semantics: restore real landmarks (header, nav, main, footer), one h1 per page, and product titles as real headings in grid templates — many marketplace themes render them as styled divs.
Native inputs: replace custom quantity steppers and selects with native elements styled to match — they inherit keyboard and screen-reader behaviour for free.
Focus & ARIA states: style :focus-visible instead of removing outlines; give filter toggles aria-expanded and result-count updates an aria-live region; every Ajax section swap moves focus to its new content.
Contrast tokens: fix grey-on-grey price and sale-badge text once in the theme's colour variables, then re-verify across banners and buttons.
Module Audit
Treat every third-party module as an accessibility unknown until proven otherwise. On staging, walk each module's complete flow by keyboard only, then with a screen reader: install, configure, use, undo. Faceted search, carousels, cookie banners and newsletter popups deserve special scrutiny — they are the categories with the worst track record. Where a module fails and the vendor offers no fix, decide deliberately: replace it, wrap it with a corrective layer, or document it as a limitation in your accessibility statement with a workaround path. Re-run your scan after every module install and every PrestaShop upgrade — updates silently reintroduce old bugs wherever vendor files were patched directly.
Audit Workflow
A repeatable PrestaShop audit process for merchants and agencies:
1. Automated crawl of home, category, product, CMS and checkout templates — expect 20-50 distinct findings on a typical store.
2. Transactional journeys: complete search → filter → product → cart → checkout end-to-end by keyboard, then by screen reader. These journeys carry the EAA risk.
3. Module pass: audit each installed module's widgets individually.
4. Fix in back office where possible, otherwise in a child theme — never patch core or vendor files directly.
5. Deliver: findings report, re-scan verification, and an accessibility statement with conformance status and documented limitations. Re-audit after every upgrade and major module change.
The back office fixes are free. The report you hand a client is not.
The five-step audit workflow above, this guide and the free Accessibility Scanner stay free forever — no account, no trial, no limit on how many PrestaShop stores you scan.
What they do not give you is step 5. It says deliver a findings report, a re-scan verification and an accessibility statement, but the scanner hands you a score in a browser tab — not a file an enterprise procurement team can file. Pro adds the GDPR/cookie and NIS2/security checks, and the whole report as a PDF you can attach to a client email or keep beside the accessibility statement.
| What you get | Free | EUComply Pro — $79/year per website |
|---|---|---|
| This guide and the 5-step audit workflow | this page, in full | included |
| Scanning a client's PrestaShop store | the accessibility checks — 15 WCAG rules, contrast included | the same 15 rules |
| Result | score and grade for the page | included |
| The report | the whole report on the page | included |
| The file you attach to a client email | — | pdf download of the whole report as a file |
| Checks only a server can make | — | GDPR/cookie and NIS2/security checks — 18 more, 33 in all |
The licence covers one website. If you only need to know whether a PrestaShop store passes, the free scanner is the whole answer — you never need to pay for anything.
Going Deeper
Run the free scanner across your storefront first — product grids, filter widgets and CMS pages are where automated findings cluster.
Frequently Asked Questions
Does the EAA apply to my small PrestaShop store?
Yes for e-commerce: online shops have no micro-enterprise exemption under the EAA. A small PrestaShop store selling to EU consumers is in scope regardless of headcount.
Is PrestaShop accessible out of the box?
The default Classic theme provides reasonable semantics and responsive markup, but most shops customise themes, add modules and translate content — each step can introduce regressions like missing labels, generic link text or low-contrast banners.
Where do I fix image alt text in PrestaShop?
Catalog → Products → open the product → Photos tab → the Legend field. Bulk-imported catalogues often leave this empty across hundreds of products; the scanner finds them all in one pass.
Do purchased themes come accessible?
Some do better than others, but marketing claims are unreliable. Always scan a full page of your live theme rather than trusting the demo — heading structure, focus styles and contrast are where themes most often fail.
How long does remediation take?
A typical mid-size store needs 1-4 weeks depending on theme customisation depth and module count. Back-office fixes (alt text, language, settings) can be done in days; theme template work takes longer.
Tools and guides
Magento Accessibility: EAA Compliance for Your Store
Accessibility guide for Magento and Adobe Commerce stores: Luma/theme fixes, checkout and account flows…
EAA Accessibility Checklist for Agency Websites
What Does an Accessibility Audit Cost in 2026?
Squarespace Accessibility: An EAA Compliance Guide
Squarespace accessibility guide for the European Accessibility Act and WCAG 2.1 AA.
Wix Accessibility: An EAA Compliance Guide
How to make a Wix site meet WCAG 2.1 AA and the European Accessibility Act.
Free e-book: EAA Compliance Checklist for WordPress Sites
The complete guide is available as a free EPUB — no signup required.
Get the free e-book →Want all six guides? Complete EU Compliance Bundle — all six listed together, each a free EPUB.