How do I install the Audit Accessibility skill?

Run npx skillmds@latest add nvidia/audit-accessibility in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Audit Accessibility safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Audit Accessibility?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Audit Accessibility free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Audit Accessibility?

NVIDIA (@nvidia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Audit Accessibility by nvidia — Agent Skill

Name: Audit Accessibility
Author: NVIDIA

Audit Accessibility

Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit, verify, or fix accessibility on any component. Also use when writing or debugging .test.axe.ts files, checking tabindex management, or reviewing focus trapping behavior.

NVIDIA b3d7343 3.0 KB Updated Sep 17, 2026 2.2k repo stars

File contents

Accessibility Auditing

You MUST read projects/site/src/docs/internal/guidelines/testing-accessibility.md before proceeding.

Audit Scope

When the user invokes this skill for a component, perform the following layers of accessibility verification:

1. Static analysis (ESLint lit-a11y)

Run ESLint on the component source and check for lit-a11y rule violations:

cd projects/core && pnpm exec eslint --no-warn-ignored src/<component>/<component>.ts

Review the component template for common issues:

Missing aria-label or aria-labelledby on interactive elements
Missing role attributes on custom interactive patterns
Images without alt text
Form inputs without associated labels

2. Runtime testing (axe-core)

Verify <component>.test.axe.ts exists and covers all component variants:

Read path="projects/core/src/<component>/<component>.test.axe.ts"

Check that the test:

Imports runAxe from @internals/testing/axe
Tests every applicable status and size variant, plus the disabled state when the component supports it
Expects zero violations: expect(results.violations.length).toBe(0)
Properly creates and removes fixtures

3. ARIA pattern verification

Identify which WAI-ARIA Authoring Practices pattern the component implements. Verify:

Correct role attribute on the host or internal elements
Required ARIA states (aria-expanded, aria-selected, aria-checked, etc.)
Proper tabindex management
Focus management for composite widgets

4. Keyboard navigation

Check if the component uses the keynav reactive controller from @nvidia-elements/core/internal:

Grep pattern="keynav|keyNavigationList|KeyNav" path="projects/core/src/<component>/"

Verify keyboard interactions match the ARIA pattern:

Arrow keys for navigation within composite widgets
Enter/Space for activation
Escape for dismissal
Tab for focus entry/exit
Home/End for first/last item

5. Color contrast (theme tokens)

Check that the component uses theme tokens rather than hardcoded colors:

Grep pattern="rgb|#[0-9a-fA-F]|hsl" path="projects/core/src/<component>/<component>.css"

Flag any hardcoded color values. Verify CSS custom properties map to theme tokens that meet WCAG 2.1 AA contrast ratios (4.5:1 for normal text, 3:1 for large text).

Output

Present a structured report with:

Pass/fail status
Findings grouped by audit layer
Specific remediation steps for each finding
Commands to run the relevant tests

---name: audit-accessibilitydescription: Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit, verify, or fix accessibility on any component. Also use when writing or debugging .test.axe.ts files, checking tabindex management, or reviewing focus trapping behavior.---# Accessibility AuditingYou MUST read `projects/site/src/docs/internal/guidelines/testing-accessibility.md` before proceeding.## Audit ScopeWhen the user invokes this skill for a component, perform the following layers of accessibility verification:### 1. Static analysis (ESLint lit-a11y)Run ESLint on the component source and check for `lit-a11y` rule violations:```shellcd projects/core && pnpm exec eslint --no-warn-ignored src/<component>/<component>.ts```Review the component template for common issues:- Missing `aria-label` or `aria-labelledby` on interactive elements- Missing `role` attributes on custom interactive patterns- Images without `alt` text- Form inputs without associated labels### 2. Runtime testing (axe-core)Verify `<component>.test.axe.ts` exists and covers all component variants:```Read path="projects/core/src/<component>/<component>.test.axe.ts"```Check that the test:- Imports `runAxe` from `@internals/testing/axe`- Tests every applicable status and size variant, plus the `disabled` state when the component supports it- Expects zero violations: `expect(results.violations.length).toBe(0)`- Properly creates and removes fixtures### 3. ARIA pattern verificationIdentify which WAI-ARIA Authoring Practices pattern the component implements. Verify:- Correct `role` attribute on the host or internal elements- Required ARIA states (`aria-expanded`, `aria-selected`, `aria-checked`, etc.)- Proper `tabindex` management- Focus management for composite widgets### 4. Keyboard navigationCheck if the component uses the `keynav` reactive controller from `@nvidia-elements/core/internal`:```Grep pattern="keynav|keyNavigationList|KeyNav" path="projects/core/src/<component>/"```Verify keyboard interactions match the ARIA pattern:- Arrow keys for navigation within composite widgets- Enter/Space for activation- Escape for dismissal- Tab for focus entry/exit- Home/End for first/last item### 5. Color contrast (theme tokens)Check that the component uses theme tokens rather than hardcoded colors:```Grep pattern="rgb|#[0-9a-fA-F]|hsl" path="projects/core/src/<component>/<component>.css"```Flag any hardcoded color values. Verify CSS custom properties map to theme tokens that meet WCAG 2.1 AA contrast ratios (4.5:1 for normal text, 3:1 for large text).## OutputPresent a structured report with:1. Pass/fail status2. Findings grouped by audit layer3. Specific remediation steps for each finding4. Commands to run the relevant tests

Frequently asked questions