skills.rest
kernex-dev
kernex-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

accessibility-auditor

Audit web interfaces for WCAG 2.2 compliance using axe-core and Lighthouse.

1|Updated Mar 6, 2026
Search Tags:#accessibility#a11y#wcag#lighthouse#contrast#screen-reader#axe-core
One-click install
npx skills add https://github.com/kernex-dev/kernex-agent --skill accessibility-auditor-kernex-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/kernex-dev/kernex-agent/tree/main/builtins/accessibility-auditor
Command: npx skills add https://github.com/kernex-dev/kernex-agent --skill accessibility-auditor-kernex-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams find and prioritize accessibility failures that block or hinder users with disabilities by combining automated scans with manual keyboard and screen reader checks so issues are detected before release.

Core Features & Use Cases

  • Automated Baseline: Run axe-core and Lighthouse accessibility audits and produce WCAG-referenced findings.
  • Interaction Testing: Guide keyboard navigation, focus management, and screen reader testing (VoiceOver, NVDA, TalkBack).
  • Visual & Contrast Checks: Evaluate color contrast, zoom/resize behavior, reduced motion, and high-contrast scenarios.
  • Use Case: Use during pre-launch QA or when addressing screen reader bug reports to produce prioritized, actionable remediation steps.

Quick Start

Run an axe-core and Lighthouse accessibility audit against your running site at http://localhost:3000 and follow the generated report and checklist to remediate issues by severity.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema
How do I run a WCAG 2.2 compliance audit on my web application?▼

Run a WCAG 2.2 compliance audit by executing automated axe-core and Lighthouse scans against your running localhost site to generate a prioritized checklist of accessibility failures referenced by WCAG criteria.

What is the best way to test screen reader compatibility during an accessibility sprint?▼

Test screen reader compatibility by combining automated axe-core scans with guided manual testing across VoiceOver, NVDA, and TalkBack to evaluate keyboard navigation and focus management issues.

Do I need node and npx installed to check my web UI for accessibility issues?▼

Yes, you need node and npx installed locally with read access to your project sources to execute the automated Lighthouse and axe-core accessibility audits against your web front-end.

Can I evaluate color contrast and reduced motion behavior for WCAG compliance?▼

Yes, you can evaluate color contrast ratios, zoom and resize behavior, reduced motion preferences, and high-contrast scenarios to identify visual accessibility failures during pre-launch checks.

When should I use axe-core and Lighthouse for accessibility remediation?▼

Use axe-core and Lighthouse during pre-launch QA checks or when addressing screen reader bug reports to produce prioritized, actionable remediation steps for single-page applications.

Related Skills

Explore More Software Engineering Skills→
DYAI2025DYAI2025
3

webapp-testing

Automate local web app testing with Playwright and capture debugging artifacts.

Community
Advanced
cy-walicy-wali

accessibility-review

Audit Figma designs and pages for WCAG 2.1 AA compliance.

Community
Intermediate
pedronauckpedronauck
567

a11y-testing

Automate accessibility testing with jest-axe and Playwright axe-core.

Community
Intermediate
altrupetsaltrupets

Accessibility (a11y)

Implement WCAG accessibility features in Flutter apps with semantic widgets and screen reader support.

Official
Intermediate