Making a chatbot's AI disclosure accessible: what Article 50(5) asks for
What the Act says
Article 50(5) covers every disclosure in Article 50, chatbots included:
"The information referred to in paragraphs 1 to 4 shall be provided to the natural persons concerned in a clear and distinguishable manner at the latest at the time of the first interaction or exposure. The information shall conform to the applicable accessibility requirements."
"Applicable" is not defined in Article 50. Where the Act deals with accessibility for high-risk systems, Article 16(l) points to two directives: the Web Accessibility Directive (EU) 2016/2102 and the European Accessibility Act, Directive (EU) 2019/882. Reading Article 50(5) the same way, the disclosure has to meet whichever of those already applies to the website or app the chatbot sits on. That is a reading, not settled law; the Commission's guidelines may say more.
Which rules apply to whom
| Where the chatbot runs | Accessibility rule that already applies | Effect on the AI disclosure |
|---|---|---|
| Public-sector website or app | Web Accessibility Directive | Disclosure must meet the same standard as the rest of the site |
| Online shop, banking, transport ticketing or another service covered by the European Accessibility Act (applies since 28 June 2025) | European Accessibility Act | Same |
| Service run by a microenterprise (fewer than 10 staff and turnover or balance sheet of no more than EUR 2 million) | Not the European Accessibility Act: its requirements do not apply to microenterprises providing services, per Ireland's CCPC | No specific accessibility law, but the disclosure still has to be "clear and distinguishable" |
| B2B site not in a covered sector | Often none | Same as above |
National laws implementing the two directives add detail and differ by country. Germany's BFSG is one example.
For agencies, the useful point is that the disclosure is part of the chat interface. If a client's site has to meet the European Accessibility Act, an inaccessible chat widget is already a problem, and the AI line inherits that.
What an accessible disclosure looks like
The harmonised European standard for these directives is EN 301 549, whose web clauses follow WCAG 2.1 level AA. These are the WCAG success criteria a chatbot disclosure most often fails:
- Real text, not an image or icon (1.1.1). A robot icon or an "AI" badge alone is not a disclosure for a screen reader user unless it has a text alternative that says the same thing. Better: put the words in the first message.
- Announced when it appears (4.1.3, status messages). Chat messages added to the page should be announced, usually through an ARIA live region on the message list. Test that the first bot message, with the disclosure in it, is read out without the user moving focus.
- Contrast (1.4.3). Small grey "Powered by AI" text under the input box often falls below the 4.5:1 ratio for normal text. Check it with a contrast checker.
- Not colour alone (1.4.1). A different bubble colour for the bot is fine as an extra cue, but it cannot be the only thing that says "this is an AI".
- Keyboard (2.1.1). The chat opens, the disclosure can be reached and the "talk to a person" option works with the keyboard alone.
- No hover-only text. A tooltip that says "AI assistant" when you hover the avatar does not reach keyboard, touch or screen reader users.
- Language of the page (3.1.1 and 3.1.2). If the bot answers in the visitor's language, mark the language so a screen reader pronounces the disclosure correctly.
Plain wording helps everyone: "I'm an AI assistant, not a person" is easier to follow than "This conversational agent is powered by generative artificial intelligence". The disclosure wording guide has examples.
Voice and video
- Voice agents. The disclosure is spoken, so it reaches blind callers already. Deaf or hard-of-hearing users who reach the business by relay or text chat need the same line in text. The voice agent guide covers the spoken wording.
- AI avatars and video. If the disclosure is only spoken, captions must carry it (1.2.2). If it is only on screen, a screen reader user may miss it, so say it in the audio too.
A quick test before go-live
- [ ] Turn on a screen reader (VoiceOver, NVDA or TalkBack), open the chat and confirm the AI line is read out.
- [ ] Open the chat, reach the disclosure and the "person" option with the Tab key only.
- [ ] Check the contrast of the disclosure text and any "AI" label.
- [ ] Zoom to 200% and confirm the disclosure is not cut off or hidden.
- [ ] Confirm icons and badges have text alternatives that say "AI".
- [ ] For voice or video, check the transcript or captions include the disclosure.
Sources
- Regulation (EU) 2024/1689 (AI Act) on EUR-Lex: Article 16(l) and Article 50(5).
- Article 50 text and Article 16 text at artificialintelligenceact.eu.
- Directive (EU) 2019/882 (European Accessibility Act) on EUR-Lex.
- Directive (EU) 2016/2102 (Web Accessibility Directive) on EUR-Lex.
- CCPC (Ireland): European Accessibility Act guidelines for microenterprises, for the microenterprise definition and the services exemption.
- W3C: WCAG 2.1, for the success criteria named above.