New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Web Accessibility Audit

by warpdotdev in warpdotdev/oz-skills

Audit web applications for WCAG accessibility compliance. An agent skill from warpdotdev/oz-skills.

MITAuto-check passedFrontend & Design

Install Web Accessibility Audit

skills CLI
$ npx skills add warpdotdev/oz-skills --skill web-accessibility-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/oz-skills web-accessibility-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/oz-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/web-accessibility-audit .claude/skills/web-accessibility-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
web-accessibility-audit
GitHub stars
825
Token cost
~3.1k tokens
SKILL.md length
639 words
Files
6 (incl. scripts, references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Audit web applications for WCAG accessibility compliance. An agent skill from warpdotdev/oz-skills.

  • Works in 4 steps: Automated Testing → Manual Code Inspection → Analyze & Prioritize → …
  • Asked to run accessibility checks
  • SKILL.md covers When to Use, WCAG Principles: POUR, Conformance Levels and 12 Most Common WCAG Violations, plus 7 more sections
  • Runs Shell scripts from its folder; calls npx; reaches webaim.org and w3.org

What it does

Web Accessibility Audit is an agent skill from warpdotdev/oz-skills. Audit web applications for WCAG accessibility compliance. Use when asked to run accessibility checks, identify common violations, and provide remediation guidance.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/ARIA-patterns.md`, `references/WCAG-criteria.md` and `references/grep-patterns.md`).

It sits in Frontend & Design, covering Accessibility. The licence is MIT.

When your agent uses it

  • Asked to run accessibility checks
  • Identify common violations
  • Provide remediation guidance

Example prompts

  • “/web-accessibility-audit”

Requirements

  • Node.js
  • A Bash shell

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Automated Testing
  2. Manual Code Inspection
  3. Analyze & Prioritize
  4. Manual Testing

What it can do on your machine

Read from SKILL.md and the folder at commit 6c08c49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • webaim.org
    • w3.org
    • dequeuniversity.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Web Accessibility Audit loads about 3.1k tokens when it runs, and up to ~9.3k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 639 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from warpdotdev/oz-skills at commit 6c08c49, republished under its MIT licence (© warpdotdev). 639 words, ~3,123 tokens.

Download SKILL.mdSave it as .claude/skills/web-accessibility-audit/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
web-accessibility-audit
description
Audit web applications for WCAG accessibility compliance. Use when asked to run accessibility checks, identify common violations, and provide remediation guidance.
tags
accessibility, a11y, wcag, testing, auditing
license
MIT

Accessibility Auditor

Audit web applications for WCAG 2.0/2.1/2.2 compliance by identifying common violations and providing actionable remediation steps.

When to Use

  • User requests accessibility audit, a11y check, or WCAG compliance review
  • User mentions accessibility issues, screen readers, or keyboard navigation problems
  • User asks to check or improve accessibility for people with disabilities

WCAG Principles: POUR

PrincipleDescription
PerceivableContent can be perceived through different senses
OperableInterface can be operated by all users
UnderstandableContent and interface are understandable
RobustContent works with assistive technologies

Conformance Levels

LevelRequirementTarget
AMinimum accessibilityMust pass
AAStandard complianceShould pass (legal requirement in many jurisdictions)
AAAEnhanced accessibilityNice to have

12 Most Common WCAG Violations

Based on WebAIM Million (2021) research analyzing top 1M websites:

  1. Low Color Contrast (WCAG 1.4.3) - 86.4% of sites

    • Text < 4.5:1 contrast ratio
    • Large text < 3:1 contrast ratio
    • UI components < 3:1

  2. Missing/Inadequate Alt Text (WCAG 1.1.1) - 60.6% of sites

    • Images without alt attribute
    • Alt text with "image", "picture", "photo"
    • Empty alt on meaningful images

  3. Missing Name, Role, or Value (WCAG 4.1.2)

    • Interactive elements without accessible names
    • Custom components without proper ARIA
    • Buttons, form fields, custom widgets

  4. Keyboard Navigation Failures (WCAG 2.1.1)

    • Elements with onClick but not keyboard accessible
    • Missing focus indicators
    • Trapped keyboard focus

  5. Unlabeled Form Controls (WCAG 1.3.1, 3.3.2) - 39.6% of sites

    • Inputs without <label> or aria-label
    • Labels not programmatically associated

  6. Missing Language Attributes (WCAG 3.1.1) - 28.9% of sites

    • No lang attribute on <html>
    • Missing lang for foreign language passages

  7. Improper Heading Structure (WCAG 1.3.1, 2.4.6)

    • Skipped heading levels (h1 → h3)
    • Multiple h1s or no h1
    • Empty headings

  8. Empty Links or Poor Link Text (WCAG 2.4.4)

    • Links with "click here", "here", "read more"
    • Empty links or links with only icons

  9. Missing/Improper Focus Indicators (WCAG 2.4.7)

    • CSS removing outline without replacement
    • Insufficient focus indicator contrast

  10. Overuse/Misuse of ARIA (WCAG 4.1.2)

    • Unnecessary ARIA when native HTML works
    • Invalid ARIA attributes for roles
    • Required ARIA attributes missing

  11. Inadequate Data Table Markup (WCAG 1.3.1)

    • Tables without <th> elements
    • Missing scope or headers attributes

  12. Missing Media Captions (WCAG 1.2.1, 1.2.2)

    • Videos without captions/subtitles
    • Audio without transcripts

Audit Process

Phase 1: Automated Testing

Run ESLint (React/JSX projects):

bash
npx eslint --ext .jsx,.tsx --no-ignore --format json . > .claude/skills/a11y-auditor/eslint-results.json 2>&1 || true

Or use helper script: .claude/skills/a11y-auditor/scripts/run-eslint.sh

Run Lighthouse (production/staging):

bash
npx lighthouse https://example.com --only-categories=accessibility --output=json --output-path=./lighthouse-results.json

Check for axe-core integration:

bash
grep -r "@axe-core\|axe-core" package.json
Show full SKILL.md (258 more words)Show less
Phase 2: Manual Code Inspection

Use grep patterns from references/grep-patterns.md to search for:

  • Missing alt text
  • Keyboard navigation issues
  • Color values for contrast checking
  • ARIA issues
  • Form labels
  • Heading structure
  • Language attributes
  • Poor link text
  • Media elements

See references/grep-patterns.md for complete pattern list.

Phase 3: Analyze & Prioritize

Group findings by severity using WCAG impact levels:

Critical (fix immediately):

  • Keyboard traps
  • No focus indicators
  • Missing form labels
  • Missing alt text on functional images
  • Insufficient color contrast on interactive elements

Serious (fix before launch):

  • Missing page language
  • Improper heading structure
  • Non-descriptive link text
  • Missing skip links
  • Auto-playing media

Moderate (fix soon):

  • Missing ARIA labels on icons
  • Inconsistent navigation
  • Missing error identification
  • Missing landmark regions
Phase 4: Manual Testing

Follow references/screen-reader-guide.md for:

  • Keyboard navigation testing
  • Screen reader testing (VoiceOver, NVDA, JAWS)
  • Zoom and reflow testing
  • High contrast mode testing
  • Reduced motion testing

WCAG Pattern Examples

Perceivable
Alt Text (1.1.1)
html
<!-- ❌ Missing alt -->
<img src="chart.png">

<!-- ✅ Descriptive alt -->
<img src="chart.png" alt="Bar chart showing 40% increase in Q3 sales">

<!-- ✅ Decorative (empty alt) -->
<img src="decorative-border.png" alt="" role="presentation">
Color Contrast (1.4.3)
css
/* ❌ Low contrast (2.5:1) */
.low-contrast {
  color: #999;
  background: #fff;
}

/* ✅ Sufficient contrast (7:1) */
.high-contrast {
  color: #333;
  background: #fff;
}

Contrast requirements:

  • Normal text: 4.5:1 (AA), 7:1 (AAA)
  • Large text (18px+ or 14px+ bold): 3:1 (AA), 4.5:1 (AAA)
  • UI components: 3:1
Media Alternatives (1.2)
html
<video controls>
  <source src="video.mp4" type="video/mp4">
  <track kind="captions" src="captions.vtt" srclang="en" label="English" default>
</video>
Operable
Keyboard Navigation (2.1.1)
javascript
// ❌ Only click
element.addEventListener('click', handleAction);

// ✅ Click + keyboard
element.addEventListener('click', handleAction);
element.addEventListener('keydown', (e) => {
  if (e.key === 'Enter' || e.key === ' ') {
    e.preventDefault();
    handleAction();
  }
});
Focus Visible (2.4.7)
css
/* ❌ Never remove focus */
*:focus { outline: none; }

/* ✅ Keyboard-only focus */
:focus-visible {
  outline: 2px solid #005fcc;
  outline-offset: 2px;
}
html
<body>
  <a href="#main-content" class="skip-link">Skip to main content</a>
  <header><!-- navigation --></header>
  <main id="main-content" tabindex="-1">
    <!-- content -->
  </main>
</body>
css
.skip-link {
  position: absolute;
  top: -40px;
  left: 0;
  background: #000;
  color: #fff;
  padding: 8px 16px;
  z-index: 100;
}

.skip-link:focus {
  top: 0;
}
Reduced Motion (2.3.3)
css
@media (prefers-reduced-motion: reduce) {
  *,
  *::before,
  *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    scroll-behavior: auto !important;
  }
}
Understandable
Page Language (3.1.1)
html
<!-- ❌ No language -->
<html>

<!-- ✅ Language specified -->
<html lang="en">

<!-- ✅ Language changes -->
<p>The French word for hello is <span lang="fr">bonjour</span>.</p>
Form Labels (3.3.2)
html
<!-- ❌ No label -->
<input type="email" placeholder="Email">

<!-- ✅ Explicit label -->
<label for="email">Email address</label>
<input type="email" id="email" autocomplete="email">

<!-- ✅ With hint -->
<label for="password">Password</label>
<input type="password" id="password" aria-describedby="password-requirements">
<p id="password-requirements">
  Must be at least 8 characters with one number.
</p>
Error Handling (3.3.1)
html
<label for="email">Email</label>
<input type="email" id="email" 
       aria-invalid="true" 
       aria-describedby="email-error">
<p id="email-error" role="alert">
  Please enter a valid email address.
</p>
Robust
ARIA Usage (4.1.2)
html
<!-- ❌ Unnecessary ARIA -->
<button role="button">Submit</button>

<!-- ✅ Native HTML -->
<button>Submit</button>

<!-- ✅ ARIA when needed (custom tabs) -->
<div role="tablist" aria-label="Product information">
  <button role="tab" aria-selected="true" aria-controls="panel-1">
    Description
  </button>
  <button role="tab" aria-selected="false" aria-controls="panel-2" tabindex="-1">
    Reviews
  </button>
</div>
<div role="tabpanel" id="panel-1" aria-labelledby="tab-1">
  <!-- content -->
</div>
Live Regions (4.1.3)
html
<!-- Polite (waits for pause) -->
<div aria-live="polite" aria-atomic="true">
  Status update
</div>

<!-- Assertive (interrupts) -->
<div role="alert" aria-live="assertive">
  Error: Form submission failed
</div>
Visually Hidden Text
css
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}
html
<button>
  <svg aria-hidden="true"><!-- icon --></svg>
  <span class="visually-hidden">Delete item</span>
</button>

Output Format

Generate reports structured as:

markdown
# Accessibility Audit Report

## Summary
- Total Issues: X
- Critical: X | Serious: X | Moderate: X | Minor: X
- WCAG Level: A, AA, or AAA
- Automated Coverage: ~57% (manual testing required)

## Critical Issues (Fix Immediately)

### 1. [Issue Name] - WCAG X.X.X
**Severity:** Critical  
**Impact:** [Who is affected and how]  
**Affected:** X elements

**Locations:**
- `path/to/file.tsx:123`
- `path/to/file.tsx:456`

**Problem:**
[Brief description]

**Fix:**
```tsx
// Before
<div onClick={handleClick}>Click me</div>

// After
<button onClick={handleClick}>Click me</button>

Why: [Accessibility principle]

Serious Issues

[Same format]

Moderate Issues

[Same format]

Testing Recommendations

  1. Manual keyboard testing (Tab, Enter, Escape)
  2. Screen reader testing (see references/screen-reader-guide.md)
  3. Automated testing setup (@axe-core/react or Lighthouse CI)
  4. Color contrast validation (WebAIM Contrast Checker)

Next Steps

[Prioritized action items]


---

## Tools & Resources

### Development Tools
- **eslint-plugin-jsx-a11y** - React/JSX static analysis (~37 rules)
- **axe-core DevTools** - Browser extension for runtime testing
- **Lighthouse** - Built into Chrome DevTools

### Testing Tools  
- **@axe-core/react** - Runtime accessibility testing
- **@axe-core/playwright** - E2E test integration
- **pa11y** - Automated command-line testing

### Manual Testing
- **WebAIM Contrast Checker** - https://webaim.org/resources/contrastchecker/
- **WAVE** - Browser extension for visual feedback
- **Screen readers** - NVDA (Windows), VoiceOver (macOS), JAWS

### Reference Docs
- `references/WCAG-criteria.md` - All WCAG 2.1 success criteria
- `references/ARIA-patterns.md` - Common ARIA patterns and examples
- `references/screen-reader-guide.md` - Testing commands and scenarios
- `references/grep-patterns.md` - Search patterns for code audits

### References
- [WebAIM Million](https://webaim.org/projects/million/) - Annual analysis of top 1M websites (violation statistics)
- [WCAG 2.1 Quick Reference](https://www.w3.org/WAI/WCAG21/quickref/) - Interactive WCAG guide
- [WAI-ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/) - Official ARIA patterns
- [Deque axe Rules](https://dequeuniversity.com/rules/axe/) - All axe-core rules explained
- [jsx-a11y Rules](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y#supported-rules) - ESLint accessibility rules

---

## Important Notes

- Automated tools catch 30-57% of issues; manual testing required
- Pages with ARIA average 41% more errors than without
- Always test with actual assistive technology when possible
- Focus on critical issues first (keyboard, screen readers, contrast)
- Document deliberate accessibility decisions
- Test on multiple browsers and devices
- Include users with disabilities in testing when possible

## Common Pitfalls to Avoid

1. Relying solely on automated testing
2. Using ARIA when native HTML suffices
3. Removing focus indicators
4. Using positive tabindex values
5. Color as only means of conveying information
6. Keyboard traps in modals/dialogs
7. Non-descriptive link text
8. Missing or incorrect heading hierarchy
9. Unlabeled form controls
10. Missing language attributes

© warpdotdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in .agents/skills/web-accessibility-audit of warpdotdev/oz-skills.

  • SKILL.md
  • references/ARIA-patterns.md
  • references/WCAG-criteria.md
  • references/grep-patterns.md
  • references/screen-reader-guide.md
  • scripts/run-eslint.sh

Open the folder on GitHubat commit 6c08c49

Compare with similar skills

Web Accessibility Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Web Accessibility Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Web Accessibility Audit this skillwarpdotdev/oz-skills825—~3.1kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.4k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17810 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 98 repos~308 tokens
    Frontend & DesignAuto-check passed

  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed

  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed

  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.4k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed

  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 10 repos~610 tokens
    Frontend & DesignAuto-check passed

  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.4k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from warpdotdev/oz-skills

All 13 skills in this repo

  • SEO Aeo Audit

    warpdotdev/oz-skills

    Optimize for search engine visibility, ranking, and AI citations.

    825 GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Webapp Testing

    warpdotdev/oz-skills

    Test local web applications with Playwright. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~914 tokensUpdated 1 mo ago
    Auto-check passed

  • GitHub Bug Report Triage

    warpdotdev/oz-skills

    Triage GitHub bug reports for actionability. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Analysis Artifacts

    warpdotdev/oz-skills

    Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • CI Fix

    warpdotdev/oz-skills

    Diagnose and fix GitHub Actions CI failures. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~790 tokensUpdated 1 mo ago
    Auto-check passed

  • Create Pull Request

    warpdotdev/oz-skills

    Create a GitHub pull request following project conventions. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Web Accessibility Audit

What does Web Accessibility Audit do?

Audit web applications for WCAG accessibility compliance. An agent skill from warpdotdev/oz-skills. Web Accessibility Audit is an agent skill from warpdotdev/oz-skills. Audit web applications for WCAG accessibility compliance.

When should I use Web Accessibility Audit?

Web Accessibility Audit fits situations like: asked to run accessibility checks; identify common violations; provide remediation guidance.

How do I install Web Accessibility Audit in Claude Code?

Run `npx skills add warpdotdev/oz-skills --skill web-accessibility-audit -a claude-code`. Or copy the skill folder (.agents/skills/web-accessibility-audit in warpdotdev/oz-skills) into .claude/skills/web-accessibility-audit in your project. Claude Code loads it when a task matches its description.

How do I install Web Accessibility Audit in Codex?

Run `npx skills add warpdotdev/oz-skills --skill web-accessibility-audit -a codex`. Or copy the skill folder (.agents/skills/web-accessibility-audit in warpdotdev/oz-skills) into .agents/skills/web-accessibility-audit in your project. Codex loads it when a task matches its description.

Can I use Web Accessibility Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/oz-skills --skill web-accessibility-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/web-accessibility-audit, .gemini/skills/web-accessibility-audit, .github/skills/web-accessibility-audit and .opencode/skills/web-accessibility-audit in your project.

What does Web Accessibility Audit need to run?

Going by SKILL.md and its folder, Web Accessibility Audit needs a shell for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js; A Bash shell.

Does Web Accessibility Audit access the network?

SKILL.md names 4 domains. In commands or code: webaim.org, w3.org, dequeuniversity.com and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Web Accessibility Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Web Accessibility Audit use?

Web Accessibility Audit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Web Accessibility Audit use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.2k tokens, read only when the agent opens those files.

What are the alternatives to Web Accessibility Audit?

Skills that share tags, products or a category with Web Accessibility Audit: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Web Accessibility Audit?

warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-skills, which has 825 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 15, 2026.

Source: warpdotdev/oz-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.