[Tracking] Accent colour contrast fixes

Abierto
  • ¿Algo no está bien?
#402 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
css
Área
accessibility, frontend

Línea de trabajo

Start with the linked issues #326, #373, and #374 in the suggested order; the shared stylesheet is index.css, and the affected controls appear on the journal and Tasks pages. Re-measure contrast using computed colours, then check both pages in light and dark mode. Done when all three issues are closed and white-on-accent text meets 4.5:1 in every theme and mode combination.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

tech-debt

Groups the accent-colour contrast fixes. They share one new token, --on-accent, and edit the same stylesheet, so they are built in one order.

Suggested order

  1. #326 — Fix the Save button text contrast in the block-reason editor and add the per-theme --on-accent token
  2. #373 — Apply --on-accent to the other white-on-accent sites that fail contrast. Blocked by #326
  3. #374 — Fix the active settings segment button losing its accent background in dark mode. Blocked by #373

Why this order

  • #326 adds the token that #373 applies.
  • #374 was found during the #326 audit and edits .settings-seg-btn in index.css, which #373 also touches. Doing it last means it rebases once.

Notes

  • All three are frontend-only (TaskFlow.Web), so they do not depend on the monorepo move (#397).
  • Contrast figures in #326 and #373 were computed by hand and must be re-measured with computed colours.
  • The journal and Tasks pages both use the controls involved. Check both after each change, in light and dark mode.

Done when

All three are closed, and no white-on-accent text fails 4.5:1 in any theme and mode combination.

Lenguaje dominante
C#
Estrellas
1
Forks
0
Merge medio
2 h 2 min
PR fusionados (30 d)
98

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nevridge/TaskFlow

Todos los issues de nevridge/TaskFlow

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.