Medical Device Accessibility: ADA, Section 508, and EU Accessibility Act Guide

Accessibility Now Reaches the Digital Surface of Medical Devices

Medical device regulations — the EU MDR, the FDA Quality Management System Regulation (QMSR), 21 CFR Part 820 — do not, by themselves, impose accessibility requirements. But the digital surface of a modern device almost always does trigger an accessibility law somewhere. A patient app that runs on a smartphone, an e-commerce store that sells devices to consumers, an infusion-pump touchscreen used by a nurse with low vision, or an electronic Instructions for Use (eIFU) can each bring a device within reach of the EU Accessibility Act (EAA), the Americans with Disabilities Act (ADA), or Section 508.

For medtech manufacturers, accessibility has shifted from a "nice to have" usability goal to a concrete compliance surface with enforcement dates that have already passed. The EU Accessibility Act (Directive (EU) 2019/882) has been enforceable across all 27 Member States since 28 June 2025. The U.S. Department of Justice's ADA Title II web and mobile-app rule, published 24 April 2024, set WCAG 2.1 Level AA as the technical standard for state and local government digital services, with compliance dates in 2027–2028. Germany's Digital Health Applications (DiGA) program already requires accessibility as a condition of reimbursement.

This guide explains which accessibility laws apply to medical devices and their digital components, where the medical-device carve-outs are, what WCAG 2.1 AA and EN 301 549 require in practice, how accessibility interacts with device usability engineering, and what manufacturers should do now.

The Core Standard: WCAG, EN 301 549, and Section 508

Across the U.S. and the EU, accessibility law converges on the Web Content Accessibility Guidelines (WCAG), developed by the W3C. The differences are in scope, version, and legal status — not in the underlying technical bar.

The POUR principles

All of these standards rest on the same four principles, often summarized as POUR:

• Perceivable — information and interface components must be presentable in ways users can perceive (text alternatives, captions, contrast)
• Operable — interface components and navigation must be operable (keyboard access, no seizure-inducing content, enough time)
• Understandable — content and operation must be understandable (readable, predictable, input-error tolerant)
• Robust — content must be robust enough to work with assistive technologies (screen readers, switches) — interoperability with current and future tools

For a medical device interface, "robustness" usually means the screen reader, voice-control, and switch-access pathways that an operating system provides must still reach the device's controls.

The WCAG criteria that matter most for device interfaces

WCAG 2.1 Level AA contains the 38 Level AA success criteria carried over from 2.0 plus 12 added in 2.1 (50 at Level AA); WCAG 2.2 adds 9 new success criteria and removes one obsolete Level A criterion (4.1.1 Parsing), bringing the all-levels total to 86. The 2.1 and 2.2 additions target low vision, cognitive/learning, and motor disabilities. A handful of AA criteria drive most of the defects found in patient apps and device screens:

Designing to these criteria resolves the majority of accessibility findings before testing begins, and most are also classic usability-engineering risks under IEC 62366-1.

EU Accessibility Act (Directive (EU) 2019/882)

The European Accessibility Act is the law that most directly reshapes medtech accessibility in Europe. It establishes harmonized accessibility requirements for specified products and services across the EU, replacing a patchwork of national rules with a single market framework.

Key dates

The critical nuance for medical devices

Medical devices are not listed as an in-scope product category under the EAA. But accessibility obligations still reach them through several well-established paths:

In short: the device itself is usually outside the EAA, but the patient's route to access it — the phone it runs on, the web store it is bought through, the app's sign-up flow — is pulled inside. As Member-State guidance has emphasized, it is the access route into the medical or healthcare app that triggers EAA obligations, not the clinical core of the app.

Penalties by Member State

Each Member State sets its own enforcement regime, and penalties vary widely:

Only microenterprises (fewer than 10 employees and under €2 million turnover) have a limited exemption — and most device manufacturers exceed that threshold, so the exemption rarely applies.

The German DiGA precedent

Germany's Digital Health Applications (DiGA) program — apps reimbursed on prescription by statutory health insurance — already requires accessibility as a condition of listing under the DiGA ordinance (Digitale-Gesundheitsanwendungen-Verordnung, DiGAV). For any medtech company building prescription digital therapeutics or SaMD for the German market, accessibility is not optional: it is a gating requirement for reimbursement.

United States: ADA and Section 508

ADA Title II — the April 2024 web and mobile-app rule

On 24 April 2024, the DOJ published a final rule updating Title II of the ADA to require that the web content and mobile apps of state and local government entities conform to WCAG 2.1 Level AA. Compliance dates, extended by an April 2026 Interim Final Rule, depend on population size:

Title II matters to medtech because public hospitals, county health systems, state clinics, public-health departments, and academic medical centers operated by public universities are covered. If your device's software or patient portal is deployed in those settings, the deploying entity's Title II obligation flows through to the product. Device manufacturers selling into public healthcare systems increasingly face contractual accessibility requirements as buyers build WCAG 2.1 AA into procurement.

ADA Title III — places of public accommodation

ADA Title III covers private entities open to the public, including private hospitals, clinics, and pharmacies. The DOJ has not yet issued a Title III web/mobile technical rule comparable to the Title II rule, but courts and the DOJ have treated inaccessible patient-facing digital services as potential Title III barriers. For patient-facing apps, patient portals, and telehealth surfaces deployed by private providers, WCAG 2.1 AA is the de facto expectation.

Section 508 — federal accessibility

Section 508 (29 U.S.C. § 794d), refreshed in 2018, requires federal agencies' information and communication technology — including ICT they procure — to conform to WCAG 2.0 AA. Medical software used by federal employees, by veterans through the VA, or by the public in federally conducted programs must be accessible. For medtech vendors selling to the VA, DoD, or other federal health systems, Section 508 conformance is a procurement gate: buyers verify accessibility in their market research and contract terms.

The standards line up

For practical purposes, designing to WCAG 2.1 Level AA satisfies the technical bar across ADA Title II, the EAA (via EN 301 549), and — with minor additions — Section 508. EN 301 549 adds hardware and document considerations on top of WCAG, so products with physical interfaces or downloadable eIFUs should be tested against EN 301 549 directly for the EU market.

Where Accessibility Lives in a Medical Device

Accessibility is not one requirement applied to one artifact. It is a set of requirements distributed across the device's digital and physical surface:

Accessibility and Device Usability Engineering

Accessibility overlaps with — but is not identical to — the usability engineering that medical devices already perform under IEC 62366-1 and, in the U.S., the FDA's human factors guidance and ANSI/AAMI HE75. Usability engineering proves the device can be used safely by the intended users under the intended use conditions; accessibility ensures it can be used by people with disabilities.

The two disciplines reinforce each other:

• A device whose interface fails for users with low vision, limited dexterity, or color-vision deficiency is also a use-error risk under IEC 62366-1 — those populations may be among the intended users
• Use-error data captured in summative usability testing should include participants with relevant disabilities where they are part of the intended user population
• Accessibility defects (e.g., color-only status indication, time-limited input without extension) are frequently also usability defects that contribute to use-related risk

Manufacturers that integrate accessibility into usability engineering avoid duplicative testing and produce a more defensible design-history file.

Practical Compliance Steps

Common Pitfalls

Frequently Asked Questions

Does the EU Accessibility Act apply to medical devices directly?

No — medical devices are not an in-scope product category under the EAA. But accessibility obligations reach them indirectly where device software runs on covered hardware (smartphones, tablets, computers), where an e-commerce service sells devices to consumers, or where a healthcare app's account-registration and onboarding functions constitute a consumer contract. Germany's DiGA program additionally requires accessibility for reimbursed digital health apps.

What technical standard should a medical device app target?

WCAG 2.1 Level AA is the convergent bar — it satisfies the ADA Title II rule, the EAA (through EN 301 549), and is close to Section 508's WCAG 2.0 AA. For the EU, also test against EN 301 549 directly because it extends beyond web content to hardware, documents, and two-way communication. Some buyers now ask for WCAG 2.2 AA.

When did the EU Accessibility Act become enforceable?

Enforcement began on 28 June 2025 across all 27 EU Member States, each of which transposed the directive into national law by 28 June 2022. Certain self-service terminals have until 28 June 2030.

What are the ADA Title II compliance dates for digital accessibility?

Under the DOJ's April 2024 final rule, as extended by the April 2026 Interim Final Rule, state and local government entities serving 50,000 or more people must conform to WCAG 2.1 Level AA by 26 April 2027; smaller entities and special-district governments have until 26 April 2028. The rule flows through to device software deployed in covered public healthcare systems.

Is there a medical-device-specific FDA accessibility regulation?

There is no standalone FDA device accessibility regulation. Accessibility for U.S. medical devices comes through the ADA (Titles II and III), Section 508 (for federal ICT), and HHS Section 508 implementation — applied to the digital and ICT components of the device rather than the clinical core. Accessibility also overlaps with FDA human factors and IEC 62366-1 usability engineering.

What is a VPAT and do medical device companies need one?

A Voluntary Product Accessibility Template (VPAT) documents a product's conformance with Section 508, WCAG, and EN 301 549, producing an Accessibility Conformance Report (ACR). Federal agencies and many public-sector and enterprise buyers require a VPAT during procurement. Medtech vendors selling software to the VA, DoD, or public health systems should expect to provide one.

How does accessibility relate to IEC 62366-1 usability engineering?

They overlap and reinforce each other. IEC 62366-1 proves the device can be used safely by intended users; accessibility ensures it can be used by users with disabilities. Many accessibility defects (color-only status, time pressure, low contrast) are also use-error risks. Including users with relevant disabilities in summative usability testing serves both purposes.

Are automated accessibility scanners enough?

No. Automated tools typically identify only about 30–40% of accessibility barriers. WCAG and EN 301 549 conformance requires manual testing with assistive technologies — screen readers, keyboard-only navigation, switch access — across real user workflows.

Sources

• Directive (EU) 2019/882 of the European Parliament and of the Council (European Accessibility Act)
• EN 301 549 (ETSI) — Harmonized European Standard on accessibility requirements for ICT products and services; incorporates WCAG 2.1 Level AA
• W3C Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2
• U.S. Department of Justice, "Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities" (ADA Title II final rule), Federal Register, 24 April 2024; and April 2026 Interim Final Rule extending compliance dates to 26 April 2027 / 26 April 2028
• Section 508 of the Rehabilitation Act, 29 U.S.C. § 794d (as refreshed in 2018 to reference WCAG 2.0 AA)
• Baker McKenzie, "Germany: Are medical devices affected by the German Accessibility Strengthening Act implementing the European Accessibility Act (Directive (EU) 2019/882)?" (June 2025) — analysis of the medical-device carve-out and the access-route principle
• BfArM, Digital Health Applications (DiGA) and the DiGAV accessibility requirements for reimbursed digital health apps in Germany
• IEC 62366-1 (usability engineering) and ANSI/AAMI HE75, in relation to accessibility and use error