docs: accessibility audit for framework tracker

Abierto
  • ¿Algo no está bien?
#761 1 comentario 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
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
playwright, typescript
Área
accessibility, frontend, testing

Línea de trabajo

Start by reviewing the component tests mentioned in #759 and how the built site and CI are configured. The issue suggests running @axe-core/playwright across built pages, then manually checking chart alternatives, screen reader tables, keyboard access to tooltips and controls, and both themes. Done means agreeing on an audit approach and fixing or triaging the findings; no specific files or completion criteria are named.

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

Descripción

enhancement research

suggestion: it might be worth doing a proper accessibility audit of the site at some point.

astro's dev toolbar already has an audit app that flags a11y issues while you browse in dev, which is nice, but it only covers the surface: a limited set of rules, only on the page you have open, and only while running astro dev. the component tests from #759 also run axe, but on each component on its own, so they miss things you only get on real pages like landmarks and headings, colour contrast with the actual theme, or the charts once they're mounted in context.

a few ideas on how we could approach it:

  • run axe (@axe-core/playwright) over every page of the built site in ci, so issues show up on prs instead of whenever someone opens the toolbar
  • go through what it finds and fix or triage it
  • do a manual pass on what tools can't judge: text alternatives for the charts, the screen reader tables, keyboard access to tooltips and the chart controls, both themes

automated checks only catch part of wcag issues, so the manual pass is probably where most of the value is. open to other ideas or tools if anyone has experience with this.

Lenguaje dominante
TypeScript
Estrellas
42
Forks
16
Merge medio
12 h 36 min
PR fusionados (30 d)
151

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 e18e/framework-tracker

Todos los issues de e18e/framework-tracker

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.