Skip to content
Webiland
Design5 min read

European Accessibility Act: What It Means for EU Websites and Apps

W
Webiland
Published · Updated

Building a digital interface for the European Union market now requires meeting statutory accessibility standards. Directive (EU) 2019/882, known as the European Accessibility Act, sets legal requirements for consumer websites and mobile applications. Teams that treat accessibility as an afterthought face compliance risks, fragmented remediation efforts, and inaccessible user flows.

Scope of Directive (EU) 2019/882

Directive (EU) 2019/882 applies to specific digital products and consumer services placed on the market in the EU. Under Article 2(2), the directive governs consumer-facing digital services. These services include:

  • E-commerce services: websites and mobile applications designed to conclude consumer sales contracts.
  • Consumer banking services: digital payment accounts, credit agreements, and payment transaction interfaces.
  • Electronic communications services: messaging, voice, and interactive communication software.
  • E-books and dedicated software: electronic reading applications and digital publishing platforms.
  • Passenger transport service elements: websites, mobile applications, interactive screens, and electronic ticketing services for air, bus, rail, and waterborne transit.

Products placed on the EU market are also covered under Article 2(1). These include general-purpose computers, smartphones, payment terminals, ATMs, ticketing machines, and e-readers. The directive excludes specific website content under Article 2(4). Pre-recorded media published before 28 June 2025, older office file formats, and third-party content outside the operator's control remain excluded.

Application Dates and the Microenterprise Exemption

The obligations under the European Accessibility Act are not indefinite proposals. Under Article 31(2), member states must apply these accessibility measures from 28 June 2025 (Directive (EU) 2019/882, 2019). Existing service contracts agreed before that date may continue without alteration for up to five years under Article 32(1).

The directive establishes a specific exemption for smaller service providers. Article 4(5) states: "Microenterprises providing services shall be exempt from complying with the accessibility requirements referred to in paragraph 3 of this Article and any obligations relating to the compliance with those requirements."

Article 3(23) defines a microenterprise precisely. A microenterprise employs fewer than 10 persons and has an annual turnover or balance sheet total not exceeding EUR 2 million. This exemption applies strictly to services, not to hardware products. Larger organizations, as well as businesses manufacturing or importing covered products, must comply fully. Member states enforce these provisions through designated market surveillance authorities and administrative bodies.

Does the Act apply, and what do you show?
  1. Covered: consumer services (Art. 2(2)) and products (Art. 2(1))
  2. A microenterprise providing services?
    Fewer than 10 persons, turnover or balance sheet total not exceeding EUR 2 million
    Yes
    Exempt — services only, not hardware products
  3. Content excluded under Art. 2(4)?
    Yes
    Excluded: pre-recorded media published before 28 June 2025, older office file formats, third-party content
  4. Applies from 28 June 2025
    Service contracts agreed before that date may continue unchanged for up to five years (Art. 32(1))
  5. Show conformity: EN 301 549 and WCAG
    Meeting harmonised standards published in the Official Journal is presumed to conform (Art. 15(1))

Showing Conformity: EN 301 549 and WCAG

The European Accessibility Act defines accessibility outcomes, not individual HTML rules. Under Article 15(1), a product or service that meets harmonised standards whose references are published in the Official Journal of the EU is presumed to conform. Check that list for your product type before you choose a standard.

In practice, teams work with two documents: the European Standard EN 301 549, which covers ICT products and services, and the Web Content Accessibility Guidelines (WCAG). W3C notes: "In addressing the European Accessibility Act (EAA), most organizations use WCAG and the European Standard EN 301 549: Accessibility requirements for ICT products and services" (W3C WAI, 2025).

WCAG is built on four principles: content must be perceivable, operable, understandable and robust. Meeting these criteria ensures that users navigating with assistive software or keyboard interfaces can complete transactions without obstruction.

Where Most Commercial Interfaces Fail

Automated scans show how far most sites are from conformance. In an evaluation of the top one million home pages, 95.9% had detectable WCAG 2 failures (WebAIM, 2026). WebAIM detected an average of 56.1 distinct accessibility errors per home page (WebAIM, 2026). Users with disabilities encounter barriers on approximately 1 in every 26 page elements (WebAIM, 2026).

The evaluation found that 83.9% of tested pages failed low-contrast text requirements (WebAIM, 2026). Additionally, 53.1% of pages had missing alternative text for images, and 51% missed form input labels (WebAIM, 2026). WebAIM reports that 96% of all detected errors fall into its six most common categories (WebAIM, 2026). Correcting interface issues during a structured UX audit prevents expensive emergency remediation.

Share of the top one million home pages
Detectable WCAG 2 failures95.9%
Low-contrast text83.9%
Missing alternative text for images53.1%
Missing form input labels51%

WebAIM, 2026

Practical Interface Audit Checklist

To prepare a website or app for EU compliance, engineering and design teams must verify six core functional areas. The following checklist outlines the essential technical checks:

  • Keyboard Access. Verification Criteria: All interactive elements must be reachable and operable using only the keyboard. Technical Implementation: Avoid mouse-only event handlers; test Tab, Enter, Space, and Escape keys across all modals.
  • Visible Focus. Verification Criteria: Interactive controls must display a distinct visual focus indicator. Technical Implementation: Do not remove CSS outline styles without providing an equivalent high-contrast indicator.
  • Color Contrast. Verification Criteria: Text and interface components must satisfy contrast ratios against background colors. Technical Implementation: Maintain at least 4.5:1 for standard text and 3:1 for large text and UI components.
  • Text Alternatives. Verification Criteria: Non-text content conveying information must have descriptive text equivalents. Technical Implementation: Provide concise alt attributes on informative images; mark decorative graphics with empty alt attributes.
  • Form Controls. Verification Criteria: Form inputs must have programmatically associated text labels and clear errors. Technical Implementation: Use explicit form label elements or matching ARIA attributes; provide descriptive inline error text.
  • Captions & Media. Verification Criteria: Prerecorded audio and video content must include synchronized text alternatives. Technical Implementation: Provide synchronized closed captions and transcripts for multimedia presentations.

Conducting this review early in the written discovery scope prevents architectural rewrites before release.

Integrating Accessibility into Production Workflows

Fixing accessibility after release means reworking screens that are already built. Teams succeed by embedding accessibility standards directly into design tokens, component architecture, and automated tests. A tokenized component library ensures that every button, input, and modal conforms to WCAG standards by default.

Updating components within a shared design system resolves contrast and focus defects across entire application suites simultaneously. Automated linting in continuous integration pipelines catches missing labels and broken hierarchy before code merges. However, automated tools catch only a fraction of usability barriers.

Manual testing with screen readers and keyboard-only navigation remains essential for complex checkout and authentication flows. In our UI/UX design work, accessibility checks run in design review before developer handoff, and the handoff carries accessibility notes.

Audit your current user flows against the harmonised standards, document exceptions in your technical files, and standardize compliant components across your repository.

Need help with a project like this?

Talk to our team about your specific situation. No sales pitch — just a conversation.

Talk to our team →

Service: UI/UX Design →