accessibility

Automate accessibility audits for web components using ESLint and axe-core.

33|9|Updated Mar 2, 2026

Search Tags:#accessibility #a11y #ARIA #WCAG #audit #web components

Ready to run

npx skills add https://github.com/NVIDIA/elements --skill accessibility-nvidia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/NVIDIA/elements/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/NVIDIA/elements --skill accessibility-nvidia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eslint, lit-a11y, axe-core, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complex task of auditing accessibility in web components, ensuring compliance with WCAG and ARIA standards.

Core Features & Use Cases

Static Analysis: Checks for common accessibility issues in the component source code.
Runtime Testing: Validates component behavior through automated tests.
ARIA Pattern Verification: Ensures correct implementation of ARIA roles and states.
Keyboard Navigation: Validates keyboard accessibility for interactive components.
Color Contrast: Checks color contrast ratios for readability compliance.
Use Case: When developing a web application, use this Skill to automatically audit and improve the accessibility of all components.

Quick Start

Run the accessibility skill to audit a component and receive a detailed report on accessibility issues.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit web components for WCAG and ARIA compliance?▼

To audit web components for WCAG and ARIA compliance, you can automate the process using static analysis, runtime testing, and ARIA pattern verification. This ensures your components meet accessibility standards thoroughly.

What is automated accessibility testing for web components?▼

Automated accessibility testing for web components is the process of validating keyboard navigation, color contrast, and ARIA roles without manual checks. It utilizes tools like axe-core and ESLint to detect compliance issues.

How do I check color contrast and keyboard navigation in web components?▼

You check color contrast and keyboard navigation in web components by running automated runtime tests. These tests validate color contrast ratios for readability and ensure interactive elements are fully keyboard accessible.

Can I use ESLint and axe-core to automate ARIA pattern verification?▼

Yes, you can use ESLint and axe-core to automate ARIA pattern verification in web components. These dependencies perform static analysis and runtime testing to ensure correct implementation of ARIA roles and states.

What is the best way to find common accessibility issues in component source code?▼

The best way to find common accessibility issues in component source code is through static analysis. By scanning the source directly, this approach catches errors early before progressing to runtime testing and behavior validation.