New series: what assistive tech really hears on your checkout page. Start with part one →
Shipwright
Home
Accessibility Jun 27, 2026 1 min read 176 views

Contrast Ratios in the Wild: A Visual Audit of Six Dashboards

Mara Okafor

Mara Okafor

@maraokafor

Share
Cover illustration for the article Contrast Ratios in the Wild: A Visual Audit of Six Dashboards

Screenshots from real admin screens, annotated with their measured contrast ratios. Accessibility bugs are easy to miss because they do not show up in screenshots. The only reliable way to find them is to use the interface the way assistive technology users do.

Analytics: secondary labels at 3.1:1
Analytics: secondary labels at 3.1:1
Billing overview passes AA throughout
Billing overview passes AA throughout
Admin sidebar: disabled items at 2.4:1
Admin sidebar: disabled items at 2.4:1
Monitoring wall: red and green pairs
Monitoring wall: red and green pairs
CRM pipeline chips at 4.6:1
CRM pipeline chips at 4.6:1
Support inbox placeholders at 2.9:1
Support inbox placeholders at 2.9:1

Reading the audit

Most of the problems we found came from custom controls that looked like buttons but were built from generic elements. Switching to native elements fixed focus, keyboard support, and announcements in one step.

What we would change next time

Questions, corrections, and war stories are welcome in the comments. Several of our best follow-up posts started as a reader pointing out something we had missed.

  • Use native elements before ARIA.
  • Every interactive element needs a visible focus style.
  • Test with a keyboard before every release.
  • Keep text contrast at 4.5:1 or higher.
Mara Okafor

Mara Okafor

Author

Staff frontend engineer focused on CSS architecture and accessibility. Mara has audited more design systems than she can count and still gets excited about a good focus ring.

Related Posts

Comments 0

Leave a comment

Your email will not be published. Sign in for a faster experience.

Supports **bold**, *italic*, and `code`.