report-generation
Report Generation
Report File
Default output: DOCUMENT-ACCESSIBILITY-AUDIT.md in the project root.
Required Sections
Every audit report MUST include these sections:
- Audit Information - date, auditor, profile, scope, counts
- Executive Summary - totals, pass rate, most common issue, effort estimate
- Cross-Document Patterns - recurring issues, systemic failures
- Findings by File - per-document issues with rule ID, severity, location, WCAG, impact, remediation
- Findings by Rule (Cross-Reference) - rule-level aggregation across files
- What Passed - acknowledge clean documents and categories
- Remediation Priority - ordered by impact (Immediate / Soon / When Possible)
- Accessibility Scorecard - per-document scores and grades
- Metadata Dashboard - document properties health
- 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
More from taylorarndt/a11y-agent-team
framework-accessibility
Framework-specific accessibility patterns and fix templates for React, Vue, Angular, Svelte, Next.js, and Tailwind CSS.
28document-scanning
Document discovery, inventory building, and metadata extraction for accessibility audits. Use when scanning folders for Office documents (.docx, .xlsx, .pptx) and PDFs, building file inventories, detecting changes via git diff, or extracting document properties like title, author, and language.
25github-analytics-scoring
Scoring formulas and analytical frameworks for GitHub workflow agents. Covers repository health scoring (0-100, A-F grades), priority scoring for issues/PRs/discussions, confidence levels for analytics findings, delta tracking (Fixed/New/Persistent/Regressed), velocity metrics, contributor metrics, bottleneck detection, and trend classification. Use when computing scores, tracking remediation progress, building prioritized dashboards, or detecting workflow bottlenecks.
25github-scanning
GitHub data collection patterns for workflow agents. Covers search query construction by intent, date range handling, repository scope narrowing, preferences.md integration, cross-repo intelligence, parallel stream collection model, and auto-recovery for empty results. Use when building agents that search GitHub for issues, PRs, discussions, releases, security alerts, or CI status.
22accessibility-rules
Cross-format document accessibility rule reference with WCAG 2.2 mapping. Use when looking up accessibility rules for Word (DOCX-*), Excel (XLSX-*), PowerPoint (PPTX-*), or PDF (PDFUA.*, PDFBP.*, PDFQ.*) documents, or when mapping findings to WCAG success criteria for compliance reporting.
21github-workflow-standards
Core standards for all GitHub workflow agents. Covers authentication, smart defaults, repository discovery, dual MD+HTML output, screen-reader-compliant HTML accessibility standards, safety rules, progress announcements, parallel execution, and output quality. Apply when building any GitHub workflow agent - issues, PRs, briefings, analytics, community reports, team management.
20