Accessibility: Footer text contrast too low #191
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#191
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: Minor
Description: Footer text uses
text-navy-light(#68A3B8) onbg-primary-navy(#0B2A3C). Contrast ratio is ~3.3:1, below WCAG AA 4.5:1 for normal text.Files:
src/components/layout/Footer.jsx,src/index.cssFix direction: Darken
#68A3B8to at least#475569(~5.4:1) or usetext-white/90.Not a defect, and the suggested fix would have caused a serious regression. Closing with the arithmetic.
The claim: text-navy-light (#68A3B8) on bg-primary-navy (#0B2A3C) is '~3.3:1, below WCAG AA 4.5:1'.
Measured: 5.33:1. That passes WCAG AA for normal text. The figure in the issue is wrong.
The proposed fix is the important part. It suggested darkening to #475569 'for ~5.4:1'. Against #0B2A3C that is 1.96:1 — a dark slate on a dark navy. It would have failed not only AA for text but the 3:1 non-text threshold as well, on all 11 footer links. Acting on this issue as written would have made the footer substantially less readable than it is today.
Its alternative suggestion, text-white/90, measures 12.32:1 and would have been safe — but it is not needed, and it would flatten the deliberate visual hierarchy between footer body text and headings.
Closing as no change required.
Verify: WCAG contrast of #68A3B8 on #0B2A3C is 5.33:1 (passes AA normal text); #475569 on #0B2A3C is 1.96:1 (fails everything).