dotnet / dotnet/aspnetcore

Components.AI: Make decorator actions accessible on hover, tap, focus, and keyboard

Open
#68,425 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: M feature-accessibility Priority:0
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.

Hover-only action disclosure excludes touch and keyboard users, and revealing controls can cause layout movement.

### Describe the solution you'd like

Reserve decorator-row space, reveal the shipped default on hover/tap/focus without shifting content, keep controls in the accessibility tree with distinct names, and provide keyboard traversal compatible with virtualization.

### Additional context

Leaf task for #68227 requirements F4 and H6.

Contributor guide

Open the contributing guide

Research direction

Start by reading the Components.AI context and requirements F4 and H6 in issue #68227, then locate the corresponding implementation and tests. Done means decorator actions remain accessible on hover, tap, focus, and keyboard without layout movement, retain distinct accessible names, and support keyboard traversal with virtualization.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.