Skip to content

Customise a chat widget's look without giving up accessibility

Brand colour, logo, position: how to dress a chat widget in a client's colours while keeping a contrast that every visitor can read, on desktop and on mobile.

Widget and integration5 min read

Your client has a brand colour and wants to see it everywhere, including in the chat widget on their site. Fair enough: an assistant in the company’s colours earns more trust than a generic window. But not every colour works behind text. Bright yellow with white text, pale green with grey text: it can look elegant in a mock-up and be unreadable for part of the audience.

This article explains how to reconcile brand identity and readability, and how blabla.bot frames widget customisation to avoid bad surprises.

Why contrast matters

Contrast is the difference in brightness between text and its background. It is expressed as a ratio, from 1:1 (no difference, invisible text) to 21:1 (black on white).

The Web Content Accessibility Guidelines (WCAG), published by the W3C, set precise thresholds. At level AA, the most common reference level:

  • normal-size text needs a ratio of at least 4.5:1 with its background;
  • large text (18 points, or 14 points bold) needs at least 3:1;
  • interface components, such as button outlines and state indicators, need 3:1 against adjacent colours.

These thresholds are not only for people with low vision. They also help the visitor reading the site on a phone in bright sunlight, or on a poor screen.

Colours that cause trouble

Some colour families are classic traps with white text:

Main colourRisk with white textWay out
Yellow, chartreuse, light greenVery low contrastSwitch to dark text
Bright orangeOften just below the thresholdDarken the shade slightly
Sky blue, turquoiseNot enough contrastDarken or switch to dark text
Navy, burgundy, forest greenUsually fineNo change

The good news is that there is almost always a solution that respects the brand: either a slightly darker version of the same hue, or dark text instead of light text.

How blabla.bot frames customisation

Rather than total freedom, blabla.bot offers presets with guardrails. You choose:

  1. A preset, out of three: Clean (4 px corners), Soft (16 px corners) and High contrast (dark background, designed for a 7:1 contrast).
  2. A main colour, as #rrggbb. It colours the widget header, the visitor’s bubbles, the send button and the launcher button.
  3. The text on that colour: light or dark.
  4. A logo, shown in the header.
  5. The launcher position: bottom right or bottom left.
  6. A welcome message and up to three suggested questions.

There is no free CSS and no font choice. That is deliberate: every extra option is another chance to break readability or the mobile layout.

A contrast check that blocks publishing

When you pick a colour, the console computes the ratio between the text and the main colour. Below 4.5:1, publishing is blocked and two fixes are offered:

  • the nearest shade that meets the threshold, in the same colour family, darker under light text or lighter under dark text;
  • the other text colour, if it passes.

The server runs the same calculation when saving. Even if someone bypasses the console, an unreadable combination is never stored.

In practice, if your client insists on their orange and white text only reaches 3:1, the console suggests a slightly deeper orange that passes, or dark text on the original orange. You show both options to the client and let them choose.

A light, safe logo

The logo accepts PNG, JPEG and WebP, up to 200 KB. SVG is refused, because an SVG file can carry script. For a crisp result, prepare a version of the logo that reads well at small size on the chosen main colour.

Accessibility goes beyond colour

Contrast is the visible part. The blabla.bot widget also includes several behaviours you do not have to configure:

  • Keyboard. Once the window is open, the Tab key cycles through its elements without escaping behind it, and Escape closes the chat. Enter sends the message, Shift + Enter adds a new line.
  • Screen readers. The conversation is announced as answers arrive, and buttons carry explicit labels.
  • Motion. Small animations are turned off when the visitor has asked their system to reduce motion.
  • Sources. Links to sources say that they open in a new tab.

A faithful preview before you publish

The “Widget appearance” screen shows a live preview of the real widget, not an imitation. You can switch between desktop and mobile formats. Visitors only see the changes after you click “Publish changes”, the next time they open the widget. Only the logo applies as soon as it is uploaded.

A six-step method

  1. Get the client’s exact main colour as a hex code.
  2. Pick the preset closest to their site: sharp or rounded corners.
  3. Enter the colour and look at the ratio shown.
  4. If publishing is blocked, compare the two suggested fixes with the client.
  5. Add the logo and check it reads well on the main colour.
  6. Check the preview in mobile format, then publish.

One more tip: also look at the launcher button on the site’s real pages. It must stand out from the page background. A navy button on a navy site will be hard to spot, even if its text is perfectly readable.

Your client’s brand, not ours

The widget does not show the blabla.bot brand to visitors. If you wish, you can turn on a discreet line, “Assistant set up by” followed by your agency’s name. It is off by default.

In short

Customising a widget does not mean accepting any colour combination. With a preset, one main colour and a contrast check that blocks unreadable cases, you get a widget that looks like your client and that all their visitors can read.

Common questions about customisation and white label are gathered in the FAQ.

Sources

Tags

  • widget
  • accessibility
  • contrast
  • white label