accessibility

Audit and remediate web accessibility issues for WCAG 2.2 compliance.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/aymenhamoudii/digitn-website --skill accessibility-aymenhamoudii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/aymenhamoudii/digitn-website/tree/main/.qwen/skills/accessibility
Command: npx skills add https://github.com/aymenhamoudii/digitn-website --skill accessibility-aymenhamoudii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many websites fail to meet WCAG 2.2 accessibility requirements, causing barriers for people who rely on screen readers, keyboard navigation, high-contrast modes, or reduced motion settings; this Skill provides clear guidance to identify and prioritize those issues so teams can make interfaces perceivable, operable, understandable, and robust.

Core Features & Use Cases

  • WCAG 2.2 Guidance: Pinpoint required success criteria (A/AA/AAA) and explain how to meet them for common patterns like forms, navigation, and media.
  • Audit & Fix Recommendations: Deliver prioritized findings, ARIA role corrections, keyboard and focus management fixes, color contrast thresholds, and testing checklists for developers and QA.
  • Patterns & Testing: Provide copy-paste patterns and manual testing steps for modals, skip links, live regions, and form error handling to speed implementation and verification.
  • Use Case: Turn a Lighthouse or axe report into a prioritized remediation plan with example markup and concise developer instructions.

Quick Start

Run an accessibility audit for https://example.com and return prioritized WCAG 2.2 failures, explanations, and actionable code or markup fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I fix WCAG 2.2 accessibility issues found in a Lighthouse audit?

To fix WCAG 2.2 accessibility issues from a Lighthouse audit, you need a remediation plan mapping failures to specific success criteria, ARIA corrections, and keyboard focus management steps. This process turns raw audit reports into prioritized developer-ready code fixes.

What WCAG 2.2 color contrast thresholds do I need to meet for web accessibility?

WCAG 2.2 color contrast thresholds require specific visual ratio limits to ensure text is perceivable. Meeting these thresholds involves adjusting CSS color values to provide sufficient contrast for users relying on high-contrast modes.

How do I add ARIA roles and keyboard navigation to a modal dialog?

Adding ARIA roles and keyboard navigation to a modal dialog requires implementing specific focus management patterns and manual testing steps. This ensures screen readers correctly interpret the UI and users can navigate without a mouse.

Does this accessibility auditing approach work for single-page applications?

Yes, this accessibility auditing approach works for single-page applications by evaluating dynamic content updates, JavaScript interactions, and UI components. It ensures WCAG 2.2 compliance for keyboard navigation and screen reader support across dynamic views.

What is the best way to prioritize web accessibility remediation for developers?

The best way to prioritize web accessibility remediation is mapping issues to WCAG 2.2 success criteria levels (A/AA/AAA) and generating copy-paste code patterns. This provides developers with concise, actionable instructions for immediate fixes.

Why does my screen reader fail to announce dynamic form errors?

Screen readers fail to announce dynamic form errors when accessibility markup lacks proper ARIA live regions or error handling patterns. Fixing this requires implementing specific ARIA attributes and focus management to alert users of content updates.