accessibility-robust

What problem does it solve?

Ensuring your interface is robust enough that assistive technologies (like screen readers and voice control) can correctly interpret your UI across browsers, components, and frameworks.

Core Features & Use Cases

• Compatible markup: Use semantic HTML first so name, role, and value are programmatically determinable for every UI component.
• Reliable status announcements: Publish dynamic updates (validation, toasts, search-result changes) through live regions without focus shifts.
• ARIA done only when needed: Apply ARIA only to non-native widgets or to add missing state, while avoiding conflicting roles that break semantics.

Use cases include deciding between semantic elements vs custom components, adding ARIA for custom controls, and auditing a UI built heavily from <div> elements for assistive-technology robustness.

Quick Start

Use the accessibility-robust skill to review a UI and identify where semantic HTML is missing, where ARIA is conflicting or incomplete, and whether status messages are announced via appropriate live regions.