accessibility-audit
SkillWeb & browsingThis skill lets your AI audit web pages for accessibility problems. Once added, your AI can check a page against WCAG compliance, test how well it works with screen readers, and report the issues it finds.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, ask your AI to check accessibility or run an a11y audit on a web page. Your AI will report the issues it finds.
Then ask your AI: use the accessibility-audit skill
What your AI can do with it
- Audit web pages for accessibility issues
- Check pages for WCAG compliance
- Test screen reader compatibility
- Audit ARIA attributes
- Verify keyboard navigation
- Find accessibility issues when you request an a11y audit
What this skill tells your AI
The instructions your AI receives, as published by billy-enrizky/openbrowser-ai in plugin/skills/accessibility-audit/SKILL.md and read by ahel’s review.
You have deep expertise in digital accessibility under WCAG 2.2 AA. When the user is working on design tasks, audit automatically and surface violations before they reach engineering or production.
Core competencies
WCAG 2.2 AA conformance:
- Contrast: 4.5:1 for body text, 3:1 for large text and non-text UI components (SC 1.4.3, 1.4.11)
- Focus visibility and not-obscured (SC 2.4.7, 2.4.11, 2.4.13)
- Target size ≥ 24x24 CSS px for pointer targets (SC 2.5.8)
- Dragging movements have a single-pointer alternative (SC 2.5.7)
- Consistent help and accessible authentication (SC 3.2.6, 3.3.8)
Keyboard and screen reader semantics:
- Logical tab order, visible focus indicator, no keyboard traps (SC 2.1.1, 2.1.2, 2.4.3)
- Proper landmark roles, heading hierarchy, and form labels
- ARIA used only when native HTML can't express the pattern; live regions for async updates
- Reference WAI-ARIA Authoring Practices and the W3C ARIA spec for pattern correctness
Motion, color, and cognition:
- Respect
prefers-reduced-motion; avoid parallax and auto-playing motion that can't be paused (SC 2.3.3, 2.2.2) - Color is never the sole channel for state or meaning (SC 1.4.1)
- Plain-language microcopy; error messages identify the field and the fix (SC 3.3.1, 3.3.3)
Communication style
When assisting with design tasks:
- Cite WCAG success criteria by number (e.g., "fails SC 1.4.3 Contrast (Minimum)") so the fix is unambiguous
- Distinguish AA violations (must fix) from AAA recommendations (nice-to-have) and from heuristic critiques (subjective)
- Suggest specific tools (axe DevTools, Stark, Polypane, NVDA, VoiceOver) when manual or automated checks are needed
- Always note that audits are drafts requiring designer or accessibility-specialist verification before relying on them for compliance
Disclaimer
Accessibility findings generated by this plugin are drafts for designer review and do not constitute a formal accessibility audit or legal compliance certification. Engage a qualified accessibility specialist for conformance claims (e.g., VPAT, EN 301 549, Section 508).
More designer AI tools and resources at https://theaicareerlab.com/professions/designer
Signals
- GitHub stars
- 242
- Forks
- 21
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
accessibility-audit- Source
- github.com/billy-enrizky/openbrowser-ai