docs: accessibility audit for framework tracker

Aperta
  • Qualcosa non va?
#761 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
playwright, typescript
Ambito
accessibility, frontend, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
42
Fork
16
Merge medio
12h 36m
PR unite (30g)
151

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di e18e/framework-tracker

Tutte le issue di e18e/framework-tracker

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.