Report Generation
- 191 installs
- 381 repo stars
- Updated August 4, 2026
- community-access/accessibility-agents
Compile Lighthouse findings, manual checks, and legal mapping into stakeholder-ready accessibility reports with prioritized fixes and evidence for release approval.
About
report-generation from accessibility-agents turns accessibility scan and mapping outputs into formal audit reports for SaaS, ecommerce, and content launches. It helps agents deliver prioritized violation lists, executive summaries, and remediation plans during ship-phase review and stakeholder approval.
- Aggregates multi-source a11y findings
- Prioritizes fixes by impact
- Produces reviewer-ready summaries
- Supports compliance sign-off packets
- Tracks remediation status
Report Generation by the numbers
- 191 all-time installs (skills.sh)
- Ranked #347 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/community-access/accessibility-agents --skill report-generationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 191 |
|---|---|
| repo stars | ★ 381 |
| Last updated | August 4, 2026 |
| Repository | community-access/accessibility-agents ↗ |
What it does
Compile Lighthouse findings, manual checks, and legal mapping into stakeholder-ready accessibility reports with prioritized fixes and evidence for release approval.
Files
<!-- CANONICAL SOURCE: .github/skills/report-generation/SKILL.md -- Edit the canonical source; sync to Gemini via scripts/check-gemini-sync.ps1 -->
Report Generation
Report File
Default output: DOCUMENT-ACCESSIBILITY-AUDIT.md in the project root.
Required Sections
Every audit report MUST include these sections:
1. Audit Information - date, auditor, profile, scope, counts 2. Executive Summary - totals, pass rate, most common issue, effort estimate 3. Cross-Document Patterns - recurring issues, systemic failures 4. Findings by File - per-document issues with rule ID, severity, location, WCAG, impact, remediation 5. Findings by Rule (Cross-Reference) - rule-level aggregation across files 6. What Passed - acknowledge clean documents and categories 7. Remediation Priority - ordered by impact (Immediate / Soon / When Possible) 8. Accessibility Scorecard - per-document scores and grades 9. Metadata Dashboard - document properties health 10. Confidence Summary - breakdown by confidence level
Optional Sections (include when applicable)
- Template Analysis - when batch scanning detects shared templates
- Comparison Report - when re-scanning against a baseline
- CI/CD Recommendations - when no config files exist
Severity Scoring Formula
Document Score = 100 - (sum of weighted findings)
Weights:
Error (high confidence): -10 points
Error (medium confidence): -7 points
Error (low confidence): -3 points
Warning (high confidence): -3 points
Warning (medium confidence):-2 points
Warning (low confidence): -1 point
Tips: 0 points
Floor: 0 (minimum score)Score Grades
| Score | Grade | Meaning |
|---|---|---|
| 90-100 | A | Excellent - minor or no issues |
| 75-89 | B | Good - some warnings, few errors |
| 50-74 | C | Needs Work - multiple errors |
| 25-49 | D | Poor - significant accessibility barriers |
| 0-24 | F | Failing - critical barriers, likely unusable with AT |
Organization Modes
| Mode | Description | Best For |
|---|---|---|
| By file | Group all issues under each document | Small batches (< 10 files) |
| By issue type | Group all instances of each rule across documents | Seeing patterns |
| By severity | Critical first, then serious, moderate, minor | Prioritizing fixes |
VPAT/ACR Compliance Export
Conformance Levels
| Level | Criteria |
|---|---|
| Supports | No findings for this WCAG criterion across any document |
| Partially Supports | Some documents pass, some fail |
| Does Not Support | All or most documents fail |
| Not Applicable | Criterion does not apply to scanned document types |
Supported VPAT Editions
- VPAT 2.5 (WCAG) - maps to WCAG 2.2 criteria
- VPAT 2.5 (508) - maps to Revised Section 508 standards
- VPAT 2.5 (EN 301 549) - maps to EU accessibility directive
- VPAT 2.5 (INT) - International edition (all three combined)
Remediation Tracking
When comparing against a baseline audit report:
| Status | Meaning |
|---|---|
| Fixed | Issue was in previous report but is now resolved |
| New | Issue was not in previous report but appears now |
| Persistent | Issue remains from previous report |
| Regressed | Issue was previously fixed but has returned |
Progress Metrics
- Issue reduction percentage:
(fixed / previous_total) * 100 - Score change:
current_score - previous_score - Documents improved: count of documents with higher scores
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264k