What does the European Accessibility Act mean in a world increasingly defined by websites, mobile applications, payment terminals, ticketing machines and automated customer journeys?

Contents

1. “Accessibility is a precondition for independent living and full participation”
2. Why the EAA matters more than ever
3. The road to the European Accessibility Act
4. So, what is the European Accessibility Act?
5. Who benefits under the EAA?
6. What the EAA actually does: the products, services and organisations in scope
7. What accessibility means under the EAA
8. The legal framework behind the experience
9. Transitional rules and existing technology
10. Why accessibility has become a boardroom issue
11. Why digital accessibility and self-service technology have become the new accessibility frontier
12. Why self-service technology has become the accessibility battleground
13. Sector by sector: where the EAA reaches the customer
14. Microenterprises, exemptions and small-business reality
15. National implementation: one Directive, different enforcement landscapes
16. EAA, ADA, WAD, UNCRPD and UK law: how the frameworks connect
17. How the EAA changes what procurement teams must ask
18. Building an EAA compliance programme
19. The cost of retrofitting accessibility and common EAA mistakes
20. Storm Interface’s perspective: design for the complete person and the complete journey
21. Beyond compliance: the future of accessibility in Europe

Legal information notice This article provides general information and practical guidance. It is not legal advice. National implementing laws, enforcement practice and standards continue to develop. Organisations should confirm the position for their products, services, markets and contractual arrangements with qualified legal and technical advisers.

So, what is the European Accessibility Act?

The European Accessibility Act is the common name for Directive (EU) 2019/882 on the accessibility requirements for products and services.

It establishes a shared European framework for a defined range of products and consumer services.

The EAA is a directive that Member States implement through national law. The common core comes from EU legislation; regulators, complaint routes, procedures and penalties operate nationally.

That creates two levels of compliance:

1. The Directive supplies the common requirements. It defines scope, economic-operator roles, accessibility outcomes, conformity concepts and enforcement principles.
2. National law makes them operational. Each Member State identifies authorities, sanctions and procedures, and may exercise options permitted by the Directive. [EUR-Lex: National transposition measures for Directive (EU) 2019/882]

For products, the EAA uses the familiar EU conformity system. Manufacturers assess conformity, prepare technical documentation and an EU declaration of conformity, then affix the CE marking. Importers and distributors have their own checking, traceability and cooperation duties.

Service providers follow a different route. They must design and provide covered services in accordance with the relevant accessibility requirements, publish accessible information explaining how the service meets them and maintain procedures as the service changes. [European Commission: Accessibility of products and services]

This is one of the EAA’s most important practical effects as accessibility becomes part of the product and service lifecycle.

A product team needs evidence before market placement. A service team needs governance after launch. Procurement, software releases, supplier changes, customer support and corrective action all become part of the same accessibility system.

What has recently changed?

The European Accessibility Act is often described as a piece of EU accessibility legislation. That description is accurate, but it misses the scale of what has changed. Since 28 June 2025, accessibility has become a condition of market access for a defined range of everyday products and consumer services across the European Union.

The legislation reaches computers and operating systems, smartphones, e-readers, payment terminals, ATMs, ticketing and check-in machines, electronic communications, passenger transport information and ticketing, consumer banking, e-books and e-commerce. It gives manufacturers, importers, distributors and service providers clear responsibilities. [European Accessibility Act, Articles 1-4]

For organisations in retail, hospitality, banking, transport, technology, telecommunications and public services, the EAA is now a product, procurement and customer-experience reality.

Yet it is still widely misunderstood.

Some organisations see it as a website law, whilst others have treated 28 June 2025 as the end of a compliance project. Product teams may assume that CE marking settles the question; Digital teams may assume that a WCAG audit covers the whole service; Procurement teams may accept a supplier’s claim that a product is “accessible” without asking what a customer with disabilities can actually do with it.

Accessibility is still commonly pictured as a ramp, a lift, a wider doorway or an accessible parking space. Those things remain essential, yet modern-day exclusion also happens inside an app, at a payment screen, during identity verification or on the first screen of a self-service journey.

The questions organisations now face are whether:

• A visually impaired customer can order a meal privately and independently;
• a wheelchair user can approach, reach and operate a terminal;
• a traveller with hearing disabilities receives the same urgent information as every other passenger;
• a person with limited dexterity can complete a payment without precise gestures or simultaneous movements;
• a customer with a cognitive disability can understand the instructions, recover from an error and finish the transaction;
• a person who cannot use biometric identification has another route;
• the accessible experience still works after a software update, a replacement component and the next procurement cycle.

These are human questions. They are also design, engineering, commercial and legal questions.

The EAA deals with them through functional requirements: Information may need to be available through more than one sensory channel; Interfaces must accommodate different ways of seeing, hearing, speaking, touching and operating; Products and services must work with assistive technologies. Instructions, support, security and payment form part of the experience. [European Accessibility Act, Annex I]

Storm Interface is a British business serving international markets, and whilst the EAA was not transposed into Great Britain’s domestic law after Brexit. British manufacturers, retailers, banks, transport businesses, technology suppliers and e-commerce providers can still enter its scope when they place covered products on the EU market or offer covered services to EU consumers. [European Commission: European Accessibility Act]

Whilst the EAA is not a general accessibility law for every product, website or service, it has a defined scope and the principle running through it is clear: people should be able to use products and services with independence, privacy, freedom of choice and dignity.

This guide explores how Europe reached this point, what the law requires and why self-service technology has become one of the clearest tests of whether accessibility works in practice.

For us at Storm Interface, there is only one question that really needs answering when it comes to self-service:  Can people complete the task they came to perform, independently and with the same confidence as everyone else?

“Accessibility is a precondition for independent living and full participation”

The European Accessibility Act did not begin with technical standards, product files or CE markings; it grew from a much older argument about who gets to participate in society.

The final law matters, but it is not the comprehensive settlement its title can suggest. The European Disability Forum welcomed it as a landmark and criticised gaps in transport and the built environment. They considered it a major step but not the completion of Europe’s accessibility work. [European Disability Forum: analysis of the European Accessibility Act]

The Council of Europe’s history of disability models states that, before the 1970s, the dominant medical model placed the problem firmly within the individual. A person who could not enter a building, use a service or understand a piece of information was expected to adapt, seek help or go without. It regarded medical treatment as the solution. The UN’s explanation of the CRPD’s “paradigm shift” describes the movement away from treating people with disabilities as objects of medical treatment, charity and social protection towards recognising them as rights-holders, and the OHCHR guide to monitoring the CRPD explains the transition from charity and medical models to a social and human-rights model in which disability results from interaction with an environment that fails to accommodate the individual.

The disability-rights movement challenged that assumption.

A wheelchair user is excluded when there is no accessible route; a visually impaired person is excluded when information is only visual; a person with hearing disabilities is excluded when an alert is only audible; a customer with limited dexterity is excluded when an interface demands precise gestures.

The barrier sits in the design of the environment, product or service, and that shift in thinking shaped the United Nations Convention on the Rights of Persons with Disabilities, adopted in 2006. Article 9 connects accessibility with the physical environment, transport, information, communications and electronic services. [UN Convention on the Rights of Persons with Disabilities, Article 9]

The UN Committee later described accessibility as a precondition for people with disabilities to live independently and participate fully and equally in society. [UN Committee on the Rights of Persons with Disabilities: General Comment No. 2]

That principle is the human foundation beneath the EAA which forms part of Europe’s practical response to those commitments, translating a right to participation into requirements that can be specified, tested, documented and enforced. [European Commission: The EU and the UN Convention]

Accessibility needs also change across a lifetime. Vision, hearing, strength, dexterity, memory and processing can alter gradually; an injury may change them overnight; bright sunlight, background noise, luggage, stress or a child held in one arm can expose the same weaknesses in a design.

Behind every percentage are people trying to travel, pay, bank, communicate, buy food, read a book or contact emergency services and moving a service online clearly does not remove a barrier when the barrier moves with it.

Why the EAA matters more than ever

Technology has now become part of Europe’s everyday infrastructure: Customers open bank accounts through apps. They buy rail tickets online, check in at terminals, pay through unattended devices and use e-commerce sites for essential goods. A self-service system may be the quickest route through a service, and in some places it is the only obvious route. This change in the way we shop, eat, and travel has fundamentally changed the practical meaning of access.

A building can have a level entrance and still contain an unusable ticket machine; a bank can have an accessible branch while its authentication process blocks a screen-reader user; a transport operator can provide passenger assistance while its real-time disruption notices remain inaccessible; a restaurant can welcome customers with disabilities through the door and exclude them at the ordering kiosk.

Eurostat’s data records lower internet use among people with disabilities than non-disabled people, together with gaps in online banking and online searches for goods and services. [Eurostat: Disability and access to information and communication technologies]

Those gaps are not explained by one technology or one impairment. They emerge from thousands of design decisions:

• labels that a screen reader cannot identify;
• controls that disappear when text is enlarged;
• authentication that assumes everyone can see, remember or copy a   code;
• time limits that cannot be extended;
• touchscreens with no tactile reference point;
• payment devices placed outside an accessible reach range;
• audio that broadcasts private information;
• error messages that tell the user something went wrong without explaining how to recover.

The EAA brings many of those decisions into a legal framework. It also changes the evidence organisations need.

Eurostat estimates that 23.9% of people aged 16 and over in the EU had a
disability in 2024. [Eurostat: Population with disability] puts into context that this is about 90 million people.  Germany, the EU’s most populous member state in 2024, had 83.4 million people. A hypothetical country formed by the EU’s adult with disability population would therefore be the largest member state, around 6.6 million people larger than Germany. Council of the EU: Disability facts and figures; Eurostat: Demography of Europe.

Globally, the numbers are even more staggering – A population of 1.3 billion would also rank third globally, behind India at approximately 1.451 billion and China at 1.419 billion. United Nations: World Population Prospects 2024. World Health Organisation: Disability and health. The World Health Organisation estimates that 1.3 billion people globally, around one in six, experience significant disability. [World Health Organisation: Disability and health].

The numbers show the scale of the opportunity and highlight how and why accessibility can no longer live only in a policy statement or a supplier brochure. Manufacturers must be able to show how covered products meet the requirements and service providers must explain how their services comply and maintain procedures as those services change.

The application date has passed. Regulators can investigate. Customers can complain. Products can be restricted or withdrawn. Services can face enforcement under national law.

For a British or global business, the EAA also demonstrates how quickly accessibility obligations travel with the market. Headquarters location does not decide the whole question; what matters most is the product, the service, the legal role and the EU customer relationship.

The human objective remains straightforward: independence, privacy, freedom of choice and equal participation.

The road to the European Accessibility Act.

The EAA did not appear suddenly in 2019. It emerged from disability-rights advocacy, international commitments, sector regulation, public procurement and a growing recognition that Europe’s accessibility rules were fragmented.

Its story is less cinematic than the Americans with Disabilities Act in that there was no single South Lawn ceremony or one speech that explains the whole Act. The European version is a story of years of campaigning, consultations, committee votes and arguments over which parts of everyday life the law would reach.

In December 2017, nearly 800 delegates gathered in the European Parliament’s chamber for the fourth European Parliament of Persons with Disabilities. People with disabilities came from across Europe and across disability groups. Together, they adopted an emergency resolution calling on the Council to agree an ambitious and forward-looking Accessibility Act. [European Disability Forum: Emergency Resolution on the European Accessibility Act] [European Disability Forum: Annual Report 2016-2017]

The urgency was real: The Commission had proposed the law two years earlier, and the European Parliament had adopted its negotiating position, but agreement among the institutions was still missing.

Campaigners kept pressing because the scope would decide what the law meant in daily life. Would it reach transport? The built environment? Payment terminals? Emergency communications? Would a European law about accessibility remove barriers or simply organise a narrow part of the market?

When the institutions reached political agreement in November 2018, the response from the disability movement was mixed. The European Disability Forum recognised gains for computers, smartphones, telephony, e-books, e-commerce, ATMs and payment terminals. It also said the agreement had fallen short on the built environment, transport and other areas. [European Disability Forum: Resolution on the European Accessibility Act, November 2018]

That tension is important to highlight because whilst the EAA is a substantial law, it is also a law with boundaries, compromises and work left for national governments and future European legislation.

Before one Act came many separate rules

In reality, Europe already had accessibility law before the EAA. EU public procurement rules required technical specifications to account for accessibility where goods and services were intended for use by people. Passenger-rights legislation addressed assistance and access in air, rail, bus, coach and water transport. Electronic communications and audiovisual media laws contained their own accessibility obligations.

The Web Accessibility Directive, adopted in 2016, created common requirements for public-sector websites and mobile applications. [Web Accessibility Directive] [Public Procurement Directive, Article 42]

The result was progress, but the picture remained uneven.

Different countries could impose different requirements on similar products and services: A manufacturer selling the same terminal across several Member States could face separate national expectations. Consumers encountered different levels of access depending on where they lived, travelled or bought a service.

The problem affected people and the single market at the same time.

The European Commission used Article 114 of the Treaty on the Functioning of the European Union, the legal basis for internal-market harmonisation, to propose a common framework. [Treaty on the Functioning of the European Union, Article 114]

This legal origin explains the EAA’s character as a market-access directive built around accessibility outcomes. The mechanism is economic but the purpose reaches much further.

A decade from proposal to application

The Commission presented its original proposal on 2 December 2015, supported by an impact assessment examining the effect of divergent national rules. [European Commission proposal COM(2015) 615] [European Commission impact assessment SWD(2015) 264]

Negotiation followed and the European Parliament approved the text on 13 March 2019 with the Council formally adopting it on 9 April 2019.

The Directive was signed on 17 April and published in the Official Journal on 7 June 2019. [European Parliament legislative resolution, 13 March 2019] [Council of the EU: adoption of the Accessibility Act, 9 April 2019]

Member States had until 28 June 2022 to adopt and publish their national measures whilst the main requirements began to apply on 28 June 2025, subject to transitional rules. [European Accessibility Act, Articles 31-32]

By the time the application date arrived, the Directive had been public for six years and proposed for almost a decade.

Who benefits under the EAA?

The EAA is designed around the needs of people with disabilities, including people with long-term physical, mental, intellectual or sensory impairments whose interaction with barriers can hinder full and effective participation in society.

That includes people who are blind or have low vision, People with hearing disabilities and people with hearing loss, people with limited mobility, reach, strength or dexterity, people with speech impairments and people with cognitive, learning or neurological disabilities.

Disability is diverse. It may be visible, invisible, permanent, episodic or progressive and the law’s functional approach reflects that reality. It asks how information is perceived, how controls are reached and operated, how people communicate, how they recover from errors and whether privacy survives the use of accessibility features.

Accessible design often helps a wider group as well. Captions help in noisy places. Clear instructions help customers under pressure. Larger targets help anyone using a touchscreen while moving. An alternative to a complex gesture can help someone with an injury or a device mounted at an awkward angle.

The wider benefit does not dilute the disability-rights purpose.  People with disabilities are the reason the requirements exist, and their experience is the test that matters.

What the EAA actually does: the products, services and organisations in scope

The EAA is broad enough to change major markets and precise enough to require careful classification.

Coverage depends on five questions:

• What is the product or service?
• Is it one of the categories listed in Article 2?
• What legal role does the organisation perform?
• Is the product being placed on the EU market or the service offered to EU consumers?
• Which date and transitional rule apply?

The presence of a screen does not automatically bring a product into scope. A website is not automatically an e-commerce service. One part of a customer journey may be covered while another sits under a different law, and that is why EAA compliance begins with a defensible scope decision, not a generic accessibility audit.

Products placed on the EU market

From a self-service perspective, the covered product categories include:

• consumer general-purpose computer hardware systems and their operating systems;
• payment terminals;
• ATMs;
• ticketing machines;
• check-in machines;
• interactive information self-service terminals, subject to the exclusion for terminals installed as integrated parts of certain transport vehicles;
• consumer terminal equipment with interactive computing capability used for electronic communications;
• consumer terminal equipment used to access audiovisual media services;
• e-readers.

These categories use legal definitions. Classification should be recorded at product level, including the intended use, market, model, software and date first placed on the market. [European Accessibility Act, Article 2]

Consumer services provided after 28 June 2025

The covered services include:

• electronic communications services, with a limited exception for transmission services used for machine-to-machine services;
• services providing access to audiovisual media services;
• specified digital, ticketing, information and terminal elements of air, bus, rail and water passenger transport;
• consumer banking services;
• e-books and dedicated software;
• e-commerce services;
• answering emergency communications to the European emergency number 112.

The service analysis must follow the complete consumer journey. Search, information, identity, security, payment, confirmation, cancellation and support can all affect whether the service is accessible.

Manufacturers, importers, distributors and service providers

The EAA allocates responsibility across the supply chain. Manufacturers design and manufacture covered products, complete the conformity assessment, prepare technical documentation, issue the declaration of conformity and affix the CE marking. They must supply accessible instructions, identify the product and take corrective action when required.

Importers check that the manufacturer has completed the required work before placing a third-country product on the EU market. Distributors must act with due care, check the CE marking and required documentation, protect conformity during storage and transport and cooperate with authorities.

An importer or distributor can become the manufacturer in law when it markets the product under its own name or trade mark, or changes it in a way that may affect conformity. Economic operators must retain supply-chain traceability for five years. [European Accessibility Act, Articles 7-12]

Service providers must explain, in accessible terms and conditions or an equivalent document, how a covered service meets the requirements. They need procedures that preserve conformity as the service changes and a route for addressing non-conformity. [European Accessibility Act, Article 13 and Annex V]

This division of responsibility matters in real projects. A kiosk may involve a manufacturer, importer, hardware distributor, software company, payment provider, systems integrator and the organisation delivering the customer service. Contracts can allocate tasks. They cannot make statutory duties disappear.

Organisations outside the EU

The EAA also follows the EU market which means a British, American, Canadian or Asian manufacturer can enter the product compliance chain when it places a covered product on that market. A non-EU service provider may be covered when it offers a covered service to EU consumers.

Online services require a careful territorial analysis. Language, currency, delivery territory, marketing, terms and the actual consumer relationship may all matter. The decision should be recorded rather than assumed.

Brexit therefore did not make the EAA irrelevant to British businesses. It changed the route through which the law applies.

Important boundaries and exclusions

Some transport terminals installed as integrated parts of aircraft, buses, coaches, rolling stock and waterborne vessels are excluded from the product list. Services supplied outside the EU are not brought into the Act simply because the provider has an EU customer elsewhere in its business.

The digital rules also exclude certain content. The list includes pre-recorded time-based media published before 28 June 2025, office-file formats published before that date, online maps where essential navigation information is supplied accessibly, third-party content that the service provider neither funds nor develops nor controls, and archived content that is no longer updated after 28 June 2025. [European Accessibility Act, Article 2(4)]

These are content exclusions, not permission to leave the surrounding service inaccessible. An old PDF may sit outside the rule while the account, payment and support journey around it remains covered.

The built environment sits differently again. The Directive allows Member States to require the built environment used by customers of covered services to meet Annex III, but does not impose one compulsory EU-wide building rule. National building, equality and planning laws may apply regardless. [European Accessibility Act, Article 4(4) and Annex III] [CEN-CENELEC: Accessibility of the built environment]

This is why scope work has to be specific. A convenient label such as “legacy content”, “transport equipment” or “outside the EU” is not an analysis.

What accessibility means under the EAA

The EAA does not prescribe one interface or one approved design. It describes the outcomes that products and services must achieve.

That is sensible. An e-reader, a banking app and a ticket machine do different jobs. Their accessible design will look different too.

The requirements begin with information.

Instructions and product information must be understandable and perceivable. Information about use should be available through more than one sensory channel. Text, symbols, contrast, spacing and non-text alternatives all matter. Instructions should explain the product’s accessibility features, how it works with assistive devices and which assistive technologies have been tested with it. [European Accessibility Act, Annex I, Section I]

Packaging and information provided on the product can also fall within the requirements. A usable interface accompanied by an inaccessible setup process can stop a person before they reach the service.

The interface itself must support accessible interaction, communication, control, orientation and manipulation. Depending on the product, this can require:

• an alternative when operation requires vision;
• adjustable magnification, brightness and contrast;
• alternatives to colour as the only way of conveying information;
• alternatives when operation requires hearing, speech, vocal input or fine motor control;
• compatibility with assistive technologies;
• sufficient time and a way to extend time limits;
• controls that can be distinguished by touch;
• operation without excessive reach, strength or simultaneous movement;
• alternatives to biometric identification and control;
• privacy when accessibility features are used;
• protection from flashes that could trigger seizures.

The last few points disappear surprisingly quickly when accessibility is treated as a website exercise. A person may need to find the machine, reach it, identify the controls, hear private audio, navigate the software, authenticate, pay, correct a mistake and collect a receipt. Every part can work in isolation, and the journey can still fail.

Support is also part of the service. Helpdesks, call centres, technical support, relay services and training services must provide information about accessibility and compatibility in accessible modes of communication where those services are available. [European Accessibility Act, Annex I, Section I]

This creates a practical duty for people as well as technology.

Staff need accurate information. Support routes must work for people using screen readers, relay services or alternative communication. A customer should not have to disclose more personal information or wait longer because an accessible function has failed.

The same principle applies after deployment. Headphone sockets need inspection. Tactile controls must remain unobstructed. Software updates should not break the accessible route. Accessibility that disappears during normal operation was never robust enough.

Functional performance criteria

Annex VII covers situations where Annex I does not specify a particular technical solution. It organises access around what people need to do:

1. use a product without vision or with limited vision;
2. use it without perception of colour;
3. use it without hearing or with limited hearing;
4. use it without vocal capability;
5. use it with limited manipulation, strength or reach;
6. use it with limited cognition;
7. avoid photosensitive seizure risks;
8. preserve privacy when accessibility features are used. [European Accessibility Act, Annex VII]

These criteria keep technical work connected to human use when a detailed standard leaves a gap.

The legal framework behind the experience

The EAA’s legal structure is less memorable than its purpose, but organisations need to understand it. The articles follow the life of a product or service from scope to evidence, enforcement and transition.

Articles 1 to 6 establish the objective, scope, definitions and central accessibility obligation. Products must meet the relevant requirements in Annex I. Services must meet the service requirements, and self-service terminals used to provide them must satisfy the applicable product requirements. [European Accessibility Act, Articles 1-6]

Articles 7 to 12 divide responsibility through the product supply chain. The manufacturer creates the evidence. The importer checks that the required work has been done. The distributor must recognise apparent non-conformity and cooperate with authorities.

Article 13 governs services. Websites are released, apps updated, authentication tools replaced and support scripts changed. Compliance therefore needs procedures that survive the life of the service rather than a report produced once and filed away.

Annex V requires publicly available information describing the covered service, explaining how it works and how it meets the accessibility requirements. That information must be accessible and remain available while the service operates. [European Accessibility Act, Annex V]

Fundamental alteration and disproportionate burden

Article 14 contains two limited exceptions. A requirement does not apply to the extent that compliance would fundamentally alter the basic nature of the product or service, or impose a disproportionate burden on the economic operator.

Those words do not create a general escape route for projects that began too late.

The operator must assess the position. Annex VI points to factors including net compliance costs, overall costs, financial and organisational resources, turnover, the estimated benefit for people with disabilities and the frequency and duration of use. [European Accessibility Act, Article 14 and Annex VI]

The assessment is requirement-specific. If one measure is genuinely disproportionate, other achievable measures remain. The evidence should identify the requirement, available options, cost, resources and likely effect.

Documentation must generally be kept for five years. Service providers reassess when the service changes, when an authority asks and at least every five years. An operator cannot rely on disproportionate burden for a measure funded specifically to improve accessibility.

An inconvenient architecture, an expensive late change or a preferred interface pattern will not answer the legal question by themselves. Regulators can ask what alternatives were considered and why they were rejected.

Standards and presumption of conformity

Standards help organisations turn functional legal requirements into testable engineering work. They need to be used carefully.

Under Article 15, products and services conforming to harmonised standards whose references have been published in the Official Journal are presumed to conform to the EAA requirements covered by those standards. Common technical specifications can play a similar role in defined circumstances. [European Accessibility Act, Article 15]

The words “covered” and “published” do a great deal of work.

A useful technical standard does not automatically create a legal presumption. The reference must be formally published for the EAA, and the presumption reaches only the requirements the standard covers.

This is why a supplier’s broad statement that a product “meets EN 301 549” should lead to more questions. Which version? Which clauses? Which components? What was tested? What sits outside the standard? Which EAA requirements does the evidence address?

CE marking and product evidence

Covered products use the internal production-control procedure in Annex IV. The manufacturer prepares technical documentation showing how conformity was assessed. That file should include a description of the product, the standards or technical specifications used and the solutions adopted where those standards were not applied. Production controls must preserve conformity across manufacturing. [European Accessibility Act, Article 16 and Annex IV]

The manufacturer then draws up the EU declaration of conformity and affixes the CE marking visibly, legibly and indelibly to the product or, where necessary, its packaging and accompanying documents.

The CE mark records the manufacturer’s legal declaration. It is not a third-party accessibility award, and it does not prove that every customer journey built around the product works.

A purchaser still needs to examine the evidence relevant to its installation, software, peripherals and service. Regulators can do the same.

Articles 19 to 22 connect the EAA with the EU market-surveillance framework. Authorities can assess conformity, request documents, require corrective action, restrict or prohibit a product and order withdrawal or recall. Missing documentation or incorrect marking can trigger action even before a functional defect is established. [Regulation (EU) 2019/1020 on market surveillance]

Services, complaints and penalties

Member States must establish procedures for checking service compliance, following complaints and verifying corrective action. Consumers may take action under national law. Public bodies and private organisations with a legitimate interest may support complainants. [European Accessibility Act, Articles 23 and 29]

Penalties are set nationally. The Directive requires them to be effective, proportionate and dissuasive. The extent of non-compliance, the number of affected units and the number of people affected can all matter. [European Accessibility Act, Article 30]

The enforcement route therefore depends on the market and the service. A pan-European organisation may face the same core requirements through several regulators with different procedures and sanctions.

Transitional rules and existing technology

The main application date was 28 June 2025. The Directive contains transitional provisions because replacing every existing product, service contract and terminal overnight would have been unrealistic.

Service providers may continue using products they lawfully used to provide similar services before that date until 28 June 2030. Service contracts agreed before the application date may continue unchanged until expiry, subject to a maximum of five years.

Member States may allow self-service terminals lawfully used before 28 June 2025 to remain in service until the end of their economically useful life, capped by the Directive at twenty years after first use. The accessibility of answering emergency communications to 112 may be deferred until 28 June 2027. [European Accessibility Act, Articles 31-32]

The twenty-year figure is often repeated as though every existing terminal is exempt until 2045. It is not that simple.

National implementation can be shorter. Germany and France have used shorter periods for certain terminals. Software and service elements may change long before the hardware reaches the end of its life. A replacement estate being procured today cannot rely on rules written for defined legacy arrangements.

Every transition decision needs evidence: the terminal, first-use date, service, contract, country and legal route.

The law itself is not static. The European Commission must report on its application by 28 June 2030 and every five years after that, including the effect on economic operators and people with disabilities. [European Accessibility Act, Article 33]

Why accessibility has become a boardroom issue

Accessibility used to be left to facilities teams, legal advisers or a small group of specialists. That division no longer matches how organisations build and deliver services.

Accessibility now influences:

1. market access;
2. customer completion and abandonment;
3. product design and engineering;
4. procurement eligibility;
5. customer-support demand;
6. brand trust;
7. cost of remediation and fleet replacement;
8. legal and regulatory exposure.

The commercial case should be handled with care. People with disabilities are people with rights. Their inclusion does not depend on proving a sufficiently attractive market opportunity.

Organisations still make investment decisions, and inaccessible services produce measurable consequences.

A customer who cannot complete checkout does not convert. A passenger who cannot use the ticket machine joins a staffed queue, if one exists. A bank customer blocked by authentication contacts support or leaves. A terminal rolled out across a thousand locations turns one design mistake into a fleet problem.

Real service data is more useful than broad claims. Teams should examine completion, abandonment, error, assistance and fault rates by route, with privacy protected. Participants with disabilities belong in discovery, prototype testing, pilots and post-deployment review.

Accessibility is also becoming part of commercial due diligence. Buyers ask for evidence. Public procurement law may require accessibility criteria. Large organisations push requirements down through supply chains. A manufacturer without a clear evidence file can lose a sale before a regulator becomes involved.

Why digital accessibility and self-service technology have become the new accessibility frontier

When the European Commission proposed the EAA in 2015, smartphones and online services were already reshaping daily life. The pace has accelerated since.

Websites, apps, digital identity, payment systems and kiosks now sit between customers and essential services.

The barrier may be a missing label in code. It may be a flat touchscreen with no tactile route. Often it is the connection between software, hardware and the physical environment.

A technically accessible website can hand the customer to an inaccessible payment provider. An accessible kiosk application can be installed at a height a wheelchair user cannot reach. A terminal can offer text-to-speech and place the headphone socket where a visually impaired person cannot find it. Each component can carry an accessibility claim while the person standing in front of the service remains unable to use it.

This is why the EAA reaches beyond content. It covers information, interfaces, assistive-technology compatibility, support, documentation, security, payment and ongoing governance.

Websites, apps and the complete digital journey

For websites, online applications and mobile services, the EAA uses four familiar principles: information must be perceivable, interfaces operable, content understandable and technology robust. These are commonly shortened to POUR. [European Accessibility Act, Annex I, Section III]

In practice, digital teams need to address:

• semantic headings, labels and relationships;
• meaningful text alternatives;
• captions and alternatives for media;
• sufficient colour contrast without relying on colour alone;
• keyboard access and visible focus;
• logical reading and focus order;
• clear error identification and recovery;
• content that resizes and reflows;
• compatibility with screen readers and other assistive technologies;
• accessible authentication, identity, security and payment;
• testing at component, page, journey and release level.

The last point is easily missed. Passing a collection of pages does not prove that a customer can complete the service.

WCAG 2.2 is essential and still only part of the answer

The Web Content Accessibility Guidelines are the leading international standard for web-content accessibility. WCAG 2.2 contains testable success criteria at Levels A, AA and AAA across the POUR principles. [W3C: Web Content Accessibility Guidelines 2.2]

WCAG 2.2 Level AA is a sensible current target for websites and web applications. Its newer criteria address areas such as focus visibility, dragging movements, target size, consistent help, redundant entry and accessible authentication. [W3C: What’s New in WCAG 2.2]

WCAG addresses web content. An EAA service may also include non-web software, hardware, product instructions, packaging, documentation, support and an unattended payment terminal.

Automated tools see only part of that picture. They can identify selected code-level failures quickly. Human review is needed for meaning, reading order, keyboard behaviour, error recovery and the coherence of the complete journey. Testing with users with disabilities reveals barriers that technical checks miss. [W3C: Evaluating Web Accessibility Overview]

EN 301 549 reaches beyond the website

EN 301 549 is the European standard for accessibility requirements for ICT products and services. Version 3.2.1 covers generic requirements, two-way voice communication, video, hardware, web content, non-web documents, non-web software, documentation and support. Its web chapter incorporates WCAG 2.1 requirements. [ETSI: EN 301 549 V3.2.1]

The standard contains requirements that WCAG does not. Its hardware provisions address tactilely discernible controls, operable parts, reach and force. Closed-functionality provisions address systems that prevent users from attaching or installing their own assistive technology.

As of August 2026, the latest published version remains EN 301 549 V3.2.1. Work on revised standards supporting the EAA continues under the Commission’s standardisation request M/587. [European Commission: standardisation request M/587] [CEN-CENELEC Work Programme 2026: Inclusivity and Accessibility]

In June 2026, CEN, CENELEC and ETSI published revised guidance bringing earlier procurement and conformity-assessment material together in CEN-CLC-ETSI/TR 101551:2026. It helps organisations use accessibility standards, but guidance is not the same thing as an EAA harmonised standard cited in the Official Journal. [AccessibleEU: revised EAA and WAD guidance, June 2026]

For organisations working today, EN 301 549 V3.2.1 is a broad and credible technical benchmark. WCAG 2.2 Level AA is a strong target for modern web content. Neither statement should be converted into an automatic claim of EAA legal conformity.

The evidence needs to connect each relevant EAA requirement to the chosen standard, clause, design response, test method and result.

Why self-service technology has become the accessibility battleground

Few technologies expose the full accessibility challenge as clearly as self-service.

A website can often work with assistive technology already owned and configured by the customer. A kiosk is a closed system in a public place. The operator controls the screen, software, physical controls, audio, height, approach space, lighting, payment device, timeout and support route.

That control creates responsibility.

The EAA’s product scope expressly includes payment terminals, ATMs, ticketing machines, check-in machines and interactive information self-service terminals, subject to the exclusion for terminals installed as integrated parts of certain transport vehicles. Interactive terminals also appear in the service requirements for passenger transport. [European Accessibility Act, Article 2]

A kiosk therefore needs two views at the same time: the hardware placed on the market and the service journey it enables.

The problem with touchscreen-only accessibility

Touchscreens are flexible. They can present a great deal of information, change by context and support rapid updates. They also remove the fixed reference points available on a physical control panel.

A visually impaired user may have no reliable way to find the first control or know what changed after activation. A person with tremor may struggle with small targets or gestures. A low-vision customer may encounter glare, fixed text, weak contrast or content outside a comfortable viewing angle. A wheelchair user may be unable to reach the screen or payment device. A short timeout can end the transaction for someone who needs longer to process the choices.

The question is not whether the touchscreen looks intuitive.

Intuitive for whom?

Accessibility has to be judged by task completion. Can the customer find the route, operate it, recover from mistakes, protect private information and finish without another person taking over?

What the EAA requires from self-service terminals

Annex I adds requirements tailored to self-service. Relevant terminals must:

• provide text-to-speech technology;
• allow the use of personal headsets;
• provide alerts through more than one sensory channel;
• allow users to extend the time available;
• provide adequate contrast and tactilely discernible keys and controls where they are present;
• make accessibility features discoverable and activatable;
• support relevant assistive technologies, including hearing-related technology where applicable. [European Accessibility Act, Annex I, Section I]

Payment terminals must support privacy and accessible operation. ATMs and other machines handling sensitive information need an audio route that does not broadcast a PIN, balance, medical detail or travel plan.

Headphone detection, volume control and spoken prompts can look like small engineering decisions. For the person using the machine, they decide whether the service is available at all.

Accessible self-service is a system

No single component can make the complete experience accessible, and a robust kiosk programme needs at least six connected layers.

1. Physical access

The route, clear floor space, knee and toe clearance, reach ranges, screen angle and location of the payment device, receipt, scanner, controls and audio connection all matter. Applicable national building law, EN 17210, ISO 21542 and standards such as BS 8300 can inform physical design, depending on market and context. [ISO 21542:2021] [CEN-CENELEC: Accessibility of the built environment]

2. Discoverability

A customer needs to find the accessible mode without already seeing the screen. A tactile control, consistent location, headphone socket that triggers audio or a clear audible cue can provide the entry point. An accessibility icon shown only on the touchscreen is invisible to the person most likely to need another route.

3. Input

The system should offer more than one reliable way to operate it. Tactile navigation controls can provide directional movement, selection, cancellation and help. Alternatives may be needed for gestures, simultaneous actions, speech and biometrics.

4. Output

Visual information needs contrast, readable type and a layout that survives zoom or larger text. Audio needs privacy, clarity, adjustable volume and complete information. Status, error and confirmation messages should reach more than one sense. Captions, visual alerts and hearing-system compatibility support customers who are Deaf or hard of hearing.

5. Software and transaction flow

Focus order, labels, timeouts, language, payment steps and error recovery determine whether the hardware works in practice. Audio and visual states need to remain synchronised. The user should be able to go back, repeat information, cancel safely and recognise when the transaction is complete.

6. Operations

Accessible features have to survive deployment. Headphone sockets need inspection. Controls should remain clear of signs, tape and furniture. Staff need to understand the accessible route without taking over the task. Maintenance teams need to know when it has failed.

Analytics can help when they are designed with privacy in mind. Activation, completion, abandonment and fault patterns show whether the accessible journey works outside a test lab.

Accessibility is about independence

Staff assistance can be warm, skilled and essential but this does not automatically replace an accessible self-service route.

Finding an employee creates delay. Asking for help with a PIN, bank balance, medical detail or travel plan can remove privacy. A customer may have chosen self-service precisely because they wanted an independent interaction.

The measure that matters is simple: can the person do what they came to do through a route that preserves choice?

Storm Interface’s NavPad and AudioNav families provide tactile navigation and private audio routes through screen-based menus. They are engineered in the UK and deployed internationally. [Storm Interface: Accessible self-service products] [Storm Interface: NavPad]

Hardware remains one layer of the system. A tactile keypad connected to inaccessible software still leaves the customer stranded. Storm’s work therefore includes accessibility audits, integration planning, deployment support, governance and training. [Storm Interface: Accessibility solutions and consultancy]

Sector by sector: where the EAA reaches the customer

The common requirements apply across the covered categories. Annex I also adds obligations for particular services.

Consumer banking

Consumer banking includes specified credit agreements, investment and ancillary services, payment services, services linked to payment accounts and electronic money.

Identification, electronic signatures, security and payment functions must be perceivable, operable, understandable and robust. Information should be understandable without exceeding level B2 of the Council of Europe’s Common European Framework of Reference for Languages, apart from proper names and unavoidable terms. [European Accessibility Act, Articles 3 and Annex I] [Council of Europe: Common European Framework of Reference for Languages]

The complete banking journey can include an app, website, authentication device, payment terminal, ATM, document, call centre and branch. Evidence has to follow the customer across those channels.

E-commerce

An e-commerce service is provided at a distance, through websites or mobile services, electronically and at the individual request of a consumer, with a view to concluding a consumer contract.

The EAA reaches product information, account creation, consent, checkout, identity, security, payment, confirmation and cancellation. Accessibility information about products and services being sold must be presented where the responsible economic operator provides it. [European Accessibility Act, Article 3(30) and Annex I]

The homepage is rarely the place where a purchase fails.

Passenger transport

The EAA covers defined digital and terminal elements of air, bus, rail and water passenger services. Websites, apps, e-tickets, electronic ticketing, passenger information and real-time information are central. Information should include accessibility details about vehicles, surrounding infrastructure and assistance. [European Accessibility Act, Article 2 and Annex I]

Transport already has a network of passenger-rights regulations. The EAA sits alongside them. [European Commission: Passenger rights]

For urban, suburban and regional transport, the EAA’s passenger-service requirements are largely limited to interactive self-service terminals located within the Union. Other laws may still apply.

E-books

Where an e-book contains audio alongside text, it must provide synchronisation. The file should support assistive technology, navigation, structural information, presentation alternatives and accessibility metadata. Digital-rights management must not block accessibility features. [European Accessibility Act, Annex I]

The EPUB Accessibility specification provides a practical route for publishers and reading-system developers. [W3C: EPUB Accessibility 1.1]

Electronic communications and emergency access

Electronic communications services must provide real-time text in addition to voice and total conversation where video is supplied, subject to the detailed requirements.

Emergency communications must support accessible routes. Answering at 112 must use the same communication means received, appropriately synchronised where voice, text and video are combined. [European Accessibility Act, Annex I]

Access to audiovisual media services

The access service that helps a user find, select, receive information about and use audiovisual content must be accessible.

Accessibility components such as subtitles for Deaf and hard-of-hearing viewers, audio description, spoken subtitles and sign-language interpretation must be transmitted accurately and with adequate quality when supplied. [European Accessibility Act, Annex I]

The Audiovisual Media Services Directive contains related obligations for progressively accessible programming. [Audiovisual Media Services Directive]

Microenterprises, exemptions and small-business reality

The EAA defines a microenterprise as an enterprise employing fewer than ten people and having annual turnover or an annual balance-sheet total no higher than €2 million. Group relationships matter when the size is calculated. [Commission Recommendation 2003/361/EC on SME definitions]

Microenterprises providing services are exempt from the service accessibility requirements and the connected obligations. Product microenterprises do not receive the same blanket exemption.

That distinction catches people out.

A small manufacturer, importer or distributor still needs to identify its legal role. A local entity within a larger corporate group may not qualify as a microenterprise. Other disability, consumer, sector and contractual duties can remain even where the EAA exemption applies. [European Accessibility Act, Article 4(5) and Article 14(4)]

The exemption sets the legal floor. Small organisations still sell to customers with disabilities, supply larger businesses and compete for contracts where accessibility evidence is requested.

National implementation: one Directive with different enforcement landscapes

The common requirements come from EU law. The regulator, procedure and sanction depend on the country and often on the product or service.

This is one of the biggest differences between reading the Directive and running a European compliance programme.

France

Main implementing measures: Law No. 2023-171, Decree No. 2023-931 and a technical order.

Enforcement model: The Directorate-General for Competition Policy, Consumer Affairs and Fraud Control (DGCCRF) has a central role for many products and services. Sector-specific authorities may also be involved.

Practical point: Controls have applied since 28 June 2025. Fines can be imposed for each infringement, while persistent product non-conformity can lead to restrictions or suspension. France provides an online process for notifying exemptions and non-conformity.

France DGCCRF: EAA guidance for professionals

Germany

Main implementing measures: The Barrierefreiheitsstärkungsgesetz (BFSG) and BFSG-Verordnung.

Enforcement model: Market surveillance is conducted at the federal-state level and coordinated through the Market Surveillance Authority of the Länder for Accessibility of Products and Services.

Practical point: Core administrative offences can attract fines of up to €100,000. Germany permits certain existing self-service terminals to remain in use for up to fifteen years.

Germany: BFSG
Germany: BFSG, section 37

Ireland

Main implementing measure: The European Union (Accessibility Requirements of Products and Services) Regulations 2023, S.I. No. 636/2023.

Enforcement model: Compliance is overseen by several sector-specific authorities, including the Competition and Consumer Protection Commission, the Commission for Communications Regulation and the Central Bank of Ireland.

Practical point: Serious offences can lead, following conviction on indictment, to a fine of up to €60,000, imprisonment for up to eighteen months, or both.

Ireland: S.I. No. 636/2023

Italy

Main implementing measure: Legislative Decree No. 82/2022.

Enforcement model: Several sector-specific authorities share responsibility. The Agency for Digital Italy (AgID) has a significant role in digital accessibility and has published guidance for service providers.

Practical point: Organisations need to identify the competent authority for each service they provide. Italy’s European Accessibility Act obligations sit alongside an established national digital-accessibility system.

Italy: Legislative Decree No. 82/2022
AgID: Accessibility and usability

Netherlands

Main implementing measures: The requirements are implemented through several sector-specific laws and decrees.

Enforcement model: Regulators include the Radiocommunications Agency, the Netherlands Authority for Consumers and Markets, the Dutch Authority for the Financial Markets, the Dutch Media Authority, and the Human Environment and Transport Inspectorate.

Practical point: A business offering several types of products or services may be answerable to more than one authority. Accurate classification of each offering is therefore especially important.

Netherlands Government: Accessible products and services

Spain

Main implementing measure: Title I of Law 11/2023.

Enforcement model: Responsibility is shared among national, regional and sector-specific authorities. Coordination arrangements were strengthened in 2026.

Practical point: Penalties follow the relevant sectoral regime, with disability-rights legislation providing a fallback framework. Businesses should identify the competent authority and applicable sanctions for each offering.

Spain: Law 11/2023
Spain: Royal Decree 143/2026

United Kingdom

Main implementing measures: The European Accessibility Act was not transposed into the domestic law of Great Britain. The Equality Act 2010 and the public-sector digital accessibility regulations remain relevant.

Enforcement model: Equality duties are generally enforced through legal claims and sector-specific routes. Public bodies are also subject to monitoring under the accessibility regulations.

Practical point: UK businesses may come within the European Accessibility Act’s scope when conducting covered activities in the EU market. Products placed on that market may require EU CE marking and supporting documentation.

UK: Equality Act 2010
UK Government: Placing CE-marked products on the EU market

These examples are a starting point as national law, regulator guidance and enforcement practice will continue to develop. Product withdrawals, complaints and court decisions will show how authorities interpret evidence, exemptions and corrective action.

A note on the European Economic Area

The Directive is marked as relevant to the European Economic Area. As of August 2026, the EFTA record lists incorporation into the EEA Agreement as pending and the act under scrutiny. Organisations should verify the current position before treating Norway, Iceland and Liechtenstein as identical to EU Member States for EAA purposes. [EFTA: EEA-Lex record for Directive (EU) 2019/882]

EAA, ADA, WAD, UNCRPD and UK law: how the frameworks connect

Accessibility teams often work across multiple legal systems. The frameworks share a concern with participation, but they do different jobs. Here’s a quick summary:

European Accessibility Act

Primary character: An EU internal-market directive that establishes functional accessibility requirements.

Main reach: It applies to defined products and consumer services placed on or provided within the EU market.

Digital and self-service significance: The Act expressly covers selected self-service terminals, websites, mobile apps, e-commerce services, consumer banking services and elements of passenger transport services.

Enforcement pattern: Enforcement takes place through national market-surveillance bodies, service authorities, consumer remedies and penalties. Covered products also follow a CE conformity-assessment route.

Americans with Disabilities Act

Primary character: A broad US civil-rights law.

Main reach: Its titles cover employment, state and local government, public accommodations, telecommunications and other areas of public life.

Digital and self-service significance: The Act’s equal-access and effective-communication principles apply in digital and self-service contexts. The detailed legal treatment varies according to the relevant title and jurisdiction.

Enforcement pattern: The Act is enforced by government agencies and through private litigation. Available remedies include injunctive relief and, depending on the claim, other forms of redress.

Web Accessibility Directive

Primary character: An EU directive governing public-sector digital accessibility.

Main reach: It applies to the websites and mobile applications of public-sector bodies, subject to specified exclusions.

Digital and self-service significance: EN 301 549 provides the harmonised technical route. Public-sector bodies must also publish accessibility statements and provide a mechanism for users to report accessibility problems or request information.

Enforcement pattern: Member States are responsible for monitoring and enforcement, alongside periodic reporting at EU level.

European Commission: Web Accessibility Directive

UN Convention on the Rights of Persons with Disabilities

Primary character: An international human-rights treaty.

Main reach: It binds States Parties and shapes their implementation of disability rights across society.

Digital and self-service significance: Article 9 addresses access to information, communications, information and communications technology, and electronic services. Article 21 covers accessible information and communication.

Enforcement pattern: Compliance is supported through international monitoring and domestic implementation. The Convention does not establish a product conformity scheme.

UK Equality Act 2010

Primary character: Domestic equality and anti-discrimination legislation.

Main reach: It applies across services, employment, education, premises and other areas in Great Britain.

Digital and self-service significance: Service providers have an anticipatory duty to make reasonable adjustments. Barriers affecting websites, digital services and self-service facilities can form part of access to a service.

Enforcement pattern: Duties are enforced through individual claims and sector-specific mechanisms. The remedies available depend on the legal context.

Equality Act 2010, section 20

The ADA and EAA are sometimes presented as American and European versions of the same law, and that comparison is useful up to a point.

The ADA is a civil-rights statute organised into titles covering broad areas of life. The EAA is a targeted market law covering listed products and consumer services. The ADA includes employment. The EAA does not serve as the EU’s general employment-discrimination law. The EAA gives product manufacturers a formal conformity and CE-marking route that has no direct ADA equivalent.

Their common centre is participation. Both ask organisations to identify barriers that exclude people with disabilities and remove them.

The UK position after Brexit

For a British organisation, the legal map has three layers.

First, the Equality Act 2010 remains the central Great Britain framework for disability discrimination and reasonable adjustments. The duty on service providers is anticipatory: organisations should consider the needs of people with disabilities generally before a named person complains. [Equality and Human Rights Commission: Services Code of Practice]

Second, the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply to covered UK public bodies. Government guidance uses WCAG 2.2 AA as the current technical expectation and requires an accessibility statement. [UK Government: public-sector website and app accessibility]

Third, the EAA applies through EU market activity. A British manufacturer exporting a covered terminal needs the EU product-compliance route. A UK online service directed to EU consumers may have service duties.

Northern Ireland requires product-specific analysis under the Windsor Framework and related arrangements. Broad assumptions are risky; the product and supply chain need to be checked. [UK Government: Windsor Framework collection]

This is why British businesses should resist the simple statement that the EAA “does not apply in the UK”. The domestic position and the EU market position are different questions.

How the EAA changes what procurement teams must ask

For many organisations, accessibility enters the conversation too late.

The kiosk has been selected. The software contract has been signed. The payment component has been approved. Enclosure tooling has begun. Deployment dates are fixed.

Then someone asks whether the system is accessible.

At that point, the choices have narrowed. A problem with reach may require a new enclosure. A missing tactile route may affect hardware, firmware and application logic. An inaccessible payment device may involve another supplier. A weak contract may leave nobody clearly responsible for remediation.

Accessibility is a procurement decision long before it becomes a testing result.

Every tender shapes the final experience through the products selected, requirements written, evidence requested, suppliers engaged and acceptance tests agreed.

Article 24 makes that connection explicit in EU public procurement. EAA requirements constitute mandatory accessibility requirements where the procurement directives require accessibility. A vague specification can create procurement risk as well as user exclusion. [European Accessibility Act, Article 24]

Private-sector buyers face the same operational truth: they inherit the limits of the specification and evidence they accept.

Questions every procurement team should ask

• Which EAA product or service category applies?
• Which party is the manufacturer, importer, distributor, authorised representative or service provider?
• Which national laws and regulators apply in each target market?
• Which Annex I requirements are relevant, and where is each one addressed?
• Which standards, versions and clauses support the solution?
• What remains outside those standards?
• Has the complete journey been tested with users with disabilities?
• Can the supplier demonstrate keyboard, screen-reader, tactile, audio, hearing, reach, strength and cognitive accessibility where relevant?
• How does the accessible route protect privacy and security?
• What technical documentation, test results, declaration and CE evidence will be delivered?
• How will third-party components and payment services be governed?
• What happens when an operating system, browser, app, authentication service or hardware component changes?
• Who corrects non-conformity, funds remediation and communicates with authorities?
• What information and training will support customers and staff?
• How will accessibility performance be measured after deployment?

A supplier declaration is one piece of evidence, what procurement teams should be asking for a traceable matrix linking each legal requirement to the design response, test method, result, owner and retained document.

The question “Does this product have accessibility features?” is too weak; the better question is: “Can customers with disabilities independently complete the tasks this product exists to support?”

Building an EAA compliance programme

EAA compliance runs across the product and service lifecycle. A one-off audit begins to age as soon as the product, content or service changes.

The programme needs ten practical elements.

1. Establish governance

Assign accountable leadership and a cross-functional group covering legal, product, design, engineering, procurement, operations, customer service and accessibility expertise. Define who decides, who owns the evidence and how issues escalate.

2. Create a defensible inventory

Record products, services, brands, legal entities, target countries, consumer groups, channels, terminal estates, suppliers and contract dates. Capture when products were first placed on the market and when terminals first entered use.

3. Determine scope and role

Classify each offering against Article 2 and the national law. Identify whether the organisation acts as manufacturer, importer, distributor, authorised representative or service provider. Record exclusions and the evidence supporting them.

4. Map the requirements

Build a matrix covering Annex I, applicable sector provisions, Annex VII, national requirements, standards and contractual duties. Separate web-content criteria from hardware, documentation, support and operational requirements.

5. Assess real journeys

Test priority tasks from beginning to end. For a kiosk, this may start with approaching and finding the device, then activating an accessible mode, navigating, authenticating, paying, receiving confirmation and obtaining help. Include users with disabilities with varied access needs.

6. Remediate by impact and dependency

Prioritise barriers that prevent entry, identification, payment, completion or privacy. Fix shared design-system and platform defects before duplicating work across pages. Coordinate hardware and software changes.

7. Build the evidence file

Retain scope decisions, test plans, results, user-research findings, design specifications, risk decisions, supplier evidence, version information, declarations, technical documentation and corrective actions. Document Article 14 assessments with the discipline expected for an exception.

8. Publish accessible service information

Prepare the Annex V description and make it easy to find and use. Explain the service, accessibility features, limitations, compatibility, support routes and feedback process in accessible language and formats.

9. Control change

Add accessibility acceptance criteria to development, release and procurement. Test design-system changes, software updates, replacement components and new content. Monitor Official Journal citations, standards work and regulator guidance.

10. Measure the experience

Track defects, complaints, completion, abandonment, assistance and uptime of accessible features. Combine quantitative data with regular disabled-user research. Report patterns to the leaders who can change them.

This is less glamorous than an accessibility launch. It is also where accessibility either becomes dependable or slowly disappears.

The cost of retrofitting accessibility and common EAA mistakes

Accessibility failures rarely begin with hostility; they often begin with assumptions.

The team assumes the touchscreen is intuitive. The supplier assumes software covers hardware. The buyer asks for “compliance” without defining evidence. Users with disabilities arrive after launch.

Remediation then touches enclosures, components, software, testing, documentation, contracts, training and hundreds or thousands of physical locations.

Early accessibility work costs time and money. Teams still have choices at that stage: architecture, components, suppliers, interaction methods and test plans. Those choices narrow quickly after tooling and deployment.

An organisation replacing a terminal estate now has a rare opportunity. The chosen hardware may remain in public use for a decade or longer. Accessibility decisions made in the specification will shape millions of interactions.

Several recurring claims deserve particular caution.

“We passed WCAG, so the service complies”

WCAG covers web content. An EAA journey may also contain non-web software, hardware, documents, support, identity, security, payment and product information. WCAG belongs inside a wider evidence model.

“The CE mark proves the kiosk is accessible”

The CE mark is the manufacturer’s declaration that applicable EU requirements have been met. Regulators can examine the technical file and the product. Purchasers still need evidence relevant to the integration and service.

“Our supplier owns accessibility”

Responsibilities follow legal roles. A service provider cannot contract away its customer duty. Importers and distributors have their own obligations. Contracts allocate work and risk; they do not rewrite public law.

“Staff can help anyone who cannot use it”

Assistance can introduce delay, dependence and loss of privacy, particularly during payments, healthcare and banking. An accessible self-service route protects choice.

“Existing terminals are exempt until 2045”

The Directive permits Member States to allow certain existing terminals until the end of economic life, with a maximum of twenty years after first use. National implementation can be shorter. The service, software or contract may have a different date.

“We are too small for the EAA”

The blanket microenterprise exemption applies to service providers meeting the definition. Product duties are different. Group relationships affect the calculation, and other legal or contractual accessibility duties may remain.

“Accessibility belongs to the legal team”

Lawyers interpret the duties. Engineers control code. Product teams control roadmaps. Procurement sets supplier requirements. Operations maintains equipment. Support teams hear the problems. Leaders allocate resources.

Nobody carries the whole system alone.

Storm Interface’s perspective: design for the complete person and the complete journey

Storm Interface is a British manufacturer with a global customer base. Its work in accessible self-service began with a practical challenge: create a robust outdoor interface that visually impaired people could use.

The result was the NavPad, launched in 2005, followed by a wider range of tactile and audio-capable technology. [Storm Interface: How Storm helped shape self-service keypad accessibility]

The lesson from that work is simple: Accessibility has to survive the real environment.

Controls need to remain discoverable after thousands of uses. Audio has to work in a noisy public space without disclosing private information. Software must respond predictably to tactile input. The terminal needs to work for a wheelchair user and for someone standing. Staff need to recognise the accessible route. Maintenance teams need to know when it has failed.

Storm’s approach starts with the customer’s task and the barriers around it. An audit can examine physical access, sensory access and digital experience. A roadmap can then connect hardware, software, integration, testing, rollout and governance. [Storm Interface: Accessibility solutions and consultancy]

The company’s technology can support:

• tactile navigation and selection;
• private audio navigation through a personal headset;
• high-contrast, durable controls;
• interfaces suited to demanding public environments;
• integration with kiosk platforms and accessible software.

The right configuration depends on the service, customer, environment and market. No product page can perform that analysis.

The EAA should prompt a wider review than the replacement of one inaccessible control.

Can every person find the service, begin the task, understand what is happening and finish with the same confidence?

Beyond compliance: the future of accessibility in Europe

The EAA’s application date has passed. Its practical meaning will continue to develop.

Regulators will investigate. Courts will interpret national provisions. Harmonised standards will mature. Products designed before 2025 will move through transition and replacement cycles. Customers will keep exposing the distance between technical claims and everyday reality.

The useful questions are straightforward:

• Who is excluded by the way this experience works today?
• Can the customer find and activate the accessible route?
• Can they complete the same task with privacy and choice?
• Does the evidence match the legal claim?
• Will accessibility still work after the next update?

The EAA gives those questions legal force across a large part of the European market.

Its value will be felt in ordinary moments: buying a ticket, checking in for a journey, reading a book, making a payment, contacting emergency services or ordering a meal.

Customers will not see the conformity assessment, procurement matrix or accessibility audit behind the interaction.

They will know whether the service worked.

That is where the EAA’s promise becomes real: one person, one task and one interaction at a time.

References

• [Directive (EU) 2019/882: European Accessibility Act]
• [European Commission: European Accessibility Act]
• [EUR-Lex summary: Accessibility of products and services]
• [EUR-Lex: National transposition measures for Directive (EU) 2019/882]
• [European Commission proposal COM(2015) 615]
• [European Commission impact assessment SWD(2015) 264]
• [EUR-Lex legislative procedure 2015/0278(COD)]
• [Council of the EU: Accessibility of products and services]
• [Council of the EU: adoption of the Accessibility Act, 9 April 2019]
• [European Parliament legislative resolution, 13 March 2019]
• [Treaty on the Functioning of the European Union, Article 114]
• [UN Convention on the Rights of Persons with Disabilities]
• [UN Committee: General Comment No. 2 on accessibility]
• [European Commission: Persons with disabilities in the EU]
• [European Commission: Strategy for the Rights of Persons with Disabilities 2021-2030]
• [Eurostat: Population with disability]
• [Eurostat: Disability and access to information and communication technologies]
• [World Health Organization: Disability and health]
• [Directive (EU) 2016/2102: Web Accessibility Directive]
• [European Commission: Web Accessibility Directive]
• [European Commission: WAD standards and harmonisation]
• [European Commission: requirements in EN 301 549 beyond WCAG]
• [ETSI: EN 301 549 V3.2.1]
• [ETSI Labs: EN 301 549 project]
• [AccessibleEU: EN 301 549 overview]
• [European Commission: standardisation request M/587]
• [CEN-CENELEC: Accessibility]
• [CEN-CENELEC: eAccessibility]
• [CEN-CENELEC Work Programme 2026: Inclusivity and Accessibility]
• [AccessibleEU: revised EAA and WAD guidance, June 2026]
• [W3C: Web Content Accessibility Guidelines 2.2]
• [W3C: WCAG 2 Overview]
• [W3C: What’s New in WCAG 2.2]
• [W3C: Evaluating Web Accessibility Overview]
• [W3C: Easy Checks – A First Review of Web Accessibility]
• [W3C: Involving Users in Web Accessibility Evaluation]
• [W3C: Accessibility Principles]
• [W3C: EPUB Accessibility 1.1]
• [W3C: European Union accessibility laws and policies]
• [ISO/IEC 40500:2025 – WCAG 2.2]
• [ISO 21542:2021 – Building construction, accessibility and usability]
• [CEN-CENELEC: Accessibility of the built environment]
• [CEN-CENELEC: Design for All]
• [Directive 2014/24/EU on public procurement]
• [Directive 2014/25/EU on procurement by utilities]
• [Regulation (EU) 2019/1020 on market surveillance]
• [European Commission: CE marking]
• [European Commission: Blue Guide on EU product rules, 2022])
• [Commission Recommendation 2003/361/EC on SME definitions]
• [Directive (EU) 2018/1972: European Electronic Communications Code]
• [Directive 2010/13/EU: Audiovisual Media Services Directive]
• [European Commission: Passenger rights]
• [Regulation (EC) No 1107/2006: air passengers with disabilities]
• [Regulation (EU) 2021/782: rail passengers’ rights]
• [Regulation (EU) No 181/2011: bus and coach passenger rights]
• [Regulation (EU) No 1177/2010: sea and inland waterway passenger rights]
• [Council of Europe: Common European Framework of Reference for Languages]
• [France: Law No. 2023-171]
• [France: Decree No. 2023-931]
• [France: Order on accessibility requirements]
• [France DGCCRF: EAA guidance for professionals]
• [France DGCCRF: notifying exemptions and non-conformity]
• [Germany: Accessibility Strengthening Act (BFSG)]
• [Germany: BFSG Regulation]
• [Germany: Federal Accessibility Centre EAA information]
• [Germany: BFSG frequently asked questions]
• [Germany: BFSG section 37 penalties]
• [Ireland: S.I. No. 636/2023]
• [Government of Ireland: European Accessibility Act]
• [Italy: Legislative Decree No. 82/2022]
• [Italy AgID: Accessibility and usability]
• [Italy AgID: EAA service accessibility guidelines, 2026]
• [Netherlands Government: accessible products and services]
• [Netherlands: EAA implementation record]
• [Spain: Law 11/2023]
• [Spain: Royal Decree 143/2026]
• [EFTA: EEA-Lex record for Directive (EU) 2019/882]
• [UK: Equality Act 2010]
• [UK: Equality Act 2010, section 20]
• [Equality and Human Rights Commission: Services Code of Practice]
• [UK Government: public-sector website and app accessibility]
• [UK Government: placing CE-marked products on the EU market]
• [UK Government: Windsor Framework collection]
• [ADA.gov: The Americans with Disabilities Act]
• [Storm Interface: Home]
• [Storm Interface: About]
• [Storm Interface: Accessible self-service products]
• [Storm Interface: Accessibility solutions and consultancy]
• [Storm Interface: Retrofitting self-service kiosks]
• [Storm Interface: How Storm helped shape self-service keypad accessibility]
• [Storm Interface: Accessibility expert]
• [Storm Interface: NavPad]
• [European Disability Forum: analysis of the European Accessibility Act]
• [European Disability Forum: Emergency Resolution on the European Accessibility Act, December 2017]
• [European Disability Forum: Annual Report 2016-2017]
• [European Disability Forum: Resolution on the European Accessibility Act, November 2018]

Sources and legal position last checked 04 September 2026.