跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

better-accessibility

Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says "make this accessible" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, pointer-events, hover on touch, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, "not keyboard accessible".

boraoztunc · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add boraoztunc/skills --skill better-accessibility

技能说明


name: better-accessibility description: Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says "make this accessible" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, pointer-events, hover on touch, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, "not keyboard accessible".

Accessibility that comes with the craft

Accessibility is not a compliance checkbox bolted on at the end; it is the floor for interface craft. Most of it is free if you use the platform: native elements ship with keyboard support, real labels announce themselves, and a visible focus ring is one CSS rule. Apply these principles when building or reviewing UI code, and write every fix in the project's own idiom: the styling system already in use, never a second one alongside it.

When reviewing, walk the interface as a keyboard-only user first (every flow must complete without a mouse), then as a screen-reader user: does each control announce a name, a role, and its state? When unsure, prefer the platform default over a custom rebuild, and remove ARIA rather than add it.

Rendered-pair contrast measurement and color remediation are covered by the better-colors skill; visual text sizing and iOS input zoom by better-typography; spatial RTL layout by better-layout.

Quick Reference

CategoryWhen to Use
Focus & KeyboardFocus rings, skip links, tabindex, focus trapping, APG keyboard patterns
Semantics & ARIANative elements first, button vs link, landmarks, accessible names, disabled states
FormsLabels, autocomplete, error messaging, input types
Screen ReadersVisually hidden content, live regions, toasts, alt text, SVG
Hit AreasTarget sizes, expanding hit areas, collision rules
Motion & Zoomprefers-reduced-motion, autoplay and timed UI, 200% zoom, reflow, rem vs px
Review Output FormatSeverity scale, findings table, verification, verdict

Core Principles

1. Native Elements First

The first rule of ARIA: don't use ARIA when a native element exists. <button> for actions, <a href> for navigation (it must support Cmd/Ctrl/middle-click), never <div onClick>. No ARIA is better than bad ARIA.

2. Visible Focus Rings

Style :focus-visible, not bare :focus, so keyboard users get a ring and mouse users usually don't. Prefer the browser's unmodified focus indicator. If the design needs a custom ring, use a project focus token or another explicit color and verify the complete indicator against every adjacent color it crosses; currentColor is acceptable only after the same check. Use at least a 2px solid perimeter or an equivalent visible area. Never use outline: none without a verified replacement, and preserve system colors in forced-colors mode.

3. Full Keyboard Support

Every pointer interaction needs a keyboard path, following the ARIA APG patterns: Escape closes overlays, arrow keys move within composite widgets (tabs, menus, listboxes), Tab moves between widgets, Enter and Space activate. Only tabindex="0" (join the natural tab order) and tabindex="-1" (programmatic focus), never positive values, which break the natural order. Composite widgets use roving tabindex: the active item is 0, all others -1.

4. Trap and Restore Focus

Modals set inert on the background content, move focus inside on open, and return focus to the trigger on close. Add overscroll-behavior: contain so background content doesn't scroll.

5. Minimum Hit Area

WCAG 2.5.8's Level AA baseline is a 24×24 CSS-pixel target or one of its defined spacing, equivalent-control, inline, user-agent, or essential exceptions. For easier activation, aim for 44×44px in touch contexts and 40×40px in desktop interfaces when density permits. Extend with a pseudo-element if the visible element should stay smaller. Never let extended hit areas overlap, and give decorative layers pointer-events: none so a glow or gradient never swallows the clicks meant for the control beneath it.

6. Label and Type Every Control

Every input gets a <label for> or wrapping <label>; a placeholder is never a label, and label and control share one hit target: no dead zones between a checkbox and its text. Add autocomplete with a meaningful name, and the correct type and inputmode for the keyboard. Never block paste; users paste passwords and one-time codes.

7. Errors That Announce

Keep submit enabled until the request starts, then disable with a spinner while keeping the original label. Validate on submit: mark failing fields with aria-invalid="true", point aria-describedby at the inline error text, and focus the first invalid field. Use native disabled when a native control is genuinely unavailable. Use aria-disabled="true" only when retaining focusability or discoverability is intentional; then block pointer, keyboard, and form behavior in code and style the state explicitly.

8. Accessible Names Everywhere

Icon-only buttons need a descriptive aria-label. Visible label text must appear in the accessible name. Decorative elements get aria-hidden="true", never on a focusable element.

9. Don't Rely on Color Alone

Status needs a redundant cue: icon, text, or underline alongside the color. Determine which WCAG contrast requirement applies from the content and state, then use better-colors to measure the rendered foreground/background pair. When cont

阅读完整来源 ↗