accessibility

Audit web pages for WCAG 2.1 accessibility issues and provide improvement recommendations.

Updated Mar 6, 2026

Search Tags:#accessibility #a11y #web development #compliance #wcag #ux

Ready to run

npx skills add https://github.com/gooftroop/Armoury --skill accessibility-gooftroop

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web content usable by everyone, regardless of ability, by auditing and improving adherence to accessibility standards.

Core Features & Use Cases

WCAG Compliance: Provides guidelines and checks based on the Web Content Accessibility Guidelines (WCAG) 2.1.
POUR Principles: Organizes checks around Perceivable, Operable, Understandable, and Robust principles.
Testing: Includes checklists for automated and manual testing, along with screen reader commands.
Use Case: When developing a new website feature, use this Skill to ensure it meets WCAG AA standards, making it accessible to users with visual, auditory, motor, or cognitive impairments.

Quick Start

Audit the provided web page for accessibility issues based on WCAG 2.1 guidelines.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit my web page for WCAG 2.1 compliance?▼

Audit web accessibility by evaluating your page against WCAG 2.1 guidelines, focusing on Perceivable, Operable, Understandable, and Robust principles. This includes detailed checks for text alternatives, color contrast, keyboard navigation, focus visibility, form labeling, error handling, and ARIA usage.

What is the best way to test keyboard navigation and focus visibility for accessibility?▼

The best way to test keyboard navigation and focus visibility is using the provided manual testing checklists. These checklists evaluate operability by verifying that users can navigate interactive elements using only a keyboard and that focus indicators are clearly visible.

How does ARIA usage affect web accessibility for screen reader users?▼

ARIA usage affects web accessibility by providing semantic information to screen readers when native HTML is insufficient. Proper ARIA implementation ensures that dynamic content and complex UI components are understandable and operable for users relying on assistive technologies.

Can I use automated testing alone to verify WCAG AA standards for my website feature?▼

You cannot rely on automated testing alone to verify WCAG AA standards. While automated tools catch many technical errors, manual testing and screen reader command references are required to ensure broad usability for users with visual, auditory, motor, or cognitive impairments.

When do I need to check color contrast and text alternatives during web development?▼

You need to check color contrast and text alternatives during web development whenever adding visual content. These checks ensure that information is perceivable by users with visual impairments, meeting WCAG 2.1 requirements for text alternatives and sufficient color contrast ratios.