accessibility-expert

Audit web interfaces for WCAG 2.1/2.2 compliance and generate prioritized remediation plans.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hvngroup/directus_b2b_crm --skill accessibility-expert-hvngroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-expert
Source: https://github.com/hvngroup/directus_b2b_crm/tree/main/.agent/skills/accessibility-expert
Command: npx skills add https://github.com/hvngroup/directus_b2b_crm --skill accessibility-expert-hvngroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web accessibility gaps in modern interfaces block users with disabilities from effectively navigating, reading content, or completing tasks. This Skill provides expert guidance to identify, prioritize, and remediate WCAG 2.1/2.2, ARIA, keyboard, and screen reader issues, enabling inclusive experiences.

Core Features & Use Cases

  • WCAG conformance assessment and violation diagnosis across pages and components.
  • WAI-ARIA implementation guidance, semantic HTML recommendations, and keyboard-navigation enhancements.
  • Manual and automated testing strategy including axe-core/Pa11y/Lighthouse integration, and developer-friendly remediation plans.
  • Use Case: Audit a product page for missing labels, inaccessible landmarks, and non-descriptive link text, then produce a prioritized fix list.

Quick Start

Run an accessibility assessment on a web page and generate a prioritized remediation plan.

Frequently Asked Questions about accessibility-expert

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

FAQPage Schema
How do I check my web app for WCAG 2.1 and 2.2 compliance issues?

Run an accessibility assessment to diagnose WCAG 2.1 and 2.2 violations across pages and components, validate ARIA usage, verify keyboard navigation, and generate a prioritized remediation plan.

What's the best way to fix WAI-ARIA implementation and keyboard navigation gaps?

Fix WAI-ARIA and keyboard navigation gaps by applying semantic HTML recommendations, validating ARIA roles and states, and enhancing keyboard accessibility to ensure interactive components are fully operable.

Can I integrate automated accessibility testing tools like axe-core and Lighthouse into my audit?

Yes, you can integrate automated testing tools like axe-core, Pa11y, and Lighthouse into your audit to establish a manual and automated testing strategy that identifies interface issues efficiently.

Does this accessibility audit work for single page applications and marketing sites?

Yes, this accessibility audit applies to product development, design reviews, and code audits across web apps, SPAs, and marketing sites, checking for missing labels, inaccessible landmarks, and non-descriptive link text.

How do I audit a product page for missing labels and inaccessible landmarks?

Audit a product page by reviewing the interface for missing labels, inaccessible landmarks, and non-descriptive link text, then produce a prioritized fix list to remediate the identified accessibility violations.

When do I need to perform a manual screen reader testing strategy?

You need manual screen reader testing when automated tools cannot fully verify semantic HTML, ARIA usage, and keyboard navigation, ensuring users with disabilities can effectively read content and complete tasks.