Predicting Accessibility Risks

Identify accessibility risks in a proposed change before implementation begins. The goal is to surface problems that would be expensive to fix later — structural choices, interaction patterns, and data model decisions that affect whether disabled users can use the feature.

This is a planning skill. It does not review implemented code (use reviewing-accessibility for that) and it does not write code. It produces a risk assessment that a developer or coder agent can act on.

Gather context

Before assessing risks, understand what is being proposed:

1. Read the plan — feature description, user story, design document, technical spec, or conversation describing the intended change.
2. Read affected code — if the change modifies existing UI, read the current implementation to understand what is already in place. Risks are relative to the starting point.
3. Identify the user interactions — what will people do with this feature? List the verbs: navigate, filter, select, submit, drag, expand, dismiss, etc. Each interaction is a potential risk surface.
4. Identify the content — what information does the feature present? Text, images, status indicators, data visualisations, real-time updates. Each content type has accessibility constraints.

Assess risks

For each risk identified, produce: