accessibility-report

Generate accessibility compliance reports including VPAT and ACR documents

16 stars

Best use case

accessibility-report is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Generate accessibility compliance reports including VPAT and ACR documents

Teams using accessibility-report should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/accessibility-report/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/accessibility-report/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/accessibility-report/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How accessibility-report Compares

Feature / Agentaccessibility-reportStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Generate accessibility compliance reports including VPAT and ACR documents

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Accessibility Report Skill

## Purpose

Generate comprehensive accessibility compliance reports including VPAT (Voluntary Product Accessibility Template) and ACR (Accessibility Conformance Report) documents.

## Capabilities

- Generate VPAT 2.4 documents
- Create ACR (Accessibility Conformance Reports)
- Complete WCAG 2.1/2.2 checklists
- Generate remediation roadmaps
- Track accessibility debt over time
- Export in multiple formats

## Target Processes

- accessibility-audit.js (vpatGenerationTask)
- component-library.js

## Integration Points

- VPAT 2.4 template
- WCAG 2.1/2.2 success criteria
- Section 508 requirements
- EN 301 549 standard

## Input Schema

```json
{
  "type": "object",
  "properties": {
    "reportType": {
      "type": "string",
      "enum": ["vpat", "acr", "wcag-checklist", "remediation-roadmap"],
      "default": "vpat"
    },
    "productName": {
      "type": "string",
      "description": "Name of the product being evaluated"
    },
    "productVersion": {
      "type": "string",
      "description": "Version of the product"
    },
    "evaluationDate": {
      "type": "string",
      "format": "date"
    },
    "wcagLevel": {
      "type": "string",
      "enum": ["A", "AA", "AAA"],
      "default": "AA"
    },
    "auditResults": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "criterion": { "type": "string" },
          "level": { "type": "string" },
          "conformance": { "type": "string" },
          "remarks": { "type": "string" }
        }
      }
    },
    "outputFormat": {
      "type": "string",
      "enum": ["docx", "pdf", "html", "markdown"],
      "default": "markdown"
    }
  },
  "required": ["reportType", "productName", "auditResults"]
}
```

## Output Schema

```json
{
  "type": "object",
  "properties": {
    "reportPath": {
      "type": "string",
      "description": "Path to generated report"
    },
    "summary": {
      "type": "object",
      "properties": {
        "overallConformance": { "type": "string" },
        "criteriaPass": { "type": "number" },
        "criteriaFail": { "type": "number" },
        "criteriaPartial": { "type": "number" }
      }
    },
    "remediationItems": {
      "type": "array",
      "description": "Prioritized remediation tasks"
    },
    "timeline": {
      "type": "object",
      "description": "Suggested remediation timeline"
    }
  }
}
```

## Usage Example

```javascript
const result = await skill.execute({
  reportType: 'vpat',
  productName: 'MyApp Web Portal',
  productVersion: '2.1.0',
  wcagLevel: 'AA',
  auditResults: [
    { criterion: '1.1.1', level: 'A', conformance: 'Supports', remarks: 'All images have alt text' },
    { criterion: '1.4.3', level: 'AA', conformance: 'Partially Supports', remarks: 'Some low contrast text in footer' }
  ],
  outputFormat: 'markdown'
});
```

Related Skills

accessibility-wcag

16
from diegosouzapw/awesome-omni-skill

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

accessibility-standards

16
from diegosouzapw/awesome-omni-skill

Implement WCAG 2.1 accessibility standards for Vue 3 apps. Use when adding ARIA labels, keyboard navigation, screen reader support, or checking color contrast. Mentions "accessibility", "ARIA", "keyboard nav", "screen reader", or "color contrast".

accessibility-review

16
from diegosouzapw/awesome-omni-skill

Reviews UI for accessibility issues against WCAG 2.1/2.2 AA. Triggers on "is this accessible?", "check accessibility", or contrast/a11y review requests.

accessibility-readability

16
from diegosouzapw/awesome-omni-skill

Ensure textbook content is accessible, readable, and understandable for learners of all skill levels. Use when reviewing content for clarity, adding explanations for beginners, or improving content accessibility.

accessibility-patterns

16
from diegosouzapw/awesome-omni-skill

Build inclusive web experiences following WCAG guidelines. Covers semantic HTML, ARIA, keyboard navigation, color contrast, and testing strategies. Triggers on accessibility, a11y, WCAG, screen readers, or inclusive design requests.

accessibility-mobile

16
from diegosouzapw/awesome-omni-skill

React Native accessibility patterns for iOS and Android. Use when implementing a11y features.

accessibility

16
from diegosouzapw/awesome-omni-skill

Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).

accessibility-games

16
from diegosouzapw/awesome-omni-skill

Game accessibility skill for colorblind modes and control remapping.

accessibility-excellence

16
from diegosouzapw/awesome-omni-skill

Master web accessibility (A11y) to ensure your product is usable by everyone, including people with disabilities. Covers WCAG standards, semantic HTML, keyboard navigation, screen readers, color contrast, and inclusive design practices. Accessibility is not a feature—it's a fundamental requirement.

accessibility-checklist

16
from diegosouzapw/awesome-omni-skill

When building UI components, forms, or any user-facing interface. Check before every frontend PR.

accessibility-a11y

16
from diegosouzapw/awesome-omni-skill

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

u01954-handoff-contracting-for-accessibility-services

16
from diegosouzapw/awesome-omni-skill

Operate the "Handoff Contracting for accessibility services" capability in production for accessibility services workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.