Components.AI: Add automated accessibility coverage
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 281
Description
### Is your feature request related to a problem? Please describe the problem.
The built-in UI has no comprehensive automated accessibility gate.
### Describe the solution you'd like
Add axe-based E2E checks plus focused keyboard, focus, announcement, forced-colors, reduced-motion, and touch-equivalent scenarios across page, drawer, bubble, composer, message actions, approvals, and attachments.
### Additional context
Leaf task for #68227 requirements I8 and M2.
Contributor guide
Research direction
Start by reading the linked #68227 requirements I8 and M2, then locate the Components.AI E2E test entry point. Add axe-based coverage and the listed keyboard, focus, announcement, forced-colors, reduced-motion, and touch-equivalent scenarios across the named UI areas; done means these checks cover page, drawer, bubble, composer, message actions, approvals, and attachments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- accessibility, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100