common-accessibility

Validate web UIs for WCAG 2.2 AA compliance with semantic HTML and ARIA.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill common-accessibility-vsf-qc-tts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: common-accessibility
Source: https://github.com/VSF-QC-TTS/vf-qc-copilot/tree/main/.agents/skills/common/common-accessibility
Command: npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill common-accessibility-vsf-qc-tts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers enforce WCAG 2.2 AA compliance for web UIs, ensuring accessibility for users with disabilities.

Core Features & Use Cases

  • Semantic HTML: Enforce proper use of semantic HTML elements for better accessibility.
  • ARIA Roles: Use ARIA roles sparingly to supplement missing semantic information.
  • Keyboard Navigation: Ensure all interactive elements are reachable and operable via keyboard.
  • Color & Contrast: Maintain sufficient color contrast for readability.
  • Touch & Pointer Targets: Set minimum size for interactive elements for ease of use.
  • Images & Media: Provide descriptive alt text for images and media content.
  • Testing: Utilize accessibility testing tools to ensure compliance.
  • Use Case: Integrate this Skill into your web development workflow to ensure your web applications meet accessibility standards.

Quick Start

Run the common-accessibility skill on your web UI codebase to enforce WCAG 2.2 AA compliance.

Frequently Asked Questions about common-accessibility

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

FAQPage Schema
How do I ensure my web UI meets WCAG 2.2 AA accessibility standards?

To ensure WCAG 2.2 AA accessibility, validate your web UI for proper semantic HTML, ARIA roles, keyboard navigation, color contrast, touch target sizes, and descriptive alt text for media.

What is the best way to use ARIA roles for web accessibility?

The best way to use ARIA roles for web accessibility is sparingly, applying them only to supplement missing semantic information when native HTML elements cannot provide the required context.

How do I check keyboard navigation and color contrast for screen reader compatibility?

Check keyboard navigation and color contrast for screen reader compatibility by verifying all interactive elements are operable via keyboard and maintaining sufficient color contrast ratios for readability.

Does semantic HTML alone satisfy web development accessibility requirements?

Semantic HTML provides a strong foundation for web accessibility, but you must also validate keyboard operability, touch target sizes, and color contrast to achieve full WCAG 2.2 AA compliance.

What are the touch target size requirements for accessible web development?

Accessible web development requires setting minimum sizes for interactive touch and pointer targets, ensuring ease of use and operability for users navigating your web UI.

When should I run accessibility testing tools during my web development workflow?

Run accessibility testing tools during your web development workflow after enforcing semantic HTML and ARIA roles, utilizing them to validate WCAG 2.2 AA compliance and identify remaining UI barriers.