102.3K+Download
Skip to the usage guide
Accessibility Auditby Alireza Rezvani

Accessibility Audit Skill.

Keep each accessibility finding connected to the affected element, proposed fix and verification result.

  • Accessibility
  • Design Review
  • Frontend
Download OpenDesignView Usage Guide
Source Review · Accessibility AuditSKILL.md
Task Accessibility Produces • A severity-ranked accessibility findings report • Before-and-after code fixes suited to the project's framework • A comparison with the initial findings and a list of remaining manual checks Before You Start Python for the bundled tools, source access and a browser or assistive-technology setup for contextual validation.
Editorial summary · source reviewed 2026-10-07 · not a generated example

01 What It Does

Turn Accessibility Findings into Verifiable Fixes

A scan-fix-verify accessibility workflow with Python utilities, framework references and report templates.

Source-based workflowNot an execution benchmark

The Working Approach

A11y Audit organizes accessibility work into scan, fix and verify phases. The source includes Python scanner and contrast-checker interfaces, severity categories and framework-specific remediation references. It can help turn a vague request to improve accessibility into a scoped list of elements and code changes.

The source describes broad WCAG coverage, but a code scan should not be presented as complete conformance certification. Keyboard flows, screen-reader behavior, dynamic content and the usefulness of alternative text still need contextual review. The practical value is traceability: preserve the initial findings, apply appropriate native semantics or styling changes, then rerun checks and test the actual interaction.

Expected Deliverables

  • A severity-ranked accessibility findings report
  • Before-and-after code fixes suited to the project's framework
  • A comparison with the initial findings and a list of remaining manual checks
See the Example Brief

From Brief to Review

  1. 01
    Scan a Defined Scope

    Identify the framework and relevant source paths. Record element-level findings and distinguish scanner detections from manual observations.

  2. 02
    Fix the Underlying Interaction

    Prefer native controls, meaningful labels and visible focus rather than adding ARIA attributes indiscriminately.

  3. 03
    Verify in Context

    Compare against the baseline, check contrast in the rendered state and exercise keyboard and assistive-technology paths that static analysis cannot establish.

02 When to Use It

When to Use It

Python for the bundled tools, source access and a browser or assistive-technology setup for contextual validation.

A Good Fit

  • Remediation PlanningUseful for converting a collection of source-level issues into prioritized, reviewable code changes.
  • Regression ChecksFits a project adding repeatable accessibility checks to an existing testing process.

Limits to Check

  • No Compliance CertificatePassing the included tools does not prove every applicable accessibility requirement is met across the product.
  • Severity Needs ContextThe source's severity labels are a triage aid. Real user impact depends on the element, task and available alternatives.

Bring These Inputs

  • Audit ScopeName the pages, components or source directory and the user journey being reviewed.
  • Rendered StatesProvide access to forms, errors, dialogs and other states that are absent from a simple static page.
  • Existing BaselineInclude prior findings or test results so resolved issues and regressions can be separated.

03 Decisions That Matter

Decisions That Matter

  1. Fixes Stay Traceable

    Before-and-after examples connect a finding to a concrete implementation rather than leaving only a standards reference.

  2. Automation Has a Boundary

    A useful report names what was scanned, what was tested manually and what remains unverified.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Setup

Retain the scripts and reference patterns. Review scanner coverage before using its results as a release gate.

Upstream Source File
https://github.com/alirezarezvani/claude-skills/blob/19392f7a08264ed00486a251f5b2098321771f94/engineering-team/a11y-audit/skills/a11y-audit/SKILL.md

Python for the bundled tools, source access and a browser or assistive-technology setup for contextual validation.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use a11y-audit to review our checkout form and modal. Start with a read-only findings report, including affected elements and severity reasoning. Check labels, native controls, focus visibility and contrast, then list manual keyboard and screen-reader checks. Do not call the page WCAG-compliant based only on the scanner, and do not apply fixes until I approve them.

Inspect the Result

Check the actual output against these observable criteria.

  • Each finding identifies a real element and an actionable correction.
  • Resolved issues are rechecked against the original baseline.
  • Untested keyboard, screen-reader and dynamic-state behavior remains explicitly unverified.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

Download OpenDesignRead the Quickstart

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
Alireza Rezvani
Repository
alirezarezvani/claude-skills
Skill File
engineering-team/a11y-audit/skills/a11y-audit/SKILL.md
License
MIT
Reviewed Snapshot
2026-10-07 · 19392f7a0826
Editorial Source Summary
A scan-fix-verify accessibility workflow with Python utilities, framework references and report templates.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

Can the scanner prove WCAG conformance?

No. The skill can support an audit, but automated source checks do not cover every contextual or interaction requirement.

Does it only support React?

The source includes patterns for several web frameworks and plain HTML. Verify the actual scanner and reference support for the project's version.

Should every clickable element receive an ARIA role?

Not automatically. The source generally prefers native semantic controls, which provide behavior that an ARIA role alone does not add.

OpenDesign

Make Room for the Next Design Iteration.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Download OpenDesignBrowse Design Skills
Upstream Source File
https://github.com/alirezarezvani/claude-skills/blob/19392f7a08264ed00486a251f5b2098321771f94/engineering-team/a11y-audit/skills/a11y-audit/SKILL.md