Accessibility And Inclusive UI Review
Audit a screen and its component patterns for semantic, keyboard, focus, and assistive-technology failures.
Where it runs
Runs inside BuildOS
Free to start. Create an account and the skill opens in BuildOS chat with the prompt already drafted. Nothing runs until you send it.
Use Cases
When to use it
Audit a route, form, dialog, menu, table, or custom control.
Diagnose keyboard, focus, contrast, or screen-reader problems.
Review a design-system primitive before it propagates.
Workflow
How it works
- 1
Run a screen-level accessibility pass on the core flow.
- 2
Run a component-pattern pass on the primitives in use.
- 3
Classify each finding by WCAG criterion, evidence, and severity.
- 4
Prioritize reusable primitive fixes and human-review items.
Try It
Start with an editable prompt
Audit this screen for keyboard, focus, semantics, contrast, and dynamic-content risks.
Review this component primitive and identify the highest-leverage inclusive fix.