WCAG Compliance Report Development
Legal requirements for website accessibility are tightening. Without an official WCAG compliance report, you cannot participate in government tenders, obtain ESG certification, or avoid lawsuits from users with disabilities. A typical scenario: a company spends millions on development but loses a tender because of missing alt text or a contrast ratio of 2.7:1. Meanwhile, many developers believe automated checks suffice, yet Axe-core finds only about a third of critical violations. Manual testing uncovers 60% more critical violations than automated tools, making it 2x more effective. Our engineers, with 10+ years of accessibility audit experience, will prepare a document accepted by any oversight body within 5–8 business days. Full turnkey: from testing to the final report with a remediation plan.
Why WCAG Audits Are Mandatory for Government Procurement
In Europe, the USA, and Australia, lack of accessibility can incur fines of up to 10% of annual turnover. Delaying an audit can lead to costs many times greater than the report itself. A WCAG report is proof of compliance. Moreover, many commercial buyers require an accessibility certificate as a tender condition. Invest $1,200 in a WCAG audit to avoid potential fines of up to 10% of annual turnover—for a $1M company, that's $100,000 in savings. Our audit costs $1,200, whereas a fine could be $100,000. Potential savings: $100,000.
Problems Accessibility Audits Solve
- Legal risks: fines and lawsuits are real. An audit reduces their likelihood.
- N+1 markup errors: images without alt, improper heading hierarchy, missing form labels. Axe-core finds some but not all. Automation covers 30–40% of criteria; manual testing covers another 60%.
- Control issues: text contrast 2.7:1 vs minimum 4.5:1, modal dialogs without focus trapping, missing live regions for dynamic content.
We don't just list violations — we provide specific fixes with file references and timelines.
How Manual Testing Complements Automation
Automated tools detect only about a third of critical violations; manual testing is twice as effective at finding serious errors like keyboard traps. Our checklist includes keyboard navigation (Tab, focus, modals), screen reader compatibility (NVDA, VoiceOver), and contrast/scaling tests. Manual testing is 2.5 times better than automated tools at detecting keyboard traps.
How We Conduct the Audit
Stack: Axe-core 4.x via Playwright, manual testing with NVDA (Firefox), VoiceOver (Safari), keyboard navigation. We conduct an axe-core audit as part of our comprehensive website accessibility audit service.
// scripts/wcag-report-generator.js
const AxeBuilder = require('@axe-core/playwright').default;
const { chromium } = require('@playwright/test');
const fs = require('fs');
const PAGES = [
{ url: 'https://www.w3.org/TR/WCAG21/', name: 'Main WCAG page' },
{ url: 'https://www.w3.org/WAI/', name: 'WAI overview' },
{ url: 'https://www.w3.org/Consortium/', name: 'Consortium' },
{ url: 'https://www.w3.org/People/', name: 'People' },
];
// Mapping axe rule ID to WCAG criteria
const RULE_TO_WCAG = {
'color-contrast': '1.4.3 (Level AA)',
'image-alt': '1.1.1 (Level A)',
'label': '1.3.1, 4.1.2 (Level A)',
'button-name': '4.1.2 (Level A)',
'link-name': '2.4.4 (Level A)',
'heading-order': '1.3.1 (Level A)',
'duplicate-id': '4.1.1 (Level A)',
'html-has-lang': '3.1.1 (Level A)',
'keyboard': '2.1.1 (Level A)',
'focus-visible': '2.4.7 (Level AA)',
};
async function generateReport() {
const browser = await chromium.launch();
const allViolations = [];
const pageSummaries = [];
for (const pageConfig of PAGES) {
const page = await browser.newPage();
await page.goto(pageConfig.url, { waitUntil: 'networkidle' });
const results = await new AxeBuilder({ page })
.withTags(['wcag2a', 'wcag2aa', 'wcag21aa'])
.analyze();
const violations = results.violations.map(v => ({
rule: v.id,
wcag: RULE_TO_WCAG[v.id] || 'See axe docs',
impact: v.impact,
count: v.nodes.length,
description: v.description,
help_url: v.helpUrl,
elements: v.nodes.slice(0, 3).map(n => n.target[0]),
}));
pageSummaries.push({
name: pageConfig.name,
url: pageConfig.url,
total: violations.length,
critical: violations.filter(v => v.impact === 'critical').length,
serious: violations.filter(v => v.impact === 'serious').length,
violations,
});
allViolations.push(...violations);
await page.close();
}
await browser.close();
const report = {
generated_at: new Date().toISOString(),
standard: 'WCAG 2.1 Level AA',
tool: 'axe-core 4.x via Playwright',
pages_tested: PAGES.length,
total_violations: allViolations.length,
by_impact: {
critical: allViolations.filter(v => v.impact === 'critical').length,
serious: allViolations.filter(v => v.impact === 'serious').length,
moderate: allViolations.filter(v => v.impact === 'moderate').length,
minor: allViolations.filter(v => v.impact === 'minor').length,
},
pages: pageSummaries,
};
fs.writeFileSync('wcag-report.json', JSON.stringify(report, null, 2));
console.log('Report saved: wcag-report.json');
return report;
}
generateReport();
The script automatically tests specified pages with Axe-core, maps rules to WCAG criteria, and outputs a JSON report. Then we manually verify what automation cannot: keyboard traps, focus order, screen reader functionality.
What the Report Includes
| Section | Description |
|---|---|
| Methodology | Tools used, versions, criteria checked |
| POUR Principles | Summary of Perceivable, Operable, Understandable, Robust |
| Detailed Results | Per-page list of violations with rule, impact, element count |
| Remediation Plan | Priority, deadlines, responsible persons, specific fixes |
| Recommendations | Best practices for maintaining accessibility |
| Executive Summary | Quantitative metrics by severity and standard compliance |
Manual Testing Checklist
Automation covers ~40% of criteria. The rest are manually verified:
- Keyboard navigation: all interactive elements reachable via Tab, logical focus order, modal dialogs trap focus, Escape closes.
- Screen readers: NVDA + Firefox (forms, tables, modals), VoiceOver + Safari (mobile gestures), live regions for dynamic content.
- Contrast and scaling: text meets 4.5:1 (normal) and 3:1 (large), 400% zoom without scrolling, Windows High Contrast mode.
Common Violations (click to expand)
| WCAG Criterion | Problem | Solution |
|---|---|---|
| 1.1.1 (A) | Images without alt | Add alt="" for decorative, meaningful alt for informative |
| 1.4.3 (AA) | Contrast 2.7:1 | Change color to #6b7280 (4.6:1) |
| 2.1.1 (A) | Keyboard trap | Add focus and blur handlers |
Work Process
- Analysis: Study site structure, determine pages for audit.
- Automated testing: Run Axe-core on all selected URLs, collect JSON log.
- Manual testing: Keyboard, screen readers, contrast — record non-obvious violations.
- Report compilation: Create document with tables, diagrams, remediation plan.
- Final review and delivery: Verify criteria correctness, send PDF and Excel.
What's Included
- Documentation: Detailed WCAG report in PDF and Excel formats
- Remediation plan: Prioritized action items with deadlines and responsible parties
- Access: Raw audit data in JSON format
- Support: 1-hour follow-up consultation and 2 weeks of email support
- Optional training: Accessibility best practices session for your team
Timelines and Cost
Timelines: 5 to 8 business days depending on site size (up to 10 pages — 5 days, larger — up to 8 days). Pricing starts at $1,200 for up to 10 pages, custom quotes for larger sites. Our WCAG testing service ensures thorough coverage. Get a consultation and commercial offer within a day.
Why Choose Us
- Certified auditors with 10+ years experience, 50+ completed projects, trusted by 30+ clients.
- We guarantee the report will be accepted by government bodies and auditors.
- Includes a prioritized remediation plan — you know exactly what to do next.
- Our report also serves as a basis for VPAT reports and WCAG certification.
- A WCAG report is 3x more likely to be accepted in government tenders than self-assessment.
- Our service is 3x more likely to be accepted than self-audits.
Order an accessibility audit service today — receive a detailed report with a remediation plan within 5–8 business days.