skills.rest
BrunoAlpezdev
BrunoAlpezdevCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web interfaces against WCAG 2.2 and Lighthouse accessibility findings.

Updated Apr 11, 2026
Search Tags:#accessibility#screen reader#keyboard navigation#wcag 2.2#color contrast#a11y audit#aria patterns
One-click install
npx skills add https://github.com/BrunoAlpezdev/lluvia-de-ideas --skill accessibility-brunoalpezdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/BrunoAlpezdev/lluvia-de-ideas/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/BrunoAlpezdev/lluvia-de-ideas --skill accessibility-brunoalpezdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and fix common accessibility barriers that prevent people with disabilities from using websites effectively, including keyboard-only navigation, screen reader compatibility, and WCAG 2.2 compliance gaps.

Core Features & Use Cases

  • WCAG 2.2 audit guidance: Review content against POUR principles (Perceivable, Operable, Understandable, Robust) and map issues to success criteria.
  • Concrete remediation patterns: Apply practical fixes for alt text, color contrast, focus handling, skip links, form labeling, error announcements, and ARIA usage.
  • Testing support: Validate fixes with tools like Lighthouse, axe-core, and manual checks for keyboard, focus visibility, zoom, and reduced motion.
  • Use case: You’re launching a new product page and need to ensure keyboard navigation works end-to-end, screen readers announce errors correctly, and focus states are visible and not obscured.

Quick Start

Ask the AI to run an accessibility audit using WCAG 2.2 AA targets for your page and provide a prioritized checklist of fixes for keyboard access, focus visibility, labels/errors, and contrast.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I run a WCAG 2.2 accessibility audit on my web interface?▼

To run a WCAG 2.2 accessibility audit, review your interface against POUR principles and map issues to conformance levels A, AA, or AAA. This generates a prioritized checklist for fixing keyboard access, focus visibility, labels, and contrast.

What is the best way to fix screen reader compatibility and keyboard navigation issues?▼

Fix screen reader compatibility and keyboard navigation by applying concrete remediation patterns for focus handling, skip links, and ARIA usage. Validate these fixes using manual checks and tools like Lighthouse and axe-core to ensure end-to-end operability.

How do I ensure form errors and live notifications are announced correctly for assistive technologies?▼

Ensure form errors and live notifications are announced correctly by applying specific ARIA patterns and error announcement techniques. This satisfies WCAG 2.2 requirements by making dynamic content updates perceivable for screen reader users.

Can I use this to check color contrast and motion preferences for visual accessibility?▼

Yes, you can check color contrast ratios and motion timing preferences to meet visual accessibility standards. The audit provides actionable remediation examples and testing checklists to verify that contrast outcomes and reduced motion settings comply with WCAG targets.

What accessibility testing checklists should I use to verify zoom and focus outcomes?▼

Use testing checklists that validate keyboard navigation, screen reader output, zoom functionality, and focus visibility. These checklists help verify that your interface meets POUR-structured guidance and achieves the desired WCAG 2.2 AA conformance level.

Why does my web interface fail Lighthouse accessibility checks for missing labels and focus management?▼

Lighthouse accessibility checks fail when interfaces lack proper form labeling, visible focus states, or valid ARIA patterns. Resolve these barriers by applying targeted remediation examples for alt text, skip links, and error announcements to achieve a usable experience.

Related Skills

Explore More Design & Creative Skills→
addyosmaniaddyosmani
2.6k

accessibility

Audit web accessibility and improve WCAG 2.1 conformance across web content.

Community
Advanced
Higashi-KotaHigashi-Kota

a11y

Audits UI components for WCAG 2.2 AA and ARIA compliance.

Community
Intermediate
mtsatryanmtsatryan
1

accessibility-auditor

Audit web applications for WCAG compliance using axe-core and Playwright.

Community
Advanced
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate