Accessibility: Sheet close button contrast below 3:1 (WCAG AA fail) #190
Labels
No Label
P0
P1
P2
P3
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
phase-7
phase-8
release-blocker
security
seo
ui
ux
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Queue-North-Website#190
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity: Major
Description: The Sheet component close button uses
text-white opacity-60 hover:opacity-100onbg-primary-navy. Theopacity-60reduces contrast below 3:1, failing WCAG AA.File:
src/components/ui/Sheet.jsxline 59Fix direction: Use
text-whitewithhover:text-primary-cyanor increase base opacity toopacity-80.Not a defect — measured rather than eyeballed, and the premise does not hold.
This issue states the Sheet close button's 'opacity-60 reduces contrast below 3:1, failing WCAG AA'.
src/components/ui/Sheet.jsx:36 renders text-white at opacity-60 on bg-primary-navy (#0B2A3C). Compositing #FFFFFF at 60% over #0B2A3C gives rgb(157,170,177), which measures 6.25:1 against that background — more than double the 3:1 WCAG 1.4.11 requires for a UI component, and above the 4.5:1 for normal text as well.
For reference, since the issue proposed raising the opacity: 70% is 7.97:1, 80% is 9.95:1, 90% is 12.32:1. All fine, none needed.
Closing as no change required. The button also already carries focus:ring-2 focus:ring-white with an offset, so it is keyboard-visible too.
Verify: composite #FFFFFF at alpha 0.6 over #0B2A3C and compute the WCAG contrast ratio against #0B2A3C — it is 6.25:1, above the 3:1 threshold this issue claims is failed.