Websites With Chatbots Everyone Can Use: An Accessibility Check for Your Chat (Free Contrast Checker)

Websites with chatbots promise instant help, but for some visitors the chat is the hardest part of the page to use. Pale grey text on a light bubble, a launcher you can’t reach with the keyboard, new messages a screen reader never announces, a window that breaks when someone zooms to 200%. These visitors include older customers, people with low vision, people who can’t use a mouse and anyone on a small phone in bright sunlight. This guide turns the relevant parts of the WCAG accessibility guidelines into checks you can run on your own chat in fifteen minutes, with a contrast checker for the colours you choose.

4.5:1text contrast
3:1button contrast
200%zoom test
24pxsmallest target

โšก In short

  • Accessible chat helps far more people than you think: older visitors, low vision, keyboard users, people on phones outdoors.
  • The biggest everyday failure is colour: pale text and brand-coloured bubbles that don’t meet 4.5:1.
  • Test four things yourself: colours, keyboard, zoom and a screen reader. It takes fifteen minutes.
  • Write bot messages and buttons in plain words, never colour or emoji alone.
Websites with chatbots in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

Who gets left out

Accessibility isn’t a niche concern for a chat

When owners of websites with chatbots hear “accessibility”, they often picture a small group of blind users. The real group is much bigger, and it includes many of your customers.

Older visitors. Eyesight changes with age, and many people over 50 struggle with low-contrast text. In many Indian families, parents and grandparents now shop and book appointments on their phones.

People with low vision or colour blindness. Light grey text, or green-and-red signals with no words, can be unreadable.

People who don’t use a mouse. Some use only a keyboard, a switch device or voice control. If they can’t reach the chat button with Tab, the chat doesn’t exist for them.

Screen reader users. If a new message arrives silently, they don’t know the bot replied.

Everyone, sometimes. A cracked phone screen, bright sunlight, a broken arm, a slow connection. Temporary situations make all of us less able for a while.

There is also a legal angle in some markets. The Web Content Accessibility Guidelines (WCAG) from the W3C are the standard that most accessibility laws point to, and the European Accessibility Act has applied to many online shops serving EU customers since June 2025. Whatever the rules where you trade, the business case is simpler: every visitor who can’t use your chat is a question that goes unasked.

Eight checks

What an accessible chat gets right

Each maps to a WCAG success criterion. The first four are the ones that fail most often.

๐ŸŽจ

Readable colours

Text in bubbles reaches 4.5:1 contrast against its background; the launcher reaches 3:1 against your page.

โŒจ๏ธ

Keyboard reachable

Tab reaches the launcher, Enter opens it, Tab moves through the chat, and Escape or a close button closes it.

๐Ÿ”ฒ

Visible focus

You can always see which element is selected while using the keyboard.

๐Ÿ”Š

Announced messages

New replies are announced to screen readers without moving the visitor’s focus.

๐Ÿ”

Survives zoom

At 200% zoom, and on a 320-pixel-wide screen, nothing is cut off or overlapping.

๐Ÿ‘†

Big enough targets

Buttons and the launcher are at least 24 by 24 pixels, ideally larger on phones.

โณ

No rush

The chat doesn’t close or clear itself while someone is still typing slowly.

๐Ÿ“

Plain words

Buttons say what they do. Meaning never depends on colour or emoji alone.

Free tool

Check your chat colours

The default example fails on purpose: a bright green bubble with white text and grey bot text. Enter your own colours and see what passes.

Enter the colours your chat uses. Hex codes like #0f766e work; the colour pickers are there for convenience.

Visitor bubble and launcher button

Bot or team bubble

Your page background (behind the launcher)

Uses the WCAG 2 contrast formula. Runs only in your browser.

Fifteen-minute test

Test your own chat without special software

You don’t need an accessibility audit firm to find the most common problems in websites with chatbots. You need fifteen minutes, a laptop and a phone.

Colours (3 minutes)

Find your chat’s colours in your widget settings, or pick them from a screenshot, and run them through the checker above. Fix anything that fails AA normal text. Brand greens, oranges and light blues are the usual offenders with white text.

Keyboard (4 minutes)

Put the mouse away. Press Tab repeatedly from the top of your page. Does focus eventually land on the chat launcher, with a visible outline? Does Enter open it? Can you type, send and Tab to any buttons? Can you close it again and carry on through the page? Note any point where you get stuck.

Zoom (3 minutes)

In your browser, zoom to 200%. Open the chat. Is the text bigger and still readable, and can you still see the input box and send button? Then try your phone with the largest text size setting.

Screen reader (5 minutes)

Windows has the free NVDA screen reader; Macs and iPhones have VoiceOver built in; Android phones have TalkBack. Turn one on, open the chat and send a message. Do you hear the bot’s reply when it arrives? Are buttons read with sensible names, or as “button, button”?

Write down every failure. Some you can fix yourself in settings and wording; others need your chat provider.

The guidelines

WCAG criteria that matter most for a chat

Level AA is the common target in accessibility laws and policies.

CriterionWhat it means in a chatQuick test
1.4.3 Contrast (Minimum), AABubble and input text at least 4.5:1Checker above
1.4.11 Non-text Contrast, AALauncher and borders at least 3:1 against the pageChecker above
2.1.1 Keyboard, AOpen, use and close the chat without a mouseTab, Enter, Escape
2.4.7 Focus Visible, AAA visible outline on the focused controlWatch while tabbing
4.1.3 Status Messages, AANew messages announced without moving focusScreen reader
1.4.10 Reflow, AAWorks at 320 CSS pixels wide without sideways scrollingPhone or 400% zoom
2.5.8 Target Size (Minimum), AA (WCAG 2.2)Clickable targets at least 24 by 24 CSS pixelsMeasure on phone
2.2.1 Timing Adjustable, ANo timeouts that end a chat mid-typingType slowly

Common failures

Five accessibility mistakes and their fixes

These turn up again and again when websites with chatbots are tested with a keyboard and a screen reader.

Brand colour chosen for looks only
๐Ÿšฉ FailsA bright brand green or orange bubble with white text, around 2:1 to 3:1 contrast.
โœ… FixDarken the bubble shade until white text reaches 4.5:1, or switch to dark text.
Pale bot text
๐Ÿšฉ FailsLight grey text on a near-white bot bubble because it ‘looks clean’.
โœ… FixUse a dark grey or near-black for message text; keep pale grey for timestamps only.
Emoji-only buttons
๐Ÿšฉ FailsQuick-reply buttons like ๐Ÿ“ฆ, ๐Ÿ’ฐ and ๐Ÿ™‹ with no words.
โœ… FixAdd words: ๐Ÿ“ฆ Track order, ๐Ÿ’ฐ Prices, ๐Ÿ™‹ Talk to a person.
Greeting that steals focus
๐Ÿšฉ FailsA pop-up greeting that jumps the keyboard focus away from what the visitor was reading.
โœ… FixShow greetings without moving focus, and make them easy to dismiss.
Chat as the only route
๐Ÿšฉ FailsNo phone number or email anywhere near the chat.
โœ… FixShow at least one other way to reach you on contact and help pages.

Accessible wording

The parts you control completely: what the bot says

Even when the widget itself is built well, the content inside it is yours: the welcome message, the bot’s answers, the button labels in your flows and your saved replies. Most accessibility wins here are also clarity wins for everyone.

Make buttons say what they do

“Track my order” beats “Option 2”. “Talk to a person” beats “๐Ÿ™‹”. A screen reader reads the label aloud, so an emoji-only button may be announced as its emoji name, or not at all.

Don’t rely on colour

“Items in green are in stock” excludes colour-blind visitors and screen reader users. Say “In stock” in words.

Keep messages short, one idea each

Long blocks are hard to read at high zoom and tiring to listen to. Two or three short sentences per bubble, then let the visitor reply.

Describe links

A link that reads “see our delivery areas” is better than “click here”. Screen reader users often jump between links and hear them out of context.

Use plain words

Avoid jargon and internal terms. If you have to use one, explain it the first time. Our guide to writing a welcome message has examples of short, clear openers.

Offer another route

Some visitors will never be comfortable in a chat. Show a phone number or email alongside it. Accessibility means choices, not only a better chat.

Your audit

Fifteen-minute accessibility check

Tick as you go. Your ticks stay in this browser tab only.

Chat accessibility

Working with your provider

What you can fix, and what to ask about

Some fixes are in your hands; others live in your chat provider’s code. Split your findings into two lists.

You can usually fix: colours, the welcome text, bot answers, button labels in flows, saved replies, where the chat appears and whether a phone number sits nearby. In LiveChatBot, colour, position, team name, avatar and welcome text are all set in the widget settings; our widget customisation guide walks through them, and UI for chatbot branding covers choosing colours that suit your brand and stay readable.

Ask your provider about: keyboard support, focus outlines, screen reader announcements, behaviour at high zoom and target sizes. Describe what you tested and what happened, for example “With NVDA on Chrome, new bot replies are not announced.” Specific reports get fixed faster than “is your widget accessible?”

Re-test after every redesign, colour change or new flow. Accessibility slips quietly: one new brand colour or one emoji-only button can undo a careful setup. Our guide to designing chat for phones covers related touch and keyboard issues on small screens.

Accessible websites with chatbots aren’t harder to run; they’re just checked more carefully. LiveChatBot’s free plan includes the chat widget with your own colours, Flows with button labels you write, and saved replies, for two websites with 100 visitors per website each month. Start on livechatbot.in.

Frequently asked questions

What contrast should chat bubbles have?

At least 4.5:1 between text and bubble background for normal-sized text (WCAG AA), and at least 3:1 between the launcher button and the page around it.

Why does white text on my brand green fail?

Many bright greens, oranges and light blues are too light for white text. Darken the bubble colour until it reaches 4.5:1; the checker suggests a shade.

How do I test my chat with a screen reader?

Use NVDA on Windows, VoiceOver on Mac or iPhone, or TalkBack on Android. Open the chat, send a message and check the reply is read out.

Are emoji in bot messages bad for accessibility?

Not on their own. Avoid buttons or messages where an emoji carries the meaning without words, because screen readers may read them oddly or skip them.

Do accessibility rules apply to small businesses?

It depends on where you trade. WCAG is the common standard that laws reference; following it is also simply good for customers.

Keep reading

Related guides

๐Ÿ“˜

Websites With Chat, Mystery-Shopped: How to Test Competitors’ Chat in One Hour and Copy What Works

Read the guide โ†’

๐Ÿงญ

Website Chat App Requirements: Write a One-Page Spec Before You Choose (Free Spec Builder)

Read the guide โ†’

๐Ÿ› ๏ธ

Website Bot Visitors: How to Spot Crawlers, AI Scrapers and Spam Bots in Your Traffic and Chat

Read the guide โ†’

A chat every visitor can use

Pick readable colours, write clear buttons and test with a keyboard. Start free on livechatbot.in.