Digital Accessibility for closed Systems and Applications

Published: 14/11/2026

Accessibility for Closed Systems and Applications An infographic explaining accessibility requirements for closed systems like ATMs and ticket machines under EN 301 549 Chapter 5, WCAG2ICT, and the European Accessibility Act (EAA). Accessibility for Closed Systems & Applications Built-in accessibility for ATMs, ticket machines, and terminals under EN 301 549 & the European Accessibility Act. 1. Concept & Regulatory Framework CLOSED SYSTEMS No External Assistive Tech Supported • Devices/apps that block user-installed screen readers or external peripherals (e.g., for security or kiosk mode). • Examples: ATMs, ticket machines, self-service kiosks. • Challenge: Accessibility must be built directly into the unit. STANDARDS & EU LAW Binding Legal Requirements • WCAG2ICT: W3C guidance applying WCAG to non-web ICT. • EN 301 549 (Ch. 5): Technical standard for closed hardware. • EAA (Dir. 2019/882): Mandates compliance for terminals & ATMs (centralized fleets make monitoring straightforward). 2. Core Requirements under EN 301 549 (Chapter 5) Clause 5.1.2 No Assistive Tech Needed System must remain fully operable without installing external assistive software or hardware. Clause 5.1.3 Non-Visual Access Must provide built-in navigation and operation modes usable by blind or visually impaired people. Clause 5.1.4 Speech Output Channels Where speech output is provided, it must be delivered via suitable channels (headphones or speakers). Clause 5.1.5 Visual Parity for Audio Any information communicated audibly (beeps, voice cues) must also be displayed visually in parallel. Clause 5.1.6 Operation Without Keyboard Alternative input methods must be built in when a physical keyboard cannot be connected. Clause 5.1.7 Operation Without Speech If voice control is offered, a non-vocal alternative mode is mandatory for users who cannot speak. 3. Specific Terminal & EAA Hardware Requirements (Annex I, Sec. I) Self-Service & Ticket Terminals 1. Complete Speech Flow: Reading labels on touch is not enough—entire navigation, errors & feedback must be spoken. 2. Privacy Protection: Speech output must not broadcast publicly (protect PINs & balances via headphone jacks). 3. Easy Self-Activation: Users must activate speech or zoom independently (e.g., plugging in headphones or a tactile button). EAA Annex I, Section I (Hardware Specs) Personal Headsets: Speech output & standard audio jack. Flexible Timing: Extendable time limits for user responses. Tactile & Contrast: High visual contrast, tactilely discernible and easily operable physical keys and controls. Hearing Aid Support: Compatibility for acoustic signals. 4. EAA Functional Performance Criteria (Annex I, Section VII) Fallback Rule: If a rigid technical rule cannot be met 1:1, alternative designs are allowed if they deliver equivalent or greater accessibility: Criterion (a): Without Vision Provide at least one non-visual operation mode wherever visual interfaces are used. Criterion (b): Limited Vision Support low-vision operation and ensure usability without relying on color perception. Criterion (d): Without Hearing Offer at least one operation mode that does not require hearing when audio cues are used. Criterion (f): Without Speech Provide non-vocal input options wherever voice, whistling, or vocal sounds are required. Criterion (h): Reach & Strength Keep controls within physical reach for all users and operable with limited muscle strength. Criterion (i): Limited Cognition Include features that simplify interaction for users with cognitive limitations. Closed hardware is no excuse: Accessibility must be integrated directly into terminals, ATMs, and kiosks.

Closed systems are applications, devices, or units that either do not support assistive technologies (e.g., traditional ticket machines) or do not allow general access (e.g., for security reasons or on special-purpose retail tablets).

Typical examples include ATMs, self-service terminals, ticket machines, or specialized in-store hardware where input options (keyboards, screens) have been strictly limited for security or functional purposes. To apply WCAG to non-web content, the W3C provides an official guidance document called WCAG2ICT (Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies). It explains how WCAG criteria must be applied to software and documents outside the web (e.g., what constitutes a "web page" in the context of a desktop app). Implementation in EN 301 549 EN 301 549 breaks this concept down into specific chapters that are directly legally relevant (under the European Accessibility Act):

Under the European Accessibility Act (EAA, Directive (EU) 2019/882) and its national transpositions across EU member states, certain hardware systems are legally required to be accessible.

The problem: Because these devices often lack standard interfaces for assistive technologies (such as screen readers), manufacturers frequently argue that accessibility is not technically feasible here.

The requirement: Nevertheless, both the legislation and EN 301 549 mandate that closed systems must meet specific requirements to minimize disadvantages for users with disabilities.

Requirements under EN 301 549 (Chapter 5)

The European standard EN 301 549 dedicates Chapter 5 to detailed requirements for closed systems. The following requirements are defined:

  • Operation without assistive technologies (Clause 5.1.2): A system must still be operable even if assistive technologies cannot be installed.
  • Non-visual access (Clause 5.1.3): Access must also be possible for blind or visually impaired users.
  • Speech output (Clause 5.1.4): Where speech output is provided, it must be delivered via appropriate channels (typically headphones or speakers).
  • Auditory information (Clause 5.1.5): Information communicated audibly must also be presented visually in parallel.
  • Operation without a keyboard (Clause 5.1.6): Alternative operation must be possible if a physical keyboard cannot be connected.
  • Operation without speech (Clause 5.1.7): Where a speech interface is present, there must always be an alternative mode of operation for people who cannot speak.

Specific requirements for ticket and self-service terminals:

  • Complete speech output: Simply reading out text content or menus upon touch is not enough; the entire navigation flow (including error messages and system feedback) must be conveyed via speech.
  • Privacy during operation: Speech output must not broadcast uncontrollably into the surrounding room (protecting PIN entries or account balances via headphone jacks or alternative privacy solutions).
  • Easy activation: Accessibility features (such as enabling speech output or magnification) must be quick and easy for affected users to activate without external assistance (e.g., simply by plugging in headphones or pressing an easily locatable hardware button).

Reference to the European Accessibility Act

Annex I of the European Accessibility Act (Directive (EU) 2019/882) specifies the legal obligations for economic operators across the EU and directly addresses these hardware requirements:

  • Covered products: ATMs, self-service terminals (e.g., in supermarkets), and ticketing machines fall directly within the scope of the directive.
  • Transitional periods: Existing hardware systems are often subject to extended transitional periods, which is why the market is still in transition. However, while there is a vast number of online shops, apps, and physical machines, implementation in the brick-and-mortar sector (machines, terminal operators) is often easier to plan and oversee than in the larger, more fragmented e-commerce market. There are relatively few manufacturers, making compliance easier to monitor. Similarly, major operators such as supermarket chains are straightforward to audit, as they typically deploy a standardized system across all branches.

Here are the requirements under Annex I, Section I of the EAA (Specific technical requirements):

  • Provision of speech output and support for personal headsets.
  • Extendable time limits for user responses.
  • Sufficient contrast, tactile discernibility, and operability of keys and controls (crucial for people with visual impairments).
  • Compatibility with hearing aids for acoustic signals.

Annex I, Section VII of the EAA (Functional Performance Criteria)

Annex I, Section VII of the European Accessibility Act (Functional Performance Criteria) provides guidance for economic operators who cannot implement specific core requirements on a one-to-one basis.

When manufacturers of closed systems (such as terminals or self-service machines) argue that certain rigid technical specifications cannot be implemented exactly as prescribed, the Functional Performance Criteria apply. The directive permits falling back on these functional criteria as an alternative—provided that doing so results in equivalent or greater accessibility. For closed systems, this means developers may choose alternative technical solutions, but the end result must deliver the same accessible benefit to people with disabilities.

  • Usage without vision (Criterion a): Where a product or service provides visual modes of operation, at least one mode of operation must be provided that does not require vision.
  • Usage with limited vision (Criterion b): Where a product or service provides visual modes of operation, at least one mode of operation must be provided that enables users to operate the product with limited vision, including usage that does not require color perception.
  • Usage without hearing (Criterion d): Where a product or service provides auditory modes of operation, at least one mode of operation must be provided that does not require hearing.
  • Usage without vocal capability (Criterion f): Where vocal input (speaking, whistling, clicking, etc.) is required from the user, at least one alternative mode of operation must be provided that does not require vocal input.
  • Usage with limited reach or strength (Criterion h): Controls must be within reach of all users. Additionally, where manual operation is required, at least one mode of operation must allow use with limited reach and strength.
  • Usage with limited cognition (Criterion i): The product or service must include features that make it simpler and easier to use for people with cognitive limitations.

More on Core UI & Patterns