skills.rest
nicoarbelaez
nicoarbelaezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Audit web pages for WCAG 2.2 gaps and generate remediation guidance.

Updated May 12, 2025
Search Tags:#accessibility#a11y#wcag#lighthouse#screen-reader#color-contrast#keyboard-navigation
One-click install
npx skills add https://github.com/nicoarbelaez/portfolio --skill accessibility-nicoarbelaez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/nicoarbelaez/portfolio/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/nicoarbelaez/portfolio --skill accessibility-nicoarbelaez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility to ensure content is usable by people with disabilities and compliant with WCAG 2.2 guidelines.

Core Features & Use Cases

  • Accessibility audits using WCAG 2.2 criteria and Lighthouse to identify issues such as missing alt text, color-contrast failures, keyboard traps, and semantic markup gaps.
  • Remediation guidance with prioritized, actionable fixes and references to best practices in A11Y patterns.
  • Use Case: When a product requires WCAG compliance before launch, run an audit and produce an actionable remediation plan for developers and content authors.

Quick Start

Audit a target page for WCAG 2.2 accessibility gaps and generate a prioritized remediation list.

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?▼

You can audit public websites and internal dashboards for WCAG 2.2 accessibility gaps to identify issues across desktop and mobile, generating a prioritized list of actionable remediation steps for developers and content authors.

What is the best way to fix color-contrast and keyboard-navigation failures?▼

Fixing color-contrast and keyboard-navigation failures involves applying WCAG 2.2 audit results to generate prioritized remediation guidance, providing developers with actionable fixes and references to best practices in A11Y patterns.

Can I use Lighthouse audit tooling to check internal dashboards for accessibility gaps?▼

Yes, you can apply Lighthouse audit tooling and WCAG 2.2 criteria to internal dashboards and content pages to detect semantic markup gaps, keyboard traps, and missing alt text across both desktop and mobile environments.

Does this process generate remediation guidance for content authors and developers?▼

Yes, the audit process generates prioritized, actionable remediation guidance specifically tailored for both developers and content authors, referencing best practices in A11Y patterns to resolve identified WCAG 2.2 accessibility issues.

When do I need to run an accessibility audit before launch?▼

You need to run an accessibility audit before launch when a product requires WCAG 2.2 compliance, ensuring content is usable by people with disabilities by identifying and resolving issues like missing alt text and semantic markup gaps.

Related Skills

Explore More Software Engineering Skills→
AlvaGonzAlvaGonz

performance

Identify web performance bottlenecks and measure improvements with Lighthouse metrics.

Community
Advanced
brandonjjonbrandonjjon

accessibility

Identify web page accessibility issues and guide WCAG 2.2 remediation.

Community
Advanced
mathemagiemathemagie

accessibility

Audit web accessibility against WCAG 2.1 standards and generate remediation plans.

Community
Basic
airoweairowe
14

Accessibility Audit Skill

Audit web projects for WCAG 2.1 violations using axe-core and eslint-plugin-jsx-a11y.

Community
Advanced