Auditing the accessibility of your PrestaShop store has a reputation for being heavy: install a module, grant access, configure. It's not true. A serious audit launches like a simple visit to your site, in a few minutes, with nothing to install. Here's the exact procedure, step by step.
The 5-step procedure
- 01Create a ComplAudit account (30 s)
- 02Paste your store's URL
- 03Optional: add a test account (to audit the logged-in purchase funnel)
- 04Click "Run the audit"
- 05Wait 5 to 20 min depending on the size of the site
That's all. No module to install, no FTP access, no API token. We crawl your site exactly as a visitor would — which guarantees we test what your customers really see, not a staging version.
Why the test account changes everything
Without a login, an audit stops at the cart's door. Yet it's in the logged-in funnel — address, delivery, payment — that the most serious non-conformities concentrate (unlabeled fields, steps not keyboard-navigable). Providing a test account lets you audit that critical journey, the one that weighs the most in case of a complaint.
What you get
- →Estimated RGAA 4.1 score (automated audit)
- →A list of issues sorted by severity
- →For each issue: DOM selector, exact URL, screenshot, fix suggestion
- →Location in the PrestaShop template when detectable
- →A downloadable timestamped PDF, usable as proof of a starting point
What an automated audit sees — and doesn't
Let's be honest: no automated tool covers 100% of the RGAA criteria. An engine like axe-core perfectly detects images without alt, unlabeled fields, insufficient contrast, heading structure — that's 30 to 40% of the criteria, and precisely the ones that take the most time to find by hand. The remaining 60% (relevance of an alt, tab logic, real modal behaviour) need a human complement. The automated audit does the bulk work; it doesn't replace it.
Frequently asked questions
Do I need to put the site in maintenance during the audit?
No. The crawl behaves like a normal visitor and writes nothing to your site. You can run it in the middle of the day, with no service interruption.
Are my theme and third-party modules audited too?
Yes: the audit tests the final rendering, as served to the browser, so everything that's displayed — theme, modules, sliders, pop-ups. That's the advantage of auditing the real site rather than the source code.
How often should I re-audit?
After every significant deployment, and ideally continuously: a regression can reappear at the slightest theme or module update. Regular monitoring locks in the gains.
Start your first PrestaShop audit now.
→ → Run my audit