European Accessibility Act and customer service: what support teams need to know

Directive (EU) 2019/882, known as the European Accessibility Act or EAA, sets accessibility requirements for a list of products in Article 2(1) and a list of services in Article 2(2). This page focuses on services, because that's where customer support sits. Article 2(2) applies to the following services provided to consumers after 28 June 2025.

The directive defines e-commerce services as services provided at a distance, through websites and mobile device-based services, by electronic means and at the individual request of a consumer with a view to concluding a consumer contract. The directive's recitals add that the e-commerce obligations cover the online sale of any product or service. The third column in the table is a checklist suggestion, not a statement of what the law requires of your business.

The EAA is a directive, so it reaches businesses through national laws. Article 31 required Member States to adopt and publish those laws by 28 June 2022 and to apply them from 28 June 2025. Article 32 adds some transitional periods.

Because each Member State writes its own law, the national texts and the authorities that enforce them differ between countries. The Commission says it monitors the complete and correct transposition of the Act. If you serve customers in several EU countries, check the national law in each one.

Article 3(23) defines a microenterprise as an enterprise that employs fewer than 10 persons and has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million. Under Article 4(5), microenterprises providing services are exempt from the accessibility requirements in Article 4(3) and from the obligations relating to compliance with them. The recitals explain that asking these businesses to carry out an assessment would itself be a disproportionate burden. The directive still encourages microenterprises to provide services that meet the requirements.

The exemption covers services only. Microenterprises that deal in products are treated differently and are not fully exempt.

For everyone else, Article 14 says the accessibility requirements apply only to the extent that compliance doesn't require a significant change that fundamentally alters the basic nature of the service, and doesn't impose a disproportionate burden. A business that relies on this has to make an assessment using the criteria in Annex VI. Service providers must renew it when the service is altered, when an authority asks, and at least every five years. The recitals add that lack of priority, time or knowledge should not be considered legitimate reasons.

Article 4(3) says all services, except urban and suburban transport services and regional transport services, must comply with Section III of Annex I, which sets general accessibility requirements for services. Section IV adds requirements for specific services, such as consumer banking and e-commerce. Three points in Section III matter most for support teams:

• Point (a): the products used to provide the service must be accessible.
• Point (c): websites, including related online applications, and mobile device-based services, including mobile apps, must be made accessible in a consistent and adequate way by making them perceivable, operable, understandable and robust.
• Point (d): where available, support services (help desks, call centres, technical support, relay services and training services) must provide information on the accessibility of the service and its compatibility with assistive technologies, in accessible modes of communication.

Article 13 adds a transparency duty. Service providers prepare information, following Annex V, that explains how the service meets the accessibility requirements, and make it available to the public in written and oral format, including in a way that is accessible to persons with disabilities. AccessibleEU's guidance adds that this information must be kept for as long as the service is in operation.

A chat widget or support bot that runs on your website or app is part of the interface customers use, so it makes sense to hold it to the same perceivable, operable, understandable and robust test. Your help desk, staffed by people or bots, should also be ready to answer questions about the accessibility of your service.

The directive doesn't list technical checks for a chat widget. The points below are common engineering practice that maps to the Annex I principles. Test them with real assistive technology, such as screen readers and keyboard-only use.

• Make the chat launcher, message field, buttons and quick replies usable with a keyboard alone, with a visible focus indicator.
• Give every control a text label that screen readers announce, and announce new messages without moving the user's focus.
• Don't rely on colour, icons or images alone to carry meaning. Give images and cards text alternatives.
• Avoid short inactivity timeouts that close the chat, or warn before closing and let the customer continue.
• Keep bot replies short and plain, and give customers an easy way to reach a person, with the conversation history passed along.
• Teach the bot and your agents to answer questions about your service's accessibility and to point to your Article 13 information.
• Offer more than one contact channel, such as chat and email, and give voice bot callers a text-based alternative.

For technical detail, look at EN 301 549, the European standard on accessibility requirements for ICT products and services. Commission Implementing Decision (EU) 2021/1339 references EN 301 549 V3.2.1 as a harmonised standard under the Web Accessibility Directive, which covers public sector websites and apps. ETSI adopted EN 301 549 V4.1.1 on 24 August 2026. It moves to WCAG 2.2 and adds an annex that maps its requirements to the EAA. AccessibleEU says V4.1.1 is not yet the legal reference for showing compliance with the EAA or the Web Accessibility Directive, and that the reference remains V3.2.1, based on WCAG 2.1 level AA, until the Commission cites V4.1.1 in the Official Journal.

TascaLab builds chat and voice bots on top of the tools you already use, such as Zendesk, Freshdesk, Jira and Slack. Standard Chat Bot projects cost $575 and Voice Bot projects $1,350. Both include basic documentation and 30 days of post-launch support. You can start with a free 30-minute Health Check call.