Index of every page on this site: llms.txt
All skills
wshobson avatar

/wcag-audit-patterns

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

Use this Skill: https://skilld.dev/gh/wshobson/agents/wcag-audit-patterns

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈61 tokens for metadata: the name and description. ≈560 when used: this file. ≈2.5k more on demand in 1 file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈244 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

WCAG Audit Patterns

Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.

When to Use This Skill

  • Conducting accessibility audits
  • Fixing WCAG violations
  • Implementing accessible components
  • Preparing for accessibility lawsuits
  • Meeting ADA/Section 508 requirements
  • Achieving VPAT compliance

Core Concepts

1. WCAG Conformance Levels

Level Description Required For
A Minimum accessibility Legal baseline
AA Standard conformance Most regulations
AAA Enhanced accessibility Specialized needs

2. POUR Principles

Perceivable:  Can users perceive the content?
Operable:     Can users operate the interface?
Understandable: Can users understand the content?
Robust:       Does it work with assistive tech?

3. Common Violations by Impact

Critical (Blockers):
├── Missing alt text for functional images
├── No keyboard access to interactive elements
├── Missing form labels
└── Auto-playing media without controls

Serious:
├── Insufficient color contrast
├── Missing skip links
├── Inaccessible custom widgets
└── Missing page titles

Moderate:
├── Missing language attribute
├── Unclear link text
├── Missing landmarks
└── Improper heading hierarchy

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

Do's

  • Start early - Accessibility from design phase
  • Test with real users - Disabled users provide best feedback
  • Automate what you can - 30-50% issues detectable
  • Use semantic HTML - Reduces ARIA needs
  • Document patterns - Build accessible component library

Don'ts

  • Don't rely only on automated testing - Manual testing required
  • Don't use ARIA as first solution - Native HTML first
  • Don't hide focus outlines - Keyboard users need them
  • Don't disable zoom - Users need to resize
  • Don't use color alone - Multiple indicators needed

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides standard educational content and guidelines for WCAG 2.2 accessibility audits. It contains only structural documentation, markdown code snippets, and common command-line tool references with no actionable security concerns.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago
  • Testing
  • wcag
  • accessibility
  • a11y
  • auditing
  • semantic-html
  • aria
  • compliance
  • ada
  • keyboard-navigation

README badge

README badge for wshobson/agents/wcag-audit-patterns

Conducts WCAG 2.2 accessibility audits with patterns for testing, remediation, and conformance verification. Covers the POUR principles, common violations by severity, and best practices for fixing accessibility issues in web applications.

Generated from the current SKILL.md.

Does this skill cover all WCAG 2.2 levels?
Yes. The skill covers WCAG 2.2 conformance at levels A, AA, and AAA, with guidance on which level is required for legal compliance and common regulations.
How much of WCAG violations can be caught automatically?
The skill acknowledges that 30-50% of issues are detectable through automated testing. Manual verification with real users is required to catch the remainder.
Does this skill provide remediation guidance?
Yes. The skill includes actionable remediation strategies organized by impact level (critical, serious, moderate) and references detailed pattern documentation in `references/details.md`.
What accessibility standards does this cover?
The skill targets WCAG 2.2 specifically and also addresses ADA, Section 508, and VPAT compliance requirements.

Generated from the current SKILL.md. These answers refresh after source changes.