A chat widget sits on top of your page, takes input, shows moving text and sometimes pops up uninvited. For visitors who use a keyboard, a screen reader or magnification, that can be a smooth experience or a wall. Chatbot accessibility is not a niche concern: it affects how many people can reach you, and it is straightforward to check. This guide gives a practical checklist and tests you can run without special tools. It is a starting point, not a legal audit.
Why It Matters
Accessibility guidelines are published by the World Wide Web Consortium as the Web Content Accessibility Guidelines (WCAG). They set out what makes web content usable by people with a wide range of needs, including people who cannot use a mouse, who rely on a screen reader, who have low vision or who are colour blind. Many organisations aim for the "AA" level of WCAG 2.2. Whether the guidelines are legally required for your business depends on where you operate, so check with a qualified adviser if that matters to you.
Apart from any legal angle, accessible design tends to be good design for everyone. Clear contrast, large tap targets and keyboard support help people on phones, in bright sunlight or with a sore wrist.
The Checklist
An accessible chat widget works by keyboard, shows focus, has readable contrast, announces new messages, survives zoom, has large tap targets, avoids surprises and has an alternative contact route.
1. Can You Use It With a Keyboard Only?
WCAG success criterion 2.1.1 says everything that works with a mouse should work with a keyboard. For a chat widget that means:
- You can reach the chat button by pressing Tab.
- Enter or Space opens it.
- You can move to the message box, type and send without a mouse.
- You can close the widget with Escape or a clearly focusable close button.
- Focus never gets stuck inside the widget. Criterion 2.1.2 (no keyboard trap) covers this.
Quick test: put your mouse aside and try to start and end a chat using only the keyboard.
2. Can You See Where You Are?
When someone tabs through the page, a visible outline or highlight should show which control has focus. If the widget hides that outline, keyboard users are lost. Make sure the chat button, the message box and the send button all show a clear focus indicator.
3. Is the Text Readable?
WCAG 1.4.3 asks for a contrast ratio of at least 4.5:1 between normal text and its background, with a lower threshold for large text. Check the text in your greeting bubble, starter questions, buttons and placeholders, especially if you have customised the colours to match your brand. Light grey on white and white on a pale brand colour are the usual offenders. Free contrast checkers will test any two colours in seconds.
4. Does It Work for Screen Readers?
A screen reader announces text and controls aloud. Chat is tricky because new messages appear without the page reloading. WCAG 4.1.3 (status messages) says important updates should be announced without moving the user's focus. In practice, check that:
- The chat button has a clear text label such as "Open chat", not just an icon.
- The message box has a label.
- New replies are announced when they appear.
- Buttons such as send and close have meaningful names.
Quick test: turn on the screen reader built into your computer or phone, open the chat and listen. If you cannot tell what is happening, a visitor who relies on one cannot either.
5. Can People Enlarge the Text?
Zoom the browser to 200 per cent and use a narrow phone-sized window. The widget should still be readable, should not cover the whole page without a way to close it and should not cut text off. Pinch-zoom on a phone should not be disabled.
6. Are the Tap Targets Big Enough?
Small buttons are hard for people with limited dexterity and for anyone on a moving bus. WCAG 2.2 added a minimum target size criterion (2.5.8), and bigger is generally friendlier. Make sure the close button, send button and starter questions have enough space around them to tap accurately.
7. Does It Avoid Surprises?
Popping up and opening itself, sudden sounds or auto-playing animation can disorient people. Let visitors open the chat when they choose, or delay any automatic prompt and make it easy to dismiss. Keep the language plain, avoid long blocks of text and write answers that are short and scannable.
8. Is There an Alternative Way to Reach You?
No chat widget works for everyone. Always provide another route, such as a phone number, an email address or a contact form, in a place that is easy to find. If the bot cannot help, the next step should not depend on the widget being usable.
A Ten-Minute Test Plan
A ten-minute test with a keyboard, 200 per cent zoom, a contrast checker, a screen reader and a phone will catch most widget problems.
- 1Use the keyboard only to open, use and close the chat.
- 2Zoom the page to 200 per cent and check nothing breaks.
- 3Run a contrast checker on the main colours.
- 4Switch on a screen reader and ask one question.
- 5Open the site on a phone and tap every button once.
- 6Check that a phone number or email is visible on the contact page.
Pro Tip: Do the test with a real person who uses assistive technology if you can. Automated checkers find some problems but miss many, and real users find the ones that matter.
Ask Your Vendor
If you use a third-party chat tool, you may not control the code. Ask the vendor how it handles keyboard use, screen readers and contrast, and whether it has tested against WCAG. Treat a clear, honest answer as a good sign. If a vendor has not tested, test it yourself using the plan above and decide whether it is good enough for your audience.
What a Business Owner Can Do This Week
A business owner can improve chat accessibility this week without writing code: run the ten-minute test, record what fails, ask the vendor about it and make sure another contact route is visible.
- Run the test and write down failures. Short, specific notes such as "close button cannot be reached by Tab" are easy for a vendor to act on.
- Send those notes to your vendor. A good vendor will tell you what is fixed, what is planned and what is not possible.
- Make the alternative route obvious. A phone number or email on the contact page helps every visitor, including those the widget cannot serve.
- Check again after updates. Accessibility can regress when a widget or your theme is updated.
Accessibility is a continuing practice, not a certificate. Be honest with visitors about what works, and fix what does not.
Related reading: where to place your chat widget and how to test a chatbot before launch.
Conclusion
An accessible chatbot works with a keyboard, shows focus, uses readable colours, announces new messages to screen readers, survives zooming, has generous tap targets, avoids surprises and sits alongside another way to contact you. You can check most of it in ten minutes with no special software. Make accessibility part of choosing and reviewing your chat widget, not an afterthought.
Key takeaways
- WCAG sets out the accessibility basics, and many organisations aim for the AA level of version 2.2.
- Test keyboard-only use, visible focus, text contrast of at least 4.5:1 and screen reader announcements.
- Check zoom to 200 per cent and make tap targets comfortable.
- Avoid surprise pop-ups and always offer another way to contact you.
- Ask your chat vendor how they test, and verify with real assistive technology.
Quick Summary
Chatbot accessibility means a chat widget that works with a keyboard only, shows visible focus, uses text with at least 4.5:1 contrast, announces new messages to screen readers, survives zooming to 200 per cent and has comfortable tap targets. Avoid surprise pop-ups and always provide another way to contact you. You can test most of this in ten minutes, and the WCAG guidelines are the reference to use.
Want to see grounded answers on your own site?
Start free, add your Q&A pairs and paste one script tag. No credit card required.

Founder & CEO
Writes about grounded AI chatbots for websites: how they work, how to measure them and what to check before you buy.
Topics
Get new posts by email
Guides on AI chatbots for websites, straight to your inbox.
