mcpField
A
accessibility-product-review

accessibility-product-review

github.com/sylphxaiTesting & quality151 installsUpdated today
Repository

About accessibility-product-review

A skill for reviewing accessibility as part of product quality across a defined user flow. It helps teams assess risks and produce prioritized findings, system fixes, validation plans, and regression checks.

Key features

  1. 01User-flow and risk assessment
  2. 02Keyboard and screen reader audit
  3. 03Prioritized accessibility findings
  4. 04Risk matrix and validation plan

Use cases

  1. 01Reviewing a critical product flow
  2. 02Finding keyboard and screen reader blockers
  3. 03Planning accessibility fixes and regression checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill accessibility-product-review

After installing, type/accessibility-product-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/accessibility-product-systems.md

Details

From the project README

Accessibility Product Review

Use this skill to make accessibility a product-quality system, not a late checklist.

Workflow

  1. Identify the user flow, platforms, input modes, assistive tech assumptions, risk level, and business-critical tasks.
  2. Read references/accessibility-product-systems.md.
  3. Audit task completion across keyboard, screen reader semantics, touch, visual contrast, focus, motion, errors, content clarity, and recovery.
  4. Separate blockers, high-impact usability issues, design-system fixes, and polish.
  5. Produce an accessibility risk matrix, fixes, validation plan, and regression checks.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not trade accessibility away for visual polish, animation, or conversion pressure.
  • Do not claim compliance from static review alone; require user-flow testing and assistive-tech checks where risk is material.
  • Do not hide inaccessible critical actions behind alternatives that are harder, paid, or support-only.

Output format

Flow/platforms:
Critical tasks:

Findings:
- P0 <blocker> -> affected users, fix, validation
- P1 <issue> -> fix, validation

System fixes:
- design token/component/pattern change

Validation:
- keyboard, screen reader, touch, contrast, motion, error, mobile/desktop

Comments

Markdown supported