A complex interface can look efficient while becoming unusable to a keyboard or assistive-technology user. Read-only records need clear row and column relationships; an editable grid needs an additional keyboard mode. Search suggestions need a stable active option and a clear way to leave the popup. Dragging a priority card needs a non-drag route to the same action. Async notifications need to identify what changed without stealing focus or repeating an entire panel. The case-review workspace ties these behaviors to one set of real tasks.
Topics in this track
- Data Table Versus Interactive Grid — Use native table relationships for reading and add grid keyboard behavior only when cells are truly interactive.
- Combobox Suggestions and Active Option — Keep input editing intact while suggestions announce a stable active option and commit path.
- Reorder Controls Without Dragging — Give priority changes a keyboard and single-pointer path that uses the same ordered mutation.
- Async Status Announcements and Focus — Report background results without stealing focus or repeatedly announcing an entire region.
Prerequisite paths
Accessible Names and Native Controls; Dialog Focus and Interruption Boundary; Form Errors and Recovery Paths.
Neighbor track
Streaming and Large Data Interfaces.
Practice path
Build Project: accessible operations workspace and check decisions in Web Development: streams and interaction decisions quiz.