predicting-accessibility-risks

Identify accessibility risks in proposed features, designs, or technical plans.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mattobee/skills --skill predicting-accessibility-risks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: predicting-accessibility-risks
Source: https://github.com/mattobee/skills/tree/main/skills/predicting-accessibility-risks
Command: npx skills add https://github.com/mattobee/skills --skill predicting-accessibility-risks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify accessibility risks in proposed features, designs, or technical plans early in the lifecycle, reducing costly fixes later by surfacing structural and interaction issues before implementation.

Core Features & Use Cases

  • Systematically assess risks for affected users (including screen reader users, keyboard-only users, and other disabled groups) and link findings to WCAG criteria.
  • Produce a structured risk assessment that documents risk, affected users, WCAG criteria, likelihood, cost to fix later, and specific mitigations.
  • Apply during planning, design reviews, or architectural decisions to guide implementation.

Quick Start

Describe the proposed change to generate an initial accessibility risk assessment before implementation.

Frequently Asked Questions about predicting-accessibility-risks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify accessibility risks in a design before implementation begins?

Assess accessibility risks by evaluating proposed features against WCAG criteria, analyzing affected users and likelihood, and documenting mitigations to produce a structured risk assessment for developer review.

What is an accessibility risk assessment and what does it include?

An accessibility risk assessment is a structured review documenting potential usability barriers, affected disabled users, relevant WCAG criteria, likelihood, cost to fix later, and specific mitigations for a proposed technical plan.

When do I need to conduct a WCAG risk assessment for a proposed feature?

Conduct a WCAG risk assessment during planning, design reviews, or architectural decisions to surface structural interaction issues early, reducing costly accessibility fixes later in the development lifecycle.

Can I evaluate keyboard-only and screen reader usability risks from a technical plan?

Yes, evaluate technical plans to systematically assess usability risks for affected users including screen reader and keyboard-only groups, linking findings to specific WCAG criteria and proposing mitigations.

What is the best way to document accessibility mitigations during a design review?

Document accessibility mitigations during a design review by generating a structured assessment that captures the risk, affected users, WCAG criteria, likelihood, cost to fix later, and targeted mitigation strategies for developer review.