The European Accessibility Act (EAA) is now the operating reality for self-service kiosks across the European Union. While new regulations can feel complex, it also gives organizations an opportunity to rethink their self-service strategy, reduce friction, and strengthen the customer experience. Self-service technology is supposed to make transactions easier. But if people who are blind or have low vision can’t independently check in, buy a ticket, or complete key tasks, the experience falls short. That creates frustration, increases staff intervention, and quietly erodes brand trust. In this post, we’ll share a practical roadmap for improving accessibility across your terminal ecosystem in a way that’s sustainable, measurable, and built for the real world.

How the EAA impacts self-service devices

To meet EAA requirements, self-service devices must support users with a wide range of abilities, including visual, mobility, and cognitive disabilities.  Accessibility needs to be built into both hardware and software, with intuitive interfaces, clear instructions, consistent navigation, and assistive technology compatibility. Devices should also offer alternative input methods like tactile buttons.  Beyond the device itself, documentation, product labels, and user guidance must be usable by everyone, enabling independent interaction from start to finish. The question then becomes: how do you operationalize this in a way that’s scalable and sustainable?

1. Start by understanding EAA fundamentals

The EAA isn’t a one-time compliance exercise. It’s an accessibility obligation that applies across the full lifecycle of self-service kiosks, from design and development to deployment, updates, and long-term support. For organizations that own, operate, or deploy kiosks, three fundamentals matter most.  First, the EAA helps harmonize accessibility requirements across EU member states, reducing the patchwork of country-specific expectations. Second, it applies broadly across the ecosystem, including manufacturers, distributors, importers, and service providers operating in EU markets. Third, while some existing self-service deployments may have extended transition timelines depending on classification, new deployments need to meet accessibility expectations from day one. The bottom line: treating accessibility as phase two almost always costs more later, whether that cost appears as rework, deployment delays, or customer friction. Organizations that lead in self-service treat accessibility as a core requirement from the start

2. Bake accessibility into procurement lifecycles

A common misstep occurs when organizations outsource accessibility to vendors without clear expectations. Under the EAA, accessibility isn’t something that can be bolted on after a product has shipped or a kiosk has been installed. It’s something organizations must specify, verify, and enforce before contracts are signed. Accessible kiosks begin with clearly defined procurement requirements that cover both hardware and software. For example, hardware should align with EN 301 549 accessibility expectations, including tactile controls where appropriate, reachable interfaces, and audio support. On the software side, kiosk interfaces should align with Web Content Accessibility Guidelines (WCAG) 2.1 AA where applicable, with predictable navigation, clear prompts, and compatibility with assistive technologies (AT) such as screen readers. This approach ensures vendors are accountable and gives your teams the documentation you’ll need if regulators request proof of conformance.

3. Design for real inclusive experiences

Accessibility extends beyond any single regulation or requirement; it’s about real people completing real tasks. A kiosk with text-to-speech support may appear conformant on paper, but that only matters if the flow is intuitive for a blind or low vision customer using it. The same goes for visual contrast, timing, and input methods: accessibility features must work together as a coherent experience. For organizations that develop and design their own kiosks, it’s important to design with inclusion in mind:

  • Use high-contrast visuals and adjustable text size to support users with low vision.
  • Ensure screen reader compatibility and keyboard navigation support blind and low-vision users.
  • Inclusion of audio output with optional headset support, a requirement under the EAA for many self-service devices.
  • The kiosk should be compatible with tactile Braille feedback or other external hardware devices.

Tools like JAWS for Kiosk, the only screen reader purpose-built for kiosk environments, create consistent, accessible interactions tailored to terminal interfaces. When organizations design self-service experiences with accessibility from the start, they do more than meet regulatory requirements. They reduce friction, foster independence, and increase customer satisfaction.

4. Validate with inclusive usability testing

Automated scans and standards-based reviews are important, but these can only confirm whether a kiosk appears compliant on paper. These reviews can’t validate whether a person with disabilities can walk up to a kiosk and complete a task independently. The EAA calls for products and services to be usable by people with disabilities—not just technically conformant—and one of the most effective ways to uncover accessibility gaps is through inclusive usability testing. When you test with disabled people who rely on AT and alternative interaction methods, you uncover issues that tools and internal teams routinely miss. The most common problems aren’t edge cases, either. They’re often unclear prompts, confusing focus order, missing audio guidance, timeouts that can’t be extended, or interactions that technically “work” but require too much guesswork to be usable. As a best practice, before widespread deployment or updates, organizations should:

  • Test with screen reader users
  • Include keyboard-only participants
  • Involve people with low vision, hearing impairments, and motor disabilities

The insights help refine interactions and demonstrate that self-service kiosks are not only technically compliant but usable and accessible in practice.

5. Prepare for ongoing compliance, not just a one-time deadline

While June 28, 2025, was the major deadline for when EAA requirements kicked in, compliance doesn’t stop once a kiosk goes live. It’s an ongoing responsibility, especially as software updates roll out, hardware gets refreshed, and UI flows change over time. Though some existing self-service deployments may have longer transition windows depending on how they’re classified and maintained, the operational reality in 2026 is clear: accessibility needs to be treated as an ongoing part of your kiosk program, not a one-time remediation project. To stay compliant (and avoid regressions that quietly break the user experience), build accessibility into your operational rhythm:

  • Audit accessibility regularly, especially after firmware updates, UI changes, or vendor patch cycles.
  • Maintain internal accessibility policies and documentation so teams aren’t reinventing the wheel every time a kiosk gets refreshed.
  • Create clear feedback paths so customers and frontline staff can report issues quickly and consistently.
  • Hold vendors accountable with defined accessibility requirements, testing expectations, and support commitments.

Documentation also matters. Enforcement authorities can request evidence of accessibility measures, and having that ready is far easier than trying to reconstruct decisions and test results after the fact.

Treat EAA compliance as a business opportunity

The EAA is a compliance requirement, but it’s also a strategic opportunity to future-proof self-service customer experiences. Organizations that address accessibility early can avoid costly retrofits, strengthen customer trust, and build more resilient self-service programs over time. To evaluate your self-service environment and build a stronger accessibility strategy under the EAA, connect Vispero’s Digital Accessibility Services experts.