Problem
Six aria-live or role="status" regions across the entire frontend. The moments that most need announcing are exactly the asynchronous ones: analysis finished, tokenizer download completed, job cancelled.
Current state
The project's own conventions require WCAG AA and full keyboard operation, so this is a stated standard not yet met.
Where to add
- Job completion messages (analysis done, export saved, download finished)
- Error messages (file parse failed, model not found)
- Status transitions ("Downloading tokenizer...", "Analysing...", "Done")
Implementation
Use aria-live="polite" on status containers. When status changes, update the text. Screen readers announce the new content automatically.
Scope
Intermediate — mostly adding the right ARIA attributes and ensuring messages are descriptive, not just "Done".
Problem
Six
aria-liveorrole="status"regions across the entire frontend. The moments that most need announcing are exactly the asynchronous ones: analysis finished, tokenizer download completed, job cancelled.Current state
The project's own conventions require WCAG AA and full keyboard operation, so this is a stated standard not yet met.
Where to add
Implementation
Use
aria-live="polite"on status containers. When status changes, update the text. Screen readers announce the new content automatically.Scope
Intermediate — mostly adding the right ARIA attributes and ensuring messages are descriptive, not just "Done".