Spain accessibility laws: RD 1112/2018, Ley 11/2023 & WCAG

Which Spanish laws regulate digital accessibility?

Three laws carry the operative weight, each targeting a different layer of obligation.

• Real Decreto Legislativo 1/2013 — consolidates Spain's disability-rights legislation into a single text, establishing accessibility as a legal right and providing the general sanctioning framework the other two laws draw on
• Real Decreto 1112/2018 (7 Sept) — transposes EU Directive 2016/2102; requires public-sector websites and mobile apps to meet WCAG 2.1 AA, publish an accessibility statement, and provide a barrier-reporting channel
• Ley 11/2023 (8 May) — transposes the European Accessibility Act (Directive (EU) 2019/882); extends obligations to private-sector products and services essential to daily life: e-commerce, banking, transport, e-books, telecommunications, and certain computing products

Each law names its own scope and reference standard, which is why an organization operating both a government contract and a consumer-facing store often has to satisfy two separate legal tests instead of one.

How does the European Accessibility Act apply in Spain?

The EAA reaches Spain through Ley 11/2023, the national transposition of Directive (EU) 2019/882. The directive doesn't create obligations directly inside Spain — a Spanish regulator applies Ley 11/2023, not the EU text itself. The Act became mandatory across the EU, including Spain, from 28 June 2025.

That date works differently depending on when a product or service launched. Anything placed on the market after 28 June 2025 has to meet the requirements immediately. Products and services already in use before that date get a longer runway — they can continue operating without full compliance until 28 June 2030, provided the service isn't substantially changed in the meantime. A significant redesign of an existing e-commerce checkout would likely reset that clock and trigger immediate compliance.

Who must comply

Compliance splits along the type of organization and the sector it operates in. The practical first filter is whether an organization sells to consumers in one of the EAA's named sectors — that determines whether Ley 11/2023 applies at all, before company size enters the picture.

• Public sector bodies — central, regional, and local government entities, public universities, and other public-law bodies; bound by RD 1112/2018 for every website and app, no size or revenue threshold
• Private companies in EAA-covered sectors — banks, e-commerce platforms, transport operators, e-book publishers, certain telecom and computing-hardware providers; covered under Ley 11/2023 regardless of headquarters location
• Microenterprises — exempted from parts of the private-sector obligations under Ley 11/2023, following the EAA; exact size/turnover conditions should be checked against the current text
• Large companies outside EAA-defined sectors — not directly bound by either law, but still exposed through RD Legislativo 1/2013's general anti-discrimination provisions and through accessibility-conditioned procurement rules

What digital accessibility standards apply in Spain?

Both RD 1112/2018 and Ley 11/2023 point to the same technical standard: EN 301 549, the harmonized European standard for ICT accessibility, adopted in Spain as UNE-EN 301549. For web content and mobile apps, EN 301 549 incorporates WCAG at version 2.1, level AA — a site conforming to WCAG 2.1 AA is doing the bulk of the work either law actually requires.

WCAG covers web content specifically, while EN 301 549 is broader — it also sets requirements for non-web documents, software, and hardware such as ATMs and ticketing machines, which matters for the sectors Ley 11/2023 covers beyond pure websites.

How do WCAG standards support accessibility compliance in Spain?

WCAG functions as the testable layer underneath Spain's legal requirements — the laws state that accessibility is mandatory, and WCAG's success criteria are what an auditor actually checks a page against. Each AA-level criterion describes a specific, verifiable condition: sufficient color contrast, keyboard operability, text alternatives for non-text content, and so on.

A regulator can point to a failed criterion — a form field with no programmatic label, say — and tie it directly to an obligation under RD 1112/2018 or Ley 11/2023, rather than arguing over what "accessible" means in the abstract. That same specificity turns compliance into a checklist a team can actually work through, page by page, rather than a subjective judgment call.

What digital products and services must be accessible?

The scope splits along the same public/private line as the laws themselves, but each side covers a different range of products.

• Public sector (RD 1112/2018) — government websites, intranets, and extranets; native mobile apps published by public bodies; documents (PDFs, forms) that form part of an administrative process
• Private sector (Ley 11/2023) — e-commerce websites and apps handling the purchase process; online banking platforms, ATMs, and payment terminals; transport apps, websites, and ticketing/check-in machines; e-book files and e-readers; consumer computer hardware and operating systems; electronic communications services and their apps

A transport app, for example, needs to satisfy EN 301 549 requirements for both the software interface and, in some cases, the physical ticketing hardware it connects to.

Accessibility requirements for persons with disabilities

Spain's requirements are written around functional needs rather than named diagnoses — the laws don't list specific disabilities and prescribe a fix for each one. They trace back to WCAG's four principles: content has to be perceivable, operable, understandable, and robust enough to work with assistive technology.

In practice, this covers people who are blind or have low vision and rely on screen readers or magnification; people who are deaf or hard of hearing and need captions or transcripts; people with motor impairments who navigate by keyboard, switch, or voice control; and people with cognitive or learning disabilities who need predictable navigation and plain-language content. Meeting WCAG 2.1 AA across a site addresses all of these at once, because the criteria were built to cover overlapping functional barriers rather than one disability at a time.

What happens if organizations don't meet accessibility standards?

Non-compliance carries consequences that scale from administrative to financial, and which one applies depends on which law was violated.

• Corrective orders — regulators can require specific barriers fixed within a set deadline before any fine is discussed; usually the first step, not an immediate penalty
• Administrative fines — both RD Legislativo 1/2013's general sanctioning regime and Ley 11/2023's EAA-specific provisions allow financial penalties, scaled to severity and duration; exact figures should be checked against the current text
• Loss of public funding/contract eligibility — non-compliant organizations can be barred from public subsidies or procurement for a period
• Reputational and litigation exposure — a misrepresenting accessibility statement or unaddressed complaints can feed into consumer-protection or discrimination claims separately

For most organizations, the corrective-order stage is where a compliance gap actually gets resolved — financial and reputational consequences mainly apply once an earlier order was ignored.

How can organizations demonstrate compliance?

Demonstrating compliance comes down to documentation an organization can produce on request, not just a website that happens to work well with a screen reader. The starting point is a conformance audit against WCAG 2.1 AA via EN 301 549, identifying exactly which success criteria pass, fail, or partially pass. Public sector bodies under RD 1112/2018 must then publish an accessibility statement; private companies under Ley 11/2023 face a similar documentation expectation, though the format follows the EAA's conformity-assessment provisions rather than the public-sector statement template.

Ongoing monitoring matters because conformance is a claim about a specific version of a product at a specific point in time — a statement written before a redesign doesn't cover the redesign. Organizations that re-run their audit after significant changes, and treat the feedback channel as an active input rather than a formality, are in a materially stronger position if a regulator or complaint ever tests the claim.

What's next for digital accessibility regulation in Spain?

The clearest near-term change isn't a new law — it's existing deadlines catching up with organizations that used the transition periods already built into Ley 11/2023. The exemption for products already on the market before 28 June 2025 expires on 28 June 2030, and a separate 2027 date applies to emergency-communications accessibility requirements. As those dates approach, enforcement activity tends to increase.

WCAG itself has moved past version 2.1 — 2.2 is current — and EN 301 549 tends to follow WCAG revisions over time, which means the specific criteria referenced by Spanish law could shift even without a new statute. Because Ley 11/2023 implements an EU directive, any future EU-level revision of the EAA would flow back into Spanish law through an updated transposition, the way most changes here have arrived so far.