masup9/a11y-specialist-skills/reviewing-a11y

日本語版 (Japanese)

Accessibility Review

Identify the review target, find accessibility issues by following the matching reference guide, and report them by severity.

Step 1: Identify Review Target

If you cannot decide, ask in one line whether to review a URL, file paths, or a design.

Step 2: Look Up the Judgment Lines in the Knowledge Base

Once you identify the target, and before looking at the code or page, align your findings with a11y-knowledge.

1. List the components that appear in the target by ARIA role (button, dialog, combobox, and so on).
2. Use index-by-component.md to find the success criteria that apply to each role. When reviewing a layout or a whole page, also pick the "Whole page" and "Multiple pages" criteria from index-by-criterion.md.
3. For each criterion found, read "Judgment lines" and "When building" in ../a11y-knowledge/references/criteria/<number>.md before writing a finding. Do not report items excluded from WCAG applicability as WCAG failures. Report items the knowledge base treats as best practice as improvement candidates without assigning a success criterion, such as a missing name on the dialog itself.
4. When a finding is based on an [Our interpretation] judgment line (an operational interpretation), say so in the finding (for example, "[Our interpretation] judgment line; the project may override it"). [Understanding] judgment lines need no such note.

The knowledge base is referenced by the relative path ../a11y-knowledge/. It resolves when installed as a plugin. When installed by symlinking individual skill directories, link a11y-knowledge as well. If it does not resolve, skip this step and write "knowledge base not consulted" in the report.

Step 3: Load the Guide and Review

Read the guide from the Step 1 table in the user's language (.ja.md for Japanese, .md for English) and execute its process in this agent. Use one guide per target type; do not mix them.

Use sub-agents only when the user explicitly requests parallel review, delegation, or division across multiple targets. Give each agent one target type with its guide and target, wait for every result, remove duplicates, and return one report. If sub-agents are unavailable, review the targets sequentially.

Severity

All guides assign severity with this table. Severity reflects the impact on users and is independent of the WCAG level (A/AA).

Mark findings that are not WCAG requirements as "best practice" and do not attach a success criterion.

Step 4: Return Results

1. Present the findings in the guide's output format. Separate what was verified from what could not be verified (sent to manual verification). Do not turn missing evidence into a conclusive finding.
2. If useful, offer to review another target type (e.g., "Would you like me to review the code implementation next?").