smukh Accessible dynamic updates
Workflow
- List the initiating action, update type, loading/error/completion states, and the user's expected next task.
- Use the dynamic update guide to decide whether to move focus, expose a passive status, or leave an ordinary content update alone.
- Observe focus and live-region mutations during the entire sequence, including rapid updates, cancellation, retry, and stale responses. Do not infer speech from attributes.
- Repair the responsible state/announcement logic. Add tests for preserved focus, relevant completion feedback, and superseded or cancelled work.
- Run the guide's manual screen-reader procedure to assess timing, duplication, interruption, and reading continuity.
Boundaries
Generic component semantics remain in accessible-component-review. This skill owns temporal behavior across states. Do not make every changing subtree live, use assertive alerts for all updates, or claim that a mutation trace proves a screen reader announced it.