skills.rest
brandonjjon
brandonjjonCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Identify web page accessibility issues and guide WCAG 2.2 remediation.

Updated Apr 21, 2026
Search Tags:#accessibility#a11y#lighthouse#screen-readers#keyboard-navigation#wcag-22
One-click install
npx skills add https://github.com/brandonjjon/astro-starter-cf --skill accessibility-brandonjjon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/brandonjjon/astro-starter-cf/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/brandonjjon/astro-starter-cf --skill accessibility-brandonjjon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web accessibility gaps prevent users with disabilities from accessing content, and many sites fail WCAG 2.2 guidelines. This Skill provides structured guidance to audit, understand, and close those gaps to meet inclusive design standards.

Core Features & Use Cases

  • WCAG 2.2-compliant audit framework based on POUR (Perceivable, Operable, Understandable, Robust) and Lighthouse audits.
  • Practical code patterns and checklists via references to real-world examples (including A11Y-PATTERNS.md).
  • Use cases include improving keyboard navigation, color contrast, screen reader compatibility, and semantic markup across web pages.

Quick Start

Assess a page for accessibility issues and apply recommended fixes using the provided patterns and checklists.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a web page for WCAG 2.2 compliance issues?▼

To audit a web page for WCAG 2.2 compliance, evaluate it against the POUR framework to identify gaps in perceivable, operable, understandable, and robust criteria, then verify improvements using Lighthouse.

What is the best way to fix keyboard navigation and screen reader compatibility on my website?▼

Fix keyboard navigation and screen reader compatibility by applying semantic markup and established A11Y patterns to remediate identified operability issues, ensuring all interactive elements are accessible without a mouse.

How does the POUR framework apply to web accessibility remediation?▼

The POUR framework structures web accessibility remediation by dividing issues across Perceivable, Operable, Understandable, and Robust categories, guiding targeted fixes for color contrast, keyboard access, and assistive technology support.

Can I use Lighthouse to verify color contrast and semantic markup fixes?▼

You can use Lighthouse to verify color contrast and semantic markup fixes by running audits on the corrected web page to confirm that the changes meet WCAG 2.2 guidelines and support assistive technologies.

What are common limitations when relying solely on automated accessibility checkers?▼

Automated accessibility checkers often miss contextual keyboard navigation barriers and nuanced screen reader compatibility issues, requiring manual POUR framework audits and A11Y pattern validation to ensure full WCAG 2.2 compliance.

Related Skills

Explore More Software Engineering Skills→
PaulRBergPaulRBerg
6

web-design-guidelines

Evaluate HTML, CSS, and JavaScript files against current Web Interface Guidelines.

Community
Intermediate
anolilabanolilab
214

accessibility

Audit web interfaces against WCAG 2.2 accessibility standards.

Official
Intermediate
marcusagmmarcusagm
4

lint-and-validate

Run linting, type checking, and security audits across Node.js/TypeScript and Python projects.

Community
Intermediate
sebafermanellisebafermanelli
1

sfermanelli-accessibility

Audit frontend code for accessibility gaps and propose WCAG remediation fixes.

Community
Advanced