Quick answer: Scope EU and US accessibility separately. The EAA applies to covered products and services, with national implementation to check ( EU Council overview ). Section 508 federal ICT requirements include WCAG 2.0 A/AA plus applicable hardware and software provisions ( GSA kiosk example ); ADA obligations are a separate assessment. Agree the standard edition, task, hardware configuration and test evidence before design freeze; neither a website audit nor a generic cabinet guarantees compliance.
Overview
Quick answer: Scope EU and US accessibility separately. The EAA applies to covered products and services, with national implementation to check ( EU Council overview ). Section 508 federal ICT requirements include WCAG 2.0 A/AA plus applicable hardware and software provisions ( GSA kiosk example ); ADA obligations are a separate assessment. Agree the standard edition, task, hardware configuration and test evidence before design freeze; neither a website audit nor a generic cabinet guarantees compliance.
EAA timeline: why the compliance window is open right now
The EAA is not a future deadline — it is an active one with long tail-offs that most kiosk buyers misread. The transition rules are the part worth reading twice:
| Milestone | Date | What it means for a kiosk project |
|---|---|---|
| Directive adopted | 2019 | Directive (EU) 2019/882 adopted; distinguish adoption, entry into force and application dates. |
| Member-state transposition | 28 June 2022 | National laws in force — e.g. Germany’s BFSG (Barrierefreiheitsstärkungsgesetz). |
| Requirements apply | 28 June 2025 | Requirements apply to products and services within the Directive’s scope, subject to applicable national rules and transitions. |
| Service contracts agreed earlier | Until 28 June 2030 max | An existing contract may run out, but no longer than five extra years. |
| Self-service terminals already in use | End of economic life, no more than 20 years after commissioning | Confirm the national transition for terminals used before 28 June 2025; assess commissioning date, replacement and changes ( AccessibleEU transition summary ). |
| Microenterprise exemption | Ongoing | Service-provider exemptions require the statutory microenterprise definition. Assess product obligations and any relief separately under the applicable national law. |
Three practical consequences: define which terminals and services are in scope, record commissioning and change history, and get a configuration-specific assessment. Enforcement is national; Germany’s BFSG §37 distinguishes offences with different maximum fines rather than imposing one automatic penalty on every kiosk.
EAA and ADA are not the same job
Buyers running both EU and US sites often assume one accessibility spec covers both. It does not — the standards differ in legal basis, scope and remediation trigger:
| Dimension | EU — EAA / EN 301 549 | US — ADA / Section 508 |
|---|---|---|
| Legal nature | Directive (EU) 2019/882 — harmonising product & service requirements | ADA = civil-rights law (Title II public entities, Title III public accommodations); Section 508 = federal procurement |
| Technical benchmark | Confirm the applicable standard edition and clauses. ETSI EN 301 549 v4.1.1 (2026-09) is published; publication alone does not prove its Official Journal citation for a particular Directive. | Assess the device, service and jurisdiction under ADA requirements, including effective communication . For federal ICT, use the Revised Section 508 Standards, not a blanket WCAG 2.1 assertion. |
| What triggers conformance | Covered products and services; assess national transition rules and changes for the specific terminal | Providing goods or services through an inaccessible interface; Section 508 applies to federal acquisitions |
| Sector overlays | Banking, e-commerce, transport, telecoms, e-books | ACAA for air travel kiosks; ACA Section 1557 for healthcare kiosks; state laws (e.g. California, Colorado) |
| Typical evidence | EN 301 549 test report + accessibility conformance report | Applicable ADA assessment; Section 508 ACR when relevant, with the exact standard edition and remediation documented |
Use a shared engineering checklist where useful, but maintain separate EU and US applicability and conformance matrices. The Commission’s WAD harmonisation guidance must not be treated as proof of EAA harmonisation. Verify the current Official Journal reference, national scope and contract edition with your compliance adviser.
What to certify: the two layers most projects under-scope
Accessibility exposure on a kiosk almost always sits in the layer the buyer forgot. Test both, separately, and name an owner for each:
| Layer | Governed by | What must be verified |
|---|---|---|
| Hardware | Applicable hardware and closed-functionality clauses; separate ADA/installation assessment | Reach range for operable parts, screen position and legibility, tactile discernibility of controls, speech output level & control, hearing-aid coupling, a means for a user to enable speech output non-visually. |
| On-screen software | Applicable software clauses and WCAG edition named in the assessment | Screen-reader reachable controls, focus order, contrast, text resizing, timeouts with an extension path, no audio-only instructions, error identification. |
| Service / operation | EAA service obligations | Session reset that does not strand a user, a documented assisted path where self-service cannot complete, and staff trained not to treat assistance as a substitute for conformance. |
Hardware spec decisions to fix before tooling
These are the items that are cheap to design in and expensive to retrofit. Values below are drawn from EN 301 549 and ADA-related guidance — confirm the exact clause against the current standard text with your test lab:
| Requirement area | Spec direction to confirm | Why it is a tooling item |
|---|---|---|
| Reach range | Operable parts within an ADA-aligned forward reach band (commonly cited as 15–48 in / 380–1220 mm) — validate against your market’s rule | Drives screen height, card slot and cash-slot placement on the enclosure. |
| Screen legibility | Display visible from the reference viewing point (ADA guidance references a point 40 in above the centre of the clear floor space); characters with a minimum cap height and a sans-serif face; light-on-dark or dark-on-light contrast | Panel size, tilt and bezel are fixed at tooling. |
| Tactile operation | Physical keys/controls tactilely discernible; shared-use devices that can output speech provide a tactile means to activate the speech mode | Requires real buttons or a tactile overlay — not a pure glass touchscreen. |
| Speech output | Document adjustable volume, controls and privacy against the applicable clause and test protocol | Needs an amplified audio path and a physical control surface. |
| Hearing-aid compatibility | Magnetic coupling / telecoil compatible output where speech is provided | Audio module choice; hard to add after enclosure sealing. |
| Headphone / privacy | A standard audio jack or equivalent private-listening provision | Exterior port plus internal routing. |
| Audio-visual pairing | Where output is audio-only or visual-only, provide a corresponding visual or audible indicator | Indicator placement and UI work. |
Note: accessibility features are configuration items, not a single SKU attribute. A touch-only configuration and a tactile + speech configuration are different builds of the same cabinet, and the accessible variant usually changes the front panel, the keypad, the audio module and the software layer.
What to put in the RFQ
Ask for evidence, not adjectives. An accessibility claim without a document is not a claim you can defend to a market-surveillance authority:
- EN 301 549 test report covering both the hardware and software clauses, naming the standard version tested.
- Accessibility conformance report (ACR/VPAT) against the applicable standard and edition, with known limitations stated, not omitted.
- Accessible-configuration bill of materials : tactile keypad, speech module, headphone provision, screen height — so the accessible variant is orderable, not a one-off.
- The assisted-service fallback in writing: what a user does when self-service cannot complete the task.
- Contact path for accessibility feedback , since most national EAA implementations require one.
EAA certification checklist: the evidence to collect
Use this checklist as a certification checklist for an EAA self-service kiosk — one row per document, with the owner and the point in the project where it must exist. Anything you cannot produce on request is, in practice, an unmanaged accessibility risk.
| Evidence item | Standard / basis | What it proves | When to request |
|---|---|---|---|
| EN 301 549 test report (hardware + software clauses) | EN 301 549 edition and applicable clauses named | The terminal was tested against the applicable hardware and software clauses, not just the screen | Before design freeze — vet the supplier, not the finished cabinet |
| Accessibility conformance report (ACR/VPAT) | Applicable standard and WCAG edition stated in the ACR | The on-screen software’s conformance level, with known limitations disclosed rather than omitted | With the quotation, refreshed on major software releases |
| Accessible-configuration bill of materials | Project specification | The accessible variant (tactile keypad, speech module, headphone provision, screen height) is a repeatable orderable build | At configuration sign-off |
| Assisted-service fallback procedure | EAA service obligations | A defined path for a user when self-service cannot complete the task | Before go-live, with staff training evidence |
| Accessibility feedback contact | National EAA implementations | A required route for users to report accessibility barriers | At deployment |
| EU Declaration of Conformity / CE-marking route (where applicable) | EAA product requirements | That product-scope obligations were addressed through the correct conformity route | Confirm applicability with your test lab and responsible compliance adviser per configuration |
Caution: whether CE-marking under the EAA applies depends on the product category and configuration — verify the route for your specific build with the responsible compliance adviser rather than assuming it from this table.
Where deployments actually fail
| Failure | Why it happens | De-risk move |
|---|---|---|
| Buyer certifies the website, not the kiosk | Teams reuse the web accessibility audit and assume it covers the terminal | Scope the EN 301 549 hardware clauses explicitly; a WCAG audit alone is not sufficient. |
| Tactile access retro-fitted | Touchscreen-only configuration approved first | Decide the accessible variant at concept stage; it changes the front panel. |
| Screen reader works, but the journey does not | Software audited in isolation from the hardware timeout/reset behaviour | Test the full task end-to-end in the accessible configuration, on the real cabinet. |
| Legacy fleet assumed exempt forever | Transition relief mistaken for permanent exemption | Track commissioning date, economic life and the national transition limit; assess replacement under the applicable rules. |
| Accessibility added to one region only | Separate EU and US specs diverge | Maintain separate applicability and conformance matrices for each deployment market. |
How this maps to the hardware
Usingwin builds self-service kiosks as OEM/ODM enclosures — the accessible configuration is part of the project specification, confirmed per configuration rather than assumed. Formats commonly specified for accessible public-facing deployments include:
- US-K320FS-2 — 32 in freestanding cabinet used for hotel & hospitality check-in (lead time 20–25 business days)
- US-K236FS-2 and US-K236 — curved-screen counter/multi-mount formats for food & beverage and retail (15–25 business days)
- US-K215FS-1 — 21.5 in floor/desktop dual-mount (lead time 15 business days)
- US-K320WM — 32 in wall-mount for retail (15–20 business days)
- US-K101CB-1 / US-K101CB-2 — 10.1 in cash-handling units for counter-top payment and change
- US-K236CB-2 — currency exchange cabinet for banking/finance and travel
MOQ 1 unit on standard formats — a single accessible evaluation unit can be built before a fleet order. Enclosure dimensions, mounting, keypad, audio and peripheral scope are confirmed per project configuration.
→ Request a quote, an accessible-configuration sample, or an accessibility test plan through our contact page , or start from the OEM/ODM project brief . Tell us the market (EU / US) and the task the kiosk must complete and we will return a configuration proposal with the accessibility options called out as separate line items.
Frequently asked questions
Is a self-service kiosk covered by the European Accessibility Act?
Coverage depends on terminal type and service scope. For existing terminals, check the national transition and commissioning date; do not assume one 2045 deadline or an automatic rule for every software update.
Does EN 301 549 mean WCAG 2.1 AA is enough for a kiosk?
No. WCAG 2.1 AA, adopted via the software clauses, covers the on-screen interface only. EN 301 549 additionally imposes hardware requirements — reach ranges, tactile controls, adjustable speech output and hearing-aid coupling — that a WCAG audit does not test. A kiosk needs both layers verified.
What is the difference between the EAA and the ADA for kiosks?
The EAA, ADA and Section 508 have different legal scopes and evidence requirements. Shared engineering work can help, but one EN 301 549 or WCAG report is not a guarantee that all three are satisfied.
What documents should an EAA self-service kiosk supplier provide?
At minimum: an EN 301 549 test report covering hardware and software clauses, an ACR/VPAT against WCAG 2.1 AA, an accessible-configuration bill of materials, a written assisted-service fallback, and an accessibility feedback contact. Where product-scope obligations apply, confirm the CE-marking route and required evidence with the responsible compliance adviser.
Do small companies have to comply?
Check the statutory microenterprise definition and the national implementing law. Service-provider exemptions and product obligations are different questions; company size alone should not be used to approve a kiosk configuration.
Can accessibility be added to a kiosk after it is built?
Partly, and expensively. Software-level fixes (contrast, focus order, timeout handling) are usually feasible. Hardware-level items — tactile controls, speech output, headphone provision and screen height — change the front panel, keypad and audio module, so they should be decided before tooling.
