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.
A review skill that checks front-end code for accessibility barriers before they reach users.
Run this on any PR that modifies UI components, page layouts, or interactive elements. Required before launching user-facing features.
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.
Use semantic HTML elements (<nav>, <main>, <article>, <button>) instead of generic <div> and <span> with click handlers. Screen readers and assistive technology rely on semantic elements to understand page structure — a <div onClick> looks like nothing to a blind user.
Every <img> must have a meaningful alt attribute. Without alt text, screen readers either skip the image entirely or read the raw filename ("DSC_0042.jpg"), leaving visually impaired users completely unable to understand the content.
Text must meet WCAG AA contrast ratio: 4.5:1 for normal text, 3:1 for large text. Low-contrast text is unreadable for users with low vision, color blindness, or anyone using a screen in bright sunlight — affecting up to 8% of male users (color blindness alone).
BeforeMerge scans your pull requests against all 4 Accessibility Review rules automatically. Get actionable feedback before code ships.