The European Accessibility Act (EAA) covers ATM software as part of its self-service terminal scope. ATM accessibility software must meet EN 301 549 requirements, which incorporate WCAG 2.1 Level AA for any web or app interfaces and add hardware-software interaction criteria specific to self-service terminals. Banks and ATM manufacturers placing products on the EU market are responsible for conformance. The EAA went into effect on June 28, 2025. ATMs already in service before that date may continue operating under transitional terms, but new deployments and replacements must meet the standard.
| Area | Requirement |
|---|---|
| Governing standard | EN 301 549, which references WCAG 2.1 AA for digital interfaces |
| Effective date | June 28, 2025 |
| Who is responsible | Banks, ATM operators, and manufacturers placing terminals on the EU market |
| Software scope | On-screen interfaces, audio output, input methods, timing, and assistive technology support |
| How to verify | An accessibility evaluation against EN 301 549 and WCAG 2.1 AA |
What the EAA Says About ATMs
Self-service terminals are named directly in the EAA, and ATMs are the most common example. The Act treats the ATM as a product with both hardware and software requirements. The software side covers everything the user sees, hears, and interacts with on screen.
The technical reference point is EN 301 549, the harmonized European standard for ICT accessibility. EN 301 549 pulls in WCAG 2.1 Level AA for web and app interfaces and adds clauses specific to hardware, biometrics, and self-service terminals. ATM software must meet both layers.
Which Software Components Must Conform?
The ATM transaction flow is mostly software, even when the user is pressing physical keys. Every screen the user sees, every prompt the machine speaks, and every input method available falls within scope.
Key components covered by EN 301 549 include on-screen text, contrast, and font sizing. Audio output through headphone jacks is required for users who cannot read the screen. Tactile keypad mapping to on-screen actions must be supported. Timing adjustments must give users enough time to complete transactions. A privacy mode for audio-assisted transactions is expected. The software must support users with limited reach, dexterity, or vision. Multilingual interface options are also in scope where the ATM serves multiple languages.
Each of these maps to specific clauses in EN 301 549 and, where applicable, WCAG 2.1 AA success criteria.
Who Is Responsible for Conformance?
The EAA places obligations on three roles: manufacturers, importers, and distributors. For ATMs, this typically means the hardware manufacturer, the bank or financial institution operating the terminal, and any third party providing the software stack.
If a bank licenses ATM software from a vendor, the bank is still accountable for the terminal’s conformance once it is deployed. Vendor documentation does not transfer liability. Both parties benefit from independent verification.
How Do You Verify ATM Software Meets EAA Requirements?
The only reliable path is an accessibility evaluation conducted against EN 301 549 and WCAG 2.1 AA. Automated scans only flag approximately 25% of issues, and most ATM-specific criteria, such as audio guidance, tactile mapping, and timing behavior, cannot be detected by a scan at all.
An auditor walks through each transaction flow, evaluates every screen, and confirms that audio output, input methods, and timing work as the standard requires. The audit identifies issues by criterion, severity, and location, which gives the development team a clear remediation path.
Documentation You Should Expect
EAA conformance is not a single certificate. It is a set of records that together demonstrate the product meets the standard. For ATM software, the expected documentation includes an audit report against EN 301 549 with WCAG 2.1 AA criteria evaluated, a remediation plan addressing identified issues, validation that fixes were implemented correctly, an accessibility statement available to users, and internal records of conformance work kept on file for market surveillance authorities.
Accessible.org clients typically receive a full audit report along with a project plan for remediation and validation.
Common Issues Identified in ATM Software Audits
Audits of ATM interfaces tend to surface the same categories of issues across manufacturers. Color contrast on transaction screens frequently falls below the 4.5:1 ratio. Audio prompts may not match on-screen content exactly. Timing windows that cannot be extended by the user are common. Touchscreen-only interactions with no tactile alternative appear regularly. Error messages that are visual only, with no audio equivalent, are another frequent finding. Receipt printing options that bypass the audio flow also come up often.
Each of these maps to a specific WCAG criterion or EN 301 549 clause, so the remediation path is clear once the audit is complete.
FAQs
Does the EAA require WCAG 2.1 AA for ATMs?
Indirectly, yes. The EAA points to EN 301 549 as the technical standard, and EN 301 549 incorporates WCAG 2.1 AA for digital interfaces. ATM software with a screen-based interface must meet those criteria along with the self-service terminal clauses in EN 301 549.
Are older ATMs grandfathered under the EAA?
ATMs placed on the market before June 28, 2025 may continue to operate under transitional provisions until the end of their service life or up to 20 years, depending on national implementation. New deployments, software updates that change the user interface, and replacements must meet the EAA.
Can a vendor’s accessibility statement substitute for an audit?
No. A vendor statement is a useful starting point, but the operator deploying the ATM is responsible for conformance in its specific configuration. An independent audit verifies the deployed software, not the vendor’s general claim.
How long does an ATM software audit take?
It depends on the number of transaction flows, languages supported, and hardware variants. A typical ATM software audit takes a few weeks from kickoff to delivery of the report.
What happens if an ATM does not meet EAA requirements?
Market surveillance authorities in each EU member state can require corrective action, restrict sales, or impose fines. Banks also face reputational and legal risk from users who cannot complete transactions independently.
ATM accessibility software conformance is a documentation exercise as much as a technical one. The audit is what converts the EAA’s broad requirements into a concrete list of fixes your team can work through.
Contact Accessible.org to request an audit quote for your ATM software.
