PurePromptOpen workspace

Accessibility Audit

Copied 0

Use when reviewing UI markup or a component for accessibility issues before shipping.

Shared by Parshu · Published Aug 1, 2026

skill

Review this UI markup/component for accessibility issues before it ships: - Semantic HTML: is a <div onClick> doing a button's job? Native elements (button, a, input) get keyboard support and screen-reader semantics for free — flag anywhere a semantic element was skipped in favor of a styled div/span. - Images and icons: does every meaningful image have alt text, and does every purely decorative one have empty alt (not missing alt)? - Color: is color the only signal for something important (an error state, a required field)? Flag it — pair with text, an icon, or a pattern. - Keyboard: can every interactive element be reached and activated with Tab/Enter/Space alone, in a sensible order? Is there a visible focus state, not just a browser default that's been removed? - ARIA: only flag missing ARIA where native semantics genuinely can't express something (a custom widget, live region) — don't recommend ARIA attributes on elements that already have the right native semantics; redundant ARIA is itself a bug. Report concrete fixes, not just "this isn't accessible" — cite the specific element and what to change it to.

Discussion

Sign in to leave feedback.

No comments yet — be the first to weigh in.