Skip to content

fix: Visible focus and forced colors support - #2616

Draft
bprusinowski wants to merge 1 commit into
feat/a11y-toolingfrom
fix/a11y-theme
Draft

bprusinowski wants to merge 1 commit into
feat/a11y-toolingfrom
fix/a11y-theme

Conversation

@bprusinowski

Copy link
Copy Markdown
Member

Part of the GitLab a11y audit. Fixes issues 131, 125, 129 and the focus part of 124.

This PR:

  • adds one visible focus ring (federal design system purple) for keyboard focus across buttons, links, tabs, menu items, inputs and sliders
  • gives the switch sufficient contrast
  • keeps switches, tabs and selected states visible in forced colors (high contrast) mode

How to test

  1. Tab through the home page, browse page and the chart editor: every stop shows a purple ring.
  2. In Chrome DevTools → Rendering, enable "forced-colors: active" and repeat.
  3. Run yarn test themes and npx playwright test e2e/keyboard-focus.spec.ts.

  • I added a CHANGELOG entry
  • I made a self-review of my own code
  • I wrote tests for the changes (if applicable)

@vercel

vercel Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
visualization-tool Error Error Nov 13, 2026 1:13pm UTC

Request Review

This branch had an error being deployed

1 failed deployment
Preview — eb3f2a51 Deployed Nov 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant