Accessibility and AI transparency

Purpose

Since 2025 the German Accessibility Improvement Act (BFSG) requires many websites to make their services usable by everyone. And the EU AI Act requires that people can recognise when they are talking to an AI. dAI Pro brings both with it; this chapter shows what the widget does on its own and what you should bear in mind in your texts.

Accessibility of the chat widget

The widget is built to the criteria of WCAG 2.2 at level AA:

Keyboard: bubble, input field, send, starter questions, sources, help and close are reachable with Tab; Escape closes the panel, Enter sends.
Screen reader: all controls have labels; new answers are announced; the roles of dialog, list and headings are set.
Focus: a visible focus ring in the accent colour; on opening, the focus jumps into the input field, on closing back to the bubble.
Contrast: the default colours meet the minimum contrasts. Anyone choosing their own colours in the configurator is responsible for the contrast themselves; light accent colours on a white background are the most common mistake.
Font and zoom: the font size follows the setting in the configurator and scales with the browser zoom; at 200 per cent everything remains usable.
Motion: no animations that cannot be switched off; the widget respects the system setting for reduced motion.
Language: the widget declares its language; answers in another language are marked.

Plain language (Chapter 4) is the content contribution: visitors can request answers in short sentences without technical terms, without content or sources changing.

Transparency under the EU AI Act

Article 50 of the EU AI Act requires that people are informed when they interact with an AI system. dAI Pro implements this in three places:

Greeting: the suggestion when the configurator is first opened begins with "I am the AI assistant of …". Anyone changing the greeting should keep the note.
Help text behind the ? button: "You are talking to an AI system, not to a human." Plus which provider the question goes to, what is stored and for how long.
Attest below the chat when a processing region is set (Chapter 20).

The help text is generated from the settings of the collection and can be regenerated at any time. What you add to it yourself, for instance a note on your data protection officer, is preserved on regeneration if you append it at the end; otherwise regenerating replaces the whole text.

What you do yourself

Mention the chat in your privacy policy: provider, region, retention of the log. The details are in the help text and in the settings of the collection.
Check the colours of your embed for contrast if you deviate from the default.
Leave human handover switched on (Chapter 12). A way to a human is part of accessibility and fairness.
Keep the greeting honest: no name that pretends to be a human.

Frequently asked questions

Do I have to commission an accessibility audit? That depends on your website, not on the widget. The widget brings its conformance with it; the page around it is your responsibility.

May the assistant have a human name? Yes, as long as the greeting makes clear that an AI is answering. "Anna, the AI assistant of Musterfirma" is fine, "Anna from customer service" is not.

Does this also apply to the search? The search shows a list of results and a summary; it is not a conversation. The summary is recognisable as an AI summary.