accessibility

Audit web content for WCAG 2.1 accessibility conformance.

Updated Apr 14, 2026

Search Tags:#accessibility #a11y #wcag #semantic-html #screen-reader #color-contrast #keyboard-navigation

Ready to run

npx skills add https://github.com/dallay/opencode-docker --skill accessibility-dallay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/accessibility
Command: npx skills add https://github.com/dallay/opencode-docker --skill accessibility-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web content often fails to be accessible to users with disabilities. This skill provides guidance and checks to bring sites into WCAG 2.1 compliance and improve overall usability for assistive technologies.

Core Features & Use Cases

WCAG-guided audits and remediation recommendations.
Keyboard navigation and screen reader compatibility checks with actionable fixes.
Color contrast and semantic HTML validation.
Use Case: A product team audits a signup flow and fixes accessibility issues before launch.

Quick Start

Run an accessibility audit on your web project and receive actionable WCAG-compliant fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit web accessibility for WCAG 2.1 compliance?▼

Audit web accessibility for WCAG 2.1 compliance by evaluating pages, forms, navigation, and dynamic content to identify failures across keyboard accessibility, screen reader compatibility, proper landmarking, color contrast, language attributes, and ARIA usage.

What does an accessibility audit check for on a website?▼

An accessibility audit checks websites for keyboard navigation, screen reader compatibility, color contrast, semantic HTML validation, proper landmarking, language attributes, and ARIA usage to ensure assistive technology compatibility.

How do I fix keyboard navigation and screen reader compatibility issues?▼

Fix keyboard navigation and screen reader compatibility issues by applying WCAG-guided remediation recommendations that validate semantic HTML, proper landmarking, and ARIA usage to improve overall usability.

Can I audit dynamic web content and signup forms for accessibility failures?▼

Yes, you can audit dynamic web content and signup forms across web applications to identify accessibility failures and ensure WCAG 2.1 conformance before launch.

What's the best way to validate color contrast and semantic HTML for a11y?▼

The best way to validate color contrast and semantic HTML for a11y is running a WCAG-guided audit that provides actionable checks and remediation recommendations for web content.

When do I need ARIA usage and proper landmarking for web accessibility?▼

You need ARIA usage and proper landmarking for web accessibility when auditing dynamic content and navigation to ensure screen reader compatibility and WCAG 2.1 conformance.