Digital accessibility · Spain and the EU
Can your checkout be completed without a mouse?
For most online stores the answer is no — and that is both a lost-sales problem and an open compliance problem. I scan your five critical templates, tell you exactly what fails and against which criterion, and fix it in your own theme. Not with an overlay.
Free · 5 templates · a one-page report with the findings, no strings attached.
- 95.9%
- of home pages have detectable WCAG failures
- 56.1
- average detected errors per page
- 51%
- have form fields with no label
- +155%
- errors on PrestaShop vs. the average
Source: WebAIM Million, February 2026 (1,000,000 home pages).
It is not a legal problem. It is a legal problem AND a conversion problem.
The same defects that make a store unusable with a keyboard or a screen reader are the ones that make people abandon the cart. They are the same defects. Fixing them pays for itself twice.
- 01
Fields with no label
The browser cannot autofill them, the screen reader announces nothing, and on mobile the placeholder disappears as soon as you type. It is the most expensive failure in a checkout.
- 02
Invisible focus
The theme removed the outline for aesthetics. Anyone navigating with a keyboard has no idea where they are. So does anyone using a laptop with a broken trackpad.
- 03
Errors flagged in red only
No text, no association with the field. The customer does not know what to correct, tries twice and leaves.
- 04
Buttons with no accessible name
Cart, close, filter, quantity. An icon with no label is a dead end for assistive technology and ambiguous for everyone else.
None of this requires redesigning your store. It requires knowing exactly where it is and touching the theme with a steady hand.
The rules, with the article number
There is not one obligation. There are two — and the second one nobody is telling you about.
Most Spanish content on this topic tells a single story: the European Accessibility Act applies from 28 June 2025 unless you are a micro-enterprise. That is incomplete. The micro-enterprise exemption in the EAA does not exempt you from the other track.
European Accessibility Act
- Who
- E-commerce services aimed at consumers
- Deadline
- In force since 28 June 2025
Directive (EU) 2019/882, transposed in Spain by Law 11/2023 of 8 May. It covers e-commerce services as defined in Annex VII.32. It exempts micro-enterprises providing services (art. 3.3). It requires the service to be perceivable, operable, understandable and robust (Annex I, sections III and IV), with specific requirements for identification, security and payment.
Law 11/2023, arts. 2.2.f, 3.1, 3.3, 13.2 · Annex I sec. IV.g · Annex VII.32
Royal Decree 193/2023
- Who
- Any website offering goods or services to the public
- Deadline
- 1 Jan 2029 (new) · 1 Jan 2030 (existing)
Article 14.2 obliges owners of websites and apps not publicly funded whose content refers to goods and services available to the public to meet priority A and AA requirements. It contains no micro-enterprise exemption. If you are under the EAA threshold, this is still your deadline — and it is close enough that it already affects any redesign you are planning.
RD 193/2023, art. 14.2 and sixth final provision
The dates that matter
28 Jun 2025
Title I of Law 11/2023 comes into force, including the supervisory authorities regime.
18th final provision, para. 2
28 Feb 2026
The state Technical Unit is created: a point of contact that receives complaints and acts as supervisory authority where no regional authority has been designated.
RD 143/2026, art. 3.g and 3.h
1 Jan 2029
RD 193/2023 becomes enforceable for new privately owned goods and services.
Sixth final provision, b)
1 Jan 2030
RD 193/2023 becomes enforceable for existing privately owned goods and services, through reasonable adjustments.
Sixth final provision, c)
And what happens if you do nothing
Law 11/2023 sets no fine amounts of its own: its article 30 refers to sectoral legislation and, failing that, to Title III of Royal Legislative Decree 1/2013, which sets a range from €301 to €1,000,000 depending on classification. Before that, in the Valencian Community, article 100.4 of Law 8/2024 requires a formal notice giving between fifteen days and two months to fix the issue before proceedings are opened. That is the honest picture: the first step is not a fine, it is a short deadline. The problem is that fifteen days is not enough to fix an inaccessible checkout if you have not done the diagnosis first.
Law 11/2023 art. 30 · RDL 1/2013 arts. 83 and 96 · Law 8/2024 (Valencian Community) arts. 93 and 100.4
Does it apply to me?
The micro-enterprise threshold, read properly
Half the sector gets this definition wrong. The headcount criterion is cumulative; the two financial criteria are alternatives. This is the literal wording of Annex VII.16 of Law 11/2023.
You are a micro-enterprise if, at the same time:
- You employ fewer than 10 people, and
- your annual turnover does not exceed €2M, or your annual balance sheet total does not exceed €2M.
If you meet that, you are exempt from the service requirements of Law 11/2023 (art. 3.3). You are not exempt from RD 193/2023, whose deadline is 2029/2030.
12 people, €900k turnover
Not exemptThe headcount criterion fails, so the exemption does not apply. Track A has been in force since June 2025.
6 people, €3M turnover, €1.5M balance sheet
Exempt from Track AIt qualifies through the balance sheet criterion. Track B still applies, with a 2029/2030 horizon.
Pure B2B, no consumers
Needs reviewAnnex VII.32 requires a consumer for the service to fall under the EAA. Track B does not require one. This is one of the points I flag for a lawyer rather than settle myself.
Your platform already tells me a lot
The WebAIM Million measures detected errors per page by platform. E-commerce platforms perform notably worse than the average, and one of them is in a league of its own.
PrestaShop
+155.3%143.2err./page
More than double the average of the million pages measured. Very common in Spain, which makes it the highest-value segment to work on.
Magento
+35.0%75.8err./page
Complex checkouts, many custom modules and a large surface for regressions on every deployment.
Shopify
+33.9%75.1err./page
Themes that strip the focus outline for aesthetics and apps that inject inaccessible markup you did not write.
WordPress
−5.8%52.8err./page
Better than average as a CMS, but the report does not break out WooCommerce separately: the checkout is usually where the failures concentrate.
Average across the million pages measured: 56.1 errors per page.
Source: WebAIM Million, February 2026.
The service
Three layers. You can stop after any of them.
You are not buying an audit, you are buying the end of an open problem. Each layer stands on its own and each one has its scope written down, so nobody discovers halfway through what was and was not included.
Diagnosis
€390
+ VAT · delivered in 5 working days
Automated scan plus manual verification of your five critical templates, with findings prioritised by effort against impact.
Included
- Home, category, product page, cart and checkout
- axe-core over a real browser, plus manual keyboard and focus testing
- Each finding with its WCAG 2.2 criterion, user impact and conversion impact
- Correct code snippet for each finding
- Check for the conformity information required by art. 13.2
- 45-minute call to walk through the report
Explicitly excluded
- Applying the fixes (that is the next layer)
- Authenticated areas or the customer account
- Native mobile apps
- Legal advice: I am not a lawyer and I do not give legal opinions
Remediation
from €1,900
+ VAT · fixed price after diagnosis
I apply the fixes to your Shopify, WooCommerce or PrestaShop theme, retest and leave dated evidence.
Included
- Fixes applied to the theme, not on top of it
- Priority on the purchase path: login, cart, checkout, payment
- Retest and before/after report with dates
- Conformity information drafted against art. 13.2 of Law 11/2023
- Complaints channel and handover documentation
- 30-day warranty on everything fixed
Explicitly excluded
- Redesign or restructuring of the store
- Third-party content outside your control (art. 2.4.d)
- Fixes to paid apps whose code you cannot modify — those are reported to the vendor
- New content published after handover
Monitoring
€79/month
+ VAT · cancel any time
Monthly rescan, regression alerts after each deployment, updated statement and a dated evidence trail.
Included
- Monthly scan of the critical templates
- Alert when a deployment breaks something that used to work
- Dated evidence history to demonstrate diligence
- Conformity information kept up to date
- Adaptation when the technical standard changes
Explicitly excluded
- Remediation of new defects (quoted separately or included in an hours pack)
- 24/7 support: response within one working day
Prices exclude VAT. The diagnosis is credited in full against the remediation if you hire it within 30 days.
How I work
Four steps, no surprises. Every scan only touches public pages, respects robots.txt, sends at most one request per second and identifies itself with a contactable user agent.
- 01
Free scan
You give me the domain. I scan five templates and send you a one-page report with the findings. No commitment, no call required.
- 02
Full diagnosis
Automated plus manual. Every finding with its criterion, its impact and the code that fixes it, sorted by effort against impact.
- 03
Remediation
I work on the theme, on a branch or a duplicate. You review before it goes live. Retest and dated evidence.
- 04
Monitoring
Monthly rescan and alerts. A live store breaks accessibility on every deployment — that is not a sales pitch, it is how software works.
What I will not do, and why it matters to you
These limits are the product, not obstacles. If someone offers you the opposite, that is your signal.
No overlay widgets
The one-line-of-JavaScript layers that promise accessibility do not deliver real conformance, are discredited by the accessibility community and are a reputational liability. I will not install one for you, and if you already have one I will tell you what it is actually covering.
I will never tell you that your site "breaks the law"
Automated tools detect part of the WCAG criteria, never all of them. What I can state is: N automatically detectable failures against criteria X, Y and Z, on these pages, on this date. Anything beyond that is sales talk, and it is the kind that collapses in front of an informed prospect.
No fear as a sales lever
I am not going to open a conversation with a fine. I am going to open it with three unlabelled fields in your checkout, which is also a measurable conversion problem.
Respectful scanning
Public pages only, robots.txt respected, one request per second per domain, identifiable user agent, never authenticated areas, never enough volume to degrade your service.
That is possible, and if the scan comes back clean I will tell you so in writing and it costs you nothing. But note that article 14.2 of Law 11/2023 states that even when a service is subcontracted, accessibility must not be compromised and the service provider remains bound. The obligation is yours, not your agency's.
Free scan
Give me your domain and I will tell you what fails
Five templates, one page of findings, each one with its WCAG 2.2 criterion. No commitment and no call required: if the report is useful and you want to go further, we talk. If not, you keep the report.
I take on a limited number of projects at a time.
Request your free scan
The domain is the only thing I really need. I reply within one working day.