agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/elements/.agents/skills/audit-accessibility/SKILL.md

audit-accessibility

Skill115 starsChanged 55 days agoApache-2.0View on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 13
  2. Very specific:

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

    line 17
  3. Very specific:

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

    line 32
  4. Distinctive:

    Check that the test:

    line 38
  5. Very specific:

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

    line 56
  6. Distinctive:

    Verify keyboard interactions match the ARIA pattern:

    line 62
  7. Distinctive:

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

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free