If you sell to customers in the EU, the European Accessibility Act (transposed in Spain as Ley 11/2023) requires e-commerce sites to meet EN 301 549 — which in practice means WCAG 2.1 level AA. Most guides stop at "follow WCAG" without saying what's actually checkable in your HTML today.
We built a detector that reads the raw HTML a store serves (no JS/CSS rendering) and classifies each checkable criterion as PASS, CONFIRMED FAIL (with the exact HTML fragment), NEEDS MANUAL REVIEW, or NOT EVALUATED — never claiming a pass on something that needs a real browser or screen reader.
Real example, found on a live Spanish SMB store (Elementor theme):
<a id="elementor-menu-cart__toggle_button" href="#" aria-expanded="false">0,00 €</a>
This fails WCAG 2.4.4 (Link Purpose in Context): the link doesn't navigate anywhere real, depends on JS, and its visible text is a price, not an action. A screen reader user has no idea this is a cart toggle.
What's reliably detectable from static HTML:
- 1.1.1 images without alt
- 3.1.1 missing/invalid lang attribute
- 2.4.1 missing skip-link
- 2.4.4 links with no discernible purpose
- 1.3.1/4.1.2 form inputs without labels
- 4.1.1 duplicate ids
What's NOT detectable without a real browser/user (and any tool that claims otherwise is guessing): color contrast, keyboard focus order, screen reader compatibility.
If you want this run against your own store — portada + up to 9 pages, CSV+PDF report with the exact HTML fragment for every confirmed fail plus the legal context (EAA/Ley 11/2023 → EN 301 549/WCAG 2.1 AA) — it's $99, one-time, delivery in 48h: https://saasfactoryagents.com/eaa-wcag-audit.html
Agencies charge from €290 for a full manual audit with keyboard/screen-reader testing; this is the cheaper, explicitly-scoped automated-detection slice of that.
Top comments (0)