Review Accessibility
Review interfaces for keyboard, screen-reader, low-vision, motor, cognitive, and motion barriers.
Install
npx skills add sandbaseai/workbuddy-skill --skill review-accessibilitygit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/review-accessibility ~/.claude/skills/review-accessibilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Review Accessibility Find barriers that affect real user journeys, explain their impact, and propose the smallest robust correction. Apply this Skill to source code, rendered pages, designs, screenshots, specifications, or a combination of them. ## Establish scope Before testing, record what is actually available: - critical journeys and content types - supported browsers, platforms, input modes, and viewport sizes - the requested standard and level, such as WCAG 2.2 AA - whether the evidence comes from code inspection, a live interface, assistive technology, automated checks, or static visuals If the user does not specify a standard, use WCAG 2.2 AA as an organizing reference, but do not imply a formal conformance audit. ## WorkBuddy review workflow 1. Map the essential journeys, including success, validation-error, empty, loading, timeout, and permission-denied states. 2. Inspect document language, page title, landmarks, headings, reading order, lists, tables, labels, instructions, errors, and status announcements. 3. Verify each control's accessible name, role, value, state, relationship, and programmatic description. Prefer native HTML semantics over custom ARIA. 4. Complete the journeys with keyboard alone. Check focus order and visibility, traps, skip paths, shortcuts, composite widgets, overlays, and focus restoration after dialogs or route changes. 5. Check text alternatives, captions or transcripts where applicable, color
Details
- Skill name
review-accessibility- Repository
- sandbaseai/workbuddy-skill
- Path
skills/review-accessibility/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Review Accessibility skill do?
Review interfaces for keyboard, screen-reader, low-vision, motor, cognitive, and motion barriers.
How do I install the Review Accessibility skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill review-accessibility. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Review Accessibility popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Web Design Reviewer
9sandbaseai/workbuddy-skill
Use when visually reviewing an authorized website for layout, responsive, accessibility, consistency, and interaction issues, with optional source-level fixes.
Premium UI Craft
9sandbaseai/workbuddy-skill
Use when designing or refining product interfaces, dashboards, forms, navigation, or component states; make hierarchy, interaction, accessibility, and motion intentional without defaulting to a template.
Yuwakisa Game Factor
5roby2358/skills
Factor a single-file browser game (a yuwakisaweb-style canvas prototype — one big index.js of module-level state, an immediate-mode render(), and inline event listeners) into a server-portable five-module split: GameArtifacts, GameDisplayArtifacts, GameState, GameEngine, GameUI. Use when asked to "factor/refactor this game", split a monolithic game into GameEngine/GameState/GameUI, make a prototype "portable to a server" or to yuwakisacloud, separate rules from rendering, or add seeded/reproducible RNG to a canvas game. Also use when deciding where a new game feature (terrain, skills, affixes,
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.