Making a website chat usable for everyone

A chat widget is a small application sitting on top of your site, which means it can quietly make your site less usable for some visitors. This guide is the honest checklist: what to test, how to test it without special equipment, and the things that are genuinely hard. It is a practical guide, not a statement of conformance to any standard.

1. The keyboard test, which takes one minute

Put the mouse down. Press Tab until focus reaches the chat button, press Enter to open it, type a message, send it, and close the chat - all without touching the mouse or the trackpad. Then check two things: that you can see where the focus is at every step, and that focus does not get stuck inside the chat with no way out. A widget that cannot be opened or closed from the keyboard is unusable for a substantial group of people, and the test is free.

2. Does a new message announce itself?

Someone using a screen reader does not see a reply appear. Unless the chat area is marked as a live region, a reply arrives in silence and the visitor sits waiting. Turn on the screen reader your own computer already has - VoiceOver on a Mac, Narrator on Windows - send a message and listen. You do not need to be fluent in it; you only need to hear whether the reply is read out at all.

3. Colour, contrast and the branding trap

Chat widgets are usually themed to match a brand, and that is where contrast goes wrong: pale grey text on white, or white text on a light brand colour. The quick version of the check is to look at the chat on a phone outdoors; if you cannot read it in daylight, neither can anybody else. Also check that nothing depends on colour alone - a status shown only by a green or red dot is invisible to a visitor who cannot distinguish them, so it needs a word as well.

4. Zoom to 200 per cent

Many people browse permanently zoomed in. Set your browser to 200 per cent and open the chat: does the text reflow, or does the panel clip it? Can you still reach the send button? This is also where a fixed-height chat panel on a small laptop screen reveals itself.

5. Motion, sound and the surprise pop-open

An animated bubble that bounces, a chat that opens itself, and a notification sound are each a problem for somebody - vestibular disorders, attention conditions, or simply a person in a quiet office. The accessible default is a static bubble that opens when a visitor decides to open it, with no sound. That is also the default that annoys the fewest ordinary visitors, so there is no trade-off to make. See where to put the chat widget.

6. Plain language is an accessibility feature

This is the part you control completely, and it is where most of the benefit is. Short sentences, one idea each, no jargon, no idioms, and the answer before the explanation. That helps a visitor with a cognitive disability, a visitor reading in their second language, a visitor on a phone in a hurry, and the assistant itself, which answers from what you wrote. If your knowledge is written in plain words, every one of those visitors is better served. See writing the way your chatbot should speak.

7. Always leave another route

The most important accessibility measure for a chatbot is that nobody is ever forced to use it. Your phone number, your e-mail address and a plain contact page must be reachable without the chat, and the chat must never be the only way to reach a person. Allinaa's assistant hands over to a person on request, and when the service is unavailable it falls back to the inquiry form - but a visible contact page is what makes that safe rather than hopeful.

What is genuinely hard, stated plainly

A chat interface is a stream of updating content inside somebody else's page, which is one of the harder things to get right for assistive technology. Allinaa's widget keeps its own styles isolated so your theme cannot break it, is operable by keyboard, and does not open itself, animate or make sounds. It has not been audited against a standard, and no conformance claim is made here - if your organisation requires a formal statement, ask for what has actually been tested rather than accepting a badge. The checks above are the ones that find real problems, and you can run all seven in twenty minutes.

Questions people ask about this

Does a chatbot make my site more accessible or less?

It can do either. A chat that answers a question in plain words without filling in a form helps some visitors a great deal. A chat that traps keyboard focus or pops open with a sound harms others. The difference is the checks above.

Is the widget a legal risk for my site?

Whether any accessibility law applies to your site is a question for your own adviser, not for a vendor page. What is in your control is running the checks, writing plainly, and keeping a non-chat route to a person.

What is the single highest-value change?

Plain language in the knowledge. It costs nothing, it is entirely yours, and it helps every group on this page at once.