European Accessibility Act and Live Chat Checklist

The European Accessibility Act and live chat meet on any website that sells to consumers in the EU. Since 28 June 2025, many online shops, banking and communication services have had to make their digital services accessible to people with disabilities, and a chat widget is part of that service. If your chat cannot be used with a keyboard, a screen reader or at high zoom, it can become an accessibility problem in the same way a broken checkout would. This guide explains in plain language what the Act covers, whether your business is affected, what to check in a chat widget, how to write the human fallback and what to ask your chat vendor. It is general information, not legal advice.

Talkmio is an AI live chat for websites. Its assistant, Mio, answers from your own content in the visitor’s language and hands the conversation to your team when it cannot answer or when the visitor asks for a person. Those two facts matter for accessibility, because a quick route to a human is one of the most useful accommodations you can offer.

What the European Accessibility Act Is

The European Accessibility Act is Directive (EU) 2019/882. It sets common accessibility requirements for selected products and services so that people with disabilities, and older people, can use them on equal terms across the EU. The overview of the Act lists the background. Each member state turned the Directive into national law, with its own authorities, enforcement and detail, so the exact rules and penalties depend on the country in which you operate or sell.

For website owners, the relevant part is that the Act applies to certain consumer-facing services. These include e-commerce services, consumer banking services, electronic communications services, audiovisual media services and some transport services. A website or app through which you sell to consumers is in scope. Micro-enterprises that provide services, generally those with fewer than ten people and a small turnover or balance sheet, are exempt from the service requirements, but the exact thresholds and national conditions should be checked locally.

European Accessibility Act Live Chat: Does It Apply to You?

The Act does not name chat widgets. It regulates the service, such as an online shop, and the chat is part of how the service is delivered. If a customer uses the chat to ask about an order, to get help with checkout or to contact support, an inaccessible chat can block a legitimate use of the service. That is why many compliance checklists include customer support channels.

Situation	Likely position
Online shop selling to consumers in the EU	In scope; the chat is part of the service
Online bank or payment service for consumers	In scope
Business-to-business software only	Usually outside the Act, but other duties or customer contracts may require accessibility
Micro-enterprise providing a service	Generally exempt from service requirements; confirm locally
Marketing site with no sales to consumers	Usually outside the Act; accessibility is still good practice

If you are unsure, ask your national authority or a lawyer, and treat accessibility as a quality goal either way. Many of the changes help everyone: clear contrast, keyboard use and plain wording make a chat easier on a phone in sunlight as well as for a person with low vision.

The Standard Behind the Requirements: WCAG 2.1 AA

The Act sets requirements in broad terms, and the technical benchmark most often used for websites and apps is the harmonised European standard EN 301 549, which in turn points to the Web Content Accessibility Guidelines. In practice, aiming for WCAG 2.1 level AA is the common target. You can read the full text of WCAG 2.1 on the W3C website. The guidelines are organised under four principles: content must be perceivable, operable, understandable and robust.

A chat widget touches many of the success criteria. The next section turns them into a checklist you can run on your own site in an afternoon.

An Accessibility Checklist for a Chat Widget

Perceivable

Contrast: text and the chat button must meet the minimum contrast ratio against their background. Check the widget colour you choose against your page.
Text size and zoom: the chat window must remain usable when the page is zoomed to 200 percent and on a small screen.
Alternatives for images: icons that carry meaning, such as the chat bubble, need an accessible name.

Operable

Keyboard: a person must be able to open, use and close the chat with the keyboard alone, and focus must be visible and move in a logical order.
No keyboard traps: focus must be able to leave the chat window.
Target size and placement: the button must be easy to hit and must not hide important controls, such as a checkout button.
Timing: avoid closing a conversation or taking away a message while someone is still typing.

Understandable

Plain language: short sentences, common words and one idea per message.
Predictable behaviour: no pop-ups that open suddenly and cover the page.
Error help: if a field fails, say what is wrong and how to fix it.

Robust

Screen readers: new messages should be announced, and the roles and names of buttons and fields should be exposed to assistive technology.
Different browsers and devices: test on at least two browsers and one phone.

For a deeper look at the same ground from a design view, read our guide on live chat widget accessibility, and for phones in particular the article on mobile live chat widget UX. Always test with real assistive tools: a screen reader, keyboard only and a zoomed page. An automated scanner finds only part of the problems.

What You Control, and What the Vendor Controls

Accessibility of a chat has two layers. The vendor controls the widget code: its structure, keyboard handling, focus order and what a screen reader hears. You control everything around it: the colour you choose, the position, the welcome text, the wording of answers, the knowledge base and whether a person is easy to reach. In Talkmio, under Websites you can set the widget colour, position, assistant name, welcome and offline texts and language, and changes apply within five minutes. Use that to choose a high-contrast colour, a position that does not cover buttons and plain wording.

Do not assume that any vendor is conformant, including us. Ask the vendor for its accessibility information or test report, and run your own checks on your own site, because a widget can behave differently in your page. If you find a problem in the widget itself, report it to the vendor with steps, browser and assistive technology, and record the date. A written note that you tested, found an issue and reported it is better evidence of good faith than silence.

Write the Human Fallback

The most reliable accommodation is an alternative way to reach you. Some visitors cannot use a chat at all, and that is acceptable under the Act when you offer an equivalent route. Make sure your contact page lists an e-mail address and, where you offer it, a phone number with hours. State them near the chat so a visitor who gets stuck can see them. Mio hands the conversation to your team when the visitor asks for a person, and it should not make anyone argue for it, so add a line to the welcome text such as “Prefer to speak to a person? Just say so.”

When the team is offline, Talkmio asks visitors for an e-mail before their first message, and your reply goes out as an e-mail. Write the offline text in plain words and give a realistic reply time. For visitors who use assistive technology, a predictable e-mail reply is often easier than a live conversation with a time limit. The Inbox also lets you add internal notes, visible only to your team, so a customer’s stated preference can be recorded and respected next time. The guide to live chat for e-commerce stores covers how to place the chat on shop pages without blocking key actions.

Content and Conversation: Accessibility Beyond the Widget

An accessible widget can still deliver an inaccessible experience if the answers are written badly. Long paragraphs, jargon, tables pasted as images and instructions such as “click the green button” do not help someone who uses a screen reader or has a cognitive disability. Mio answers from your content, so the cheapest improvement is to fix the source: use headings, short sentences, descriptive link text and real text instead of text in images. Then add a business instruction that asks for short answers, one step at a time, with numbered steps for processes.

Think about timing too. Some people take longer to read and type, so do not use messages that disappear, and do not close a conversation after a few minutes of silence. Tell the team to be patient and to avoid pressure phrases. Our reasoning for the wider European approach is the same as for the Act itself: services should work for the people who need them, whatever their abilities. A short test with a real user who relies on assistive technology teaches more than any checklist, and many organisations of disabled people will advise on testing if you ask.

Finally, remember mixed needs. A person may use a screen reader and also write in a second language; Mio replies in the visitor’s language, and the chat window is translated, but you should test those combinations rather than assume. A European Accessibility Act live chat review is not a one-off job; repeat it whenever you change your theme, your widget settings or your main layout, since each change can break something that worked yesterday.

Document What You Did

An accessibility statement is expected for services in scope in many countries. It normally says which standard you aim for, what you have tested, known limitations, how to contact you with a problem and how to complain to the authority. Include the chat in the statement, with an honest note of any known limits and the alternatives you provide. Keep a dated record of tests, fixes and vendor communication.

The chat’s AI also comes under a second set of rules: the EU AI Act and chatbots, mainly the duty to tell people when they are talking to an AI. The two fit together, because clear labelling is also good accessibility. Plans and limits are on the Talkmio pricing page.

A One-Afternoon Plan

Decide whether your service is in scope and note the national authority for your country.
Test the chat with keyboard only, a screen reader and a page zoomed to 200 percent.
Check the colour contrast of the widget against your page and fix it in the widget settings.
Rewrite the welcome and offline text in plain language, and add the line about speaking to a person.
Publish clear alternatives: e-mail, phone where offered, and hours.
Write or update the accessibility statement, and set a date to repeat the tests.

Frequently Asked Questions

Does the European Accessibility Act apply to live chat?

The Act regulates services, such as online shops and consumer banking, and a chat widget is part of delivering that service. If your service is in scope, an inaccessible chat can create a problem, so test it and offer an alternative way to reach you.

Which standard should my chat meet?

Most organisations aim for WCAG 2.1 level AA, which the European standard EN 301 549 builds on. That means checking contrast, keyboard use, focus, zoom and screen reader support, and testing with real assistive tools rather than relying only on an automated scan.

Are small businesses exempt?

Micro-enterprises providing services, generally with fewer than ten people and a small turnover or balance sheet, are exempt from the service requirements. Thresholds and conditions are set nationally, so check your own country’s rules or ask the authority before you rely on the exemption.

Can an AI assistant be part of an accessible service?

Yes, if the widget works with assistive technology, the wording is plain and a person is easy to reach. Mio hands over when a visitor asks for a person, and you can add a welcome line making that clear. Test the full experience, not only the widget.

What should I ask my chat vendor?

Ask for accessibility information or a test report, which standard it targets, how issues are reported and fixed, and whether keyboard and screen reader use have been tested. Then run your own checks on your own site, because behaviour depends on your page too.

Is this legal advice?

No. This article is general information only. The rules differ between member states, so check your national law and speak to a qualified adviser about your own situation, especially if you sell to consumers in several countries or run a regulated service.

The Bottom Line

The European Accessibility Act and live chat belong together wherever you sell to consumers in the EU. Test the widget with keyboard, screen reader and zoom, choose a high-contrast colour, write plain text, keep a human route open and record what you did in an accessibility statement. Ask your vendor for evidence and check it yourself. Start free with Talkmio, set a readable colour and a clear line about speaking to a person, and run your first accessibility test on your own page.

European Accessibility Act Live Chat: What Site Owners Must Check