Accessibility

v1.0.0

Reviews web UI for WCAG compliance — semantic HTML, ARIA usage, keyboard navigation, color contrast, and screen reader compatibility. Accessibility bugs exclude real users and often violate legal requirements, yet they are invisible to sighted mouse-users during development.

4 rules

1 categories

Quality(4)

Ensure Keyboard Navigation

Every interactive element must be operable via keyboard alone (Tab, Enter, Space, Escape). Users with motor disabilities, RSI, or broken trackpads cannot use a mouse — if your app requires mouse interaction, those users are completely locked out.

ARIAKeyboardWCAG

CRITICAL

Automate Accessibility checks on every PR

BeforeMerge scans your pull requests against all 4 Accessibility rules automatically. Get actionable feedback before code ships.

Join Waitlist Browse All Rules

Accessibility Review

A review skill that checks front-end code for accessibility barriers before they reach users.

What it covers

Semantic HTML — correct heading hierarchy, landmark regions, lists for list content, buttons vs. links
ARIA usage — ARIA only when native HTML is insufficient, correct roles, live regions for dynamic content
Keyboard navigation — focus management, visible focus indicators, no keyboard traps, skip links
Forms — associated labels, error messages linked to inputs, fieldset/legend for groups
Color and contrast — WCAG AA contrast ratios, not relying on color alone to convey meaning
Media — alt text for images, captions for video, reduced motion preferences

When to use

Run this on any PR that modifies UI components, page layouts, or interactive elements. Required before launching user-facing features.