The-DevOps-Daily / The-DevOps-Daily/devops-daily
feat: Add dark mode contrast audit and improvements
Open
Nobody has claimed this yet.
enhancement
good first issue
hacktoberfest
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 392
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 121
Description
Description
Audit and improve dark mode color contrast ratios to meet WCAG AA standards.
Problem
- Dark mode exists but contrast ratios haven't been audited
- Some text/background combinations may not meet WCAG standards
- Code blocks in dark mode may have poor readability
- Potential accessibility issues for users with visual impairments
WCAG Requirements
- AA (minimum): Contrast ratio of 4.5:1 for normal text
- AA (large text): Contrast ratio of 3:1 for 18px+ or 14px+ bold
- AAA (enhanced): Contrast ratio of 7:1 for normal text
Areas to Audit
- Body text on background
- Headings on background
- Links (hover, focus, active states)
- Code blocks syntax highlighting
- Quiz cards and buttons
- Form inputs
- Navigation menu
- Footer
Tools for Testing
- Chrome DevTools Lighthouse
- WebAIM Contrast Checker
- axe DevTools browser extension
- Colour Contrast Analyser
Proposed Solution
- Audit all color combinations
- Document current contrast ratios
- Update colors that fail WCAG AA
- Consider adding high-contrast theme option
- Document color palette with contrast ratios
Acceptance Criteria
- Audit all text/background combinations
- Document current contrast ratios
- Fix colors that fail WCAG AA
- Ensure all code block colors meet standards
- Test with actual users (color blindness simulators)
- Update Tailwind color config
- Add contrast ratio documentation
- Add automated contrast checks to CI
Example Improvements
/* Before: Might be 3.2:1 ratio */
--text-secondary: rgb(156 163 175);
/* After: 4.6:1 ratio */
--text-secondary: rgb(209 213 219);
Files to Modify
app/globals.css- Update CSS custom propertiestailwind.config.ts- Update color palettecomponents/code-block.tsx- Update syntax themedocs/colors.md- New color documentation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing the color combinations in app/globals.css, tailwind.config.ts, and components/code-block.tsx with Lighthouse, axe DevTools, or a contrast checker. Compare the results with the WCAG AA ratios and record them in the new docs/colors.md file. Done means the listed areas meet AA, code blocks are readable, and the requested documentation and automated contrast checks are added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tailwindcss, typescript
- Domain
- accessibility, ci-cd, documentation, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100