The Accessible Chat Playbook: EAA Compliance That Also Sells More

One exemption matters for small stores. Microenterprises that provide services are exempt: fewer than 10 employees and an annual turnover or balance sheet total of no more than 2 million euro. Both conditions must hold. If you have 12 staff, or 6 staff and turnover above the cap, you are in scope. And even exempt stores should read on, because the fixes below convert better for every visitor, not just the ones the law names.

Who the EAA actually covers, in plain terms

The directive names e-commerce services explicitly, alongside banking, ticketing, transport booking and streaming. If your store sells to EU consumers and you are not a microenterprise, your whole buying journey is in scope, and the chat widget is part of that journey. It is not a side feature you can leave out of the audit. A shopper who cannot complete a purchase because the chat popup stole keyboard focus, or because the bot’s error message was never announced, has hit an accessibility barrier in your checkout flow, even if your product pages are perfect.

The same logic applies to the tools around the widget. GDPR-compliant chat already taught EU stores that the widget collects personal data and needs consent handling; accessibility adds a second duty on top of the first. Consent banners, privacy notices and chat transcripts all need to work for assistive technology too. Treat the widget as part of the store, not as a third-party island, and the audit gets much simpler.

The 30-minute chat accessibility audit

You do not need an agency to find the worst problems. Put your mouse aside and run this audit yourself before you spend anything.

Step 1 – Tab through the whole journey

Open your store, press Tab, and try to reach the chat button, open the widget, answer the first bot question, close the widget and continue to checkout, using only the keyboard. Watch for three failures: focus disappearing into the page behind the open widget, focus order jumping randomly, and no visible focus outline on buttons and links. A keyboard trap, where you can enter the widget but cannot Tab out of it, is the single most common chat failure and the easiest to feel.

Step 2 – Listen to it with a screen reader

Turn on VoiceOver or NVDA, both free, and open the widget. Every button should announce what it does: “Open chat”, “Send message”, “Close chat”, not “button” three times. New bot messages should be announced as they arrive, and the visitor should hear when the bot is typing. If your widget injects messages silently, a blind shopper is talking into a void and has no way to know the bot replied.

Step 3 – Check labels, contrast and errors

Every input needs a real label, not placeholder text that vanishes when you type. Text and icons need enough contrast against their background to pass WCAG AA, which means a contrast ratio of at least 4.5 to 1 for normal text. And error messages must be announced and explained in words: “Enter a valid email address” helps; a red border alone helps nobody, and a shopper who cannot see the border will submit the same broken form forever. The same discipline that makes conversational forms reduce abandonment by asking one question at a time also makes them more accessible: one labelled question, one clear error, one way forward.

Step 4 – Test the edges: time limits, motion and language

Timed chat features, like a popup that auto-closes or a session that expires mid-conversation, must warn the visitor and offer more time. Auto-playing animations and flashing elements inside the widget should be avoidable. And remember that accessibility includes language: serving shoppers in their own language matters just as much for a screen reader user, whose software pronounces text according to the page language you declare. A widget that answers a Dutch shopper in English with a Dutch language tag will sound like gibberish through a screen reader.

What to fix first, in order of impact

Fix keyboard traps and missing focus indicators before anything else, because they block the entire journey rather than degrading it. Next, add real labels and accessible names to every control, and make new messages announce themselves. Then fix contrast and error handling. After that, audit the flows that sit behind the widget: if your bot hands a shopper to a booking form, a configurator or a checkout step, that destination must be accessible too, or the accessible chat just delivers people to an inaccessible door.

When you evaluate vendors, ask the questions your audit just taught you. Can the widget be fully operated by keyboard? Are controls labelled for screen readers? Does it respect the visitor’s reduced-motion setting? A provider that answers with a demo instead of documentation is telling you something. The same vendor discipline applies when you migrate chat platforms: accessibility acceptance tests belong in the migration checklist next to data import and bot training, not discovered by customers after launch.

One more fix pays for itself on mobile. Mobile chat is where most EU shoppers will meet your widget, and small touch targets, overlapping popups and unreadable text are accessibility failures that also hurt every other mobile visitor. Fixing tap targets and spacing for accessibility is the same work as fixing mobile conversion.

Publish an accessibility statement and keep it honest

In-scope services are expected to publish an accessibility statement describing the conformity status of the service, known limitations and how to report a problem. Write it in plain language, name the parts of the journey you know are imperfect, and give a real contact route for feedback. A statement that claims perfection while the chat traps keyboards is worse than an honest one, because it turns a fixable gap into a credibility problem. Review the statement after every major store change, and after every widget update, since a vendor update can quietly undo your fixes.

Why accessible chat sells more, not just complies more

Here is the part founders miss when they treat the EAA as a tax. Every fix in this playbook helps visitors who never touch assistive technology. Visible focus indicators help anyone navigating on a laptop trackpad. Clear error messages help every shopper who mistypes an email. One question at a time helps every visitor on a small phone screen. And the shoppers the law protects are not a niche: they are customers with money, loyalty and long memories about which stores respected them. A store whose chat works for everyone is simply a store whose chat works, and that is a conversion advantage no discount can buy.

Frequently asked questions