Accessibility review

Review public documents and web pages against accessibility standards and report actionable fixes.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill accessibility-review-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility review
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/public-sector/accessibility-review
Command: npx skills add https://github.com/vstorm-co/agenticos --skill accessibility-review-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Public documents and pages often exclude users with disabilities through issues like poor contrast, missing alt text, or unlabelled form fields, and vague findings lead to endless rework cycles. ## Core Features & Use Cases - Standards-Based Checks: Verifies heading hierarchy, alternative text, contrast ratios, link text, table headers, form labels, language attributes, colour independence, and captions or transcripts for media. - Actionable Reporting: Reports each issue with the measured value and the concrete fix, such as "Contrast 3.1:1 against a 4.5:1 requirement — darken to #4A4A4A". - Exclusion-Based Prioritisation: Orders findings by who is shut out entirely, so one unlabelled form field on an application page outranks twenty decorative images missing alt text. - Use Case: A public sector team submits a draft citizen services page and receives a prioritised list of accessibility violations with exact remediation steps before publication. ## Quick Start Review the attached public document for accessibility issues and give me a prioritised report with the specific fix for each finding.

Frequently Asked Questions about Accessibility review

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

FAQPage Schema
How do I check a web page for accessibility issues?▼

Check heading hierarchy, alternative text, contrast ratios, link text, table headers, form labels, the language attribute, colour-independent meaning, and captions or transcripts for media. Report each finding with the measured value and the specific fix.

How to write an actionable accessibility report?▼

State the measured value against the requirement and give the concrete fix, such as "Contrast 3.1:1 against a 4.5:1 requirement — darken to #4A4A4A". Vague findings like "poor contrast" only produce another review round.

What contrast ratio is required for accessible text?▼

The review checks contrast against the required ratio and reports the measured value, for example 3.1:1 against a 4.5:1 requirement. The fix specifies the exact colour adjustment needed to pass.

How should accessibility issues be prioritised?▼

Prioritise by who is shut out entirely, not by issue count. One unlabelled form field on an application page outranks twenty decorative images missing alt text because it blocks a user from completing a task.

Is a PDF accessible if it opens without errors?▼

No. A PDF that opens is not necessarily accessible, and a document that looks fine visually can still fail. Accessibility must be verified against the standard's checks rather than appearance.