Naser Mansour
7f35297025
Naser confirmed all remaining QA Review / Draft rows (97 subtasks, 16
parent rollups) are done in substance: the site has been in production
for roughly a year. Overrides the conservative QA-Review/Draft mapping
from the prior takeover commit (0f9d12c) at his explicit instruction.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 13-1 | 13-1 Language Toggle Visibility Enhancement | Done | 2026-09-27 | 13 |
Description
As a user on authentication pages I want to clearly see and interact with the language toggle So that I can easily switch between Arabic and English. - resources/views/components/language-toggle.blade.php. Full implementation history: docs/stories/story-13.1-language-toggle-visibility.md
Acceptance Criteria
- AC1: Update Light Variant Text Color: Given the language toggle has a
lightvariant for light backgrounds; When viewed on auth pages (white/cream background); Then the inactive language usestext-primary(Dark Forest Green #2D3624) instead oftext-body/70 - AC2: Update Light Variant Hover State: Given the user hovers over an inactive language option; When the variant is
light; Then the hover state uses: - AC3: Update Light Variant Separator Color: Given the separator
|between languages; When the variant islight; Then it usestext-primary/50instead oftext-body/30for better visibility - AC4: Dark Variant Unchanged: Given the language toggle has a
darkvariant for dark backgrounds (navigation bar); When viewed on the public navigation; Then the existing styling remains unchanged: - AC5: Active State Unchanged: Given the currently active language; When displayed in either variant; Then it maintains the existing active styling:
- AC6: Contrast Compliance: Given accessibility requirements; When the light variant is used on Warm Cream background (#F4F1EA); Then the text contrast meets WCAG AA: