accessibility

Audit web pages against WCAG 2.1 guidelines and provide remediation guidance.

7|2|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/hq-opensource/predictive-control --skill accessibility-hq-opensource
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/hq-opensource/predictive-control/tree/main/.agent/skills/accessibility
Command: npx skills add https://github.com/hq-opensource/predictive-control --skill accessibility-hq-opensource

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility to ensure content is usable by people with disabilities and to meet WCAG 2.1 guidelines.

Core Features & Use Cases

  • WCAG-aligned audits: Evaluate pages against POUR principles and WCAG 2.1 success criteria.
  • Practical remediation guidance: Provide concrete fixes for semantic structure, focus management, color contrast, keyboard navigation, and screen reader support.
  • Examples and references: Link to WCAG quick reference and best practices for reference during development and QA.

Quick Start

Use an accessibility audit to identify and fix WCAG issues on the target page to improve inclusivity.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my website for WCAG 2.1 compliance?

To audit web accessibility for WCAG 2.1 compliance, evaluate pages against POUR principles and success criteria covering headings, links, forms, color contrast, keyboard navigation, and screen reader support to identify inclusivity issues.

What is the best way to fix keyboard navigation and focus management issues?

Fixing keyboard navigation and focus management requires applying practical remediation guidance aligned with WCAG references, ensuring interactive elements are reachable and focus states are logically managed for screen reader users.

How do I improve color contrast for screen reader accessibility?

Improve color contrast by evaluating elements against WCAG 2.1 success criteria and applying concrete remediation guidance, ensuring text and interactive components meet inclusive design visual requirements.

Can I evaluate web application forms and semantic structure for inclusive design?

You can evaluate web application forms and semantic structure by auditing against WCAG 2.1 guidelines, identifying missing semantic HTML, and providing actionable remediation guidance for improved screen reader support.

Does this web accessibility audit cover both websites and web applications?

This web accessibility audit applies to both websites and web applications, evaluating conformance across headings, links, images, forms, color contrast, keyboard navigation, and screen reader support to ensure full WCAG 2.1 alignment.

Why do I need WCAG 2.1 conformance evaluation for my site?

WCAG 2.1 conformance evaluation is needed to ensure your site is usable by people with disabilities, identifying structural and navigational barriers and providing actionable fixes aligned with best practices.