Find interface accessibility barriers

better-accessibility reviews interface semantics, keyboard operation, focus, accessible names, forms, dynamic announcements, motion and zoom. Findings identify the WCAG criterion being broken and describe fixes in the project's existing styling system. Its review follows a keyboard-only walk through the flow and a screen-reader walk that checks each control's name, role and state. Native platform behavior takes priority over custom replacements.

The guidance distinguishes WCAG 2.2 Level A and AA failures from recommendations. Findings need a numbered criterion or a concrete task an assistive-technology user cannot complete. AAA criteria, APG conventions, the one-h1 and no-skipped-levels outline, and the 44px and 40px target recommendations are never HIGH on their own. Established usable density should be preserved.

Control checks cover native buttons for actions, real links for navigation, disabled behavior and visible keyboard focus. Custom focus indicators need an explicit color and verified contrast against adjacent colors, including forced-colors handling. Focus must remain visible around sticky chrome. Keyboard interactions follow widget patterns, with natural tab order, roving tabindex or aria-activedescendant where appropriate. Overlays move focus inside, make the background inert and return focus to their trigger. Route changes update the document title and focus the new view.

Forms receive bound labels, useful autocomplete values, names, types and input modes. Paste remains available. Validation happens on submit, marks invalid fields, connects inline error descriptions and focuses the first failure. Icon buttons need names, visible labels remain part of accessible names, and decorative content stays out of the accessibility tree without hiding focusable controls.

The skill also checks target collisions and alternatives to dragging; redundant cues for color-coded status; reduced-motion behavior; pause controls for persistent movement; and action or error toasts that remain until dismissed. Announcements distinguish field errors, polite updates and urgent alerts. Stable empty live regions support repeated polite messages. Image descriptions follow purpose: decoration, information or action. Headings, a primary main landmark and a skip link support navigation. Text must survive 200% resizing, with reflow at 320px and no restrictive viewport settings. The Level AA hit-area baseline is 24 by 24 CSS pixels or an applicable exception; 44 by 44 touch and 40 by 40 desktop targets remain recommendations. Text contrast is 4.5:1, or 3:1 for large text at 24px or 18.67px bold; meaningful UI boundaries require 3:1. Inactive controls and logos are exempt. Custom focus indicators also need 3:1 against adjacent colors; a 2px solid perimeter with a 3:1 contrast change is the separate 2.4.13 AAA target. Movement continuing beyond five seconds needs a pause control.

Use it for an authorized interface accessibility review or requested implementation. Reviews remain read-only unless changes are requested. Unrelated work is preserved, synthetic fixtures replace private customer data, and connected tools require authorization. It is scoped guidance rather than a proof of conformance; browser and assistive-technology availability limit what can be verified. A source inspection alone cannot justify approval of behavior that was never exercised.

The input is the interface or component within the requested scope. Without a browser, checks inspect names, handlers, focus styles, motion guards and label bindings. Browser verification adds keyboard traversal, computed accessibility names and roles, visible focus at each stop and an automated audit. Unavailable checks are marked Not verified.

The result groups findings by violated principle and severity, with one row per root cause covering every affected location. Rows contain severity, file and line, before, after and a reason naming the criterion and user impact. HIGH means a prevented task, inaccessible content or systemic failure; MEDIUM means a meaningfully harder interaction; LOW means isolated polish. Any remaining HIGH ends in Block; otherwise the result is Approve with remaining work listed. A clean result reports no actionable findings together with verification coverage.

better-colors owns rendered contrast measurement and color changes. The better-typography skill owns text sizing, input zoom and language metadata; better-layout owns spatial fixes and RTL. The better-writing skill handles wording, while better-ui owns animation recipes, hover styling and scroll containment. The workflow is adapted from jakubkrehel/skills under the MIT license.