Skip to content

Accessibility Audit Report Export

Complete WCAG 2.2 Level AA checklist with pass/fail/N/A toggles for every success criterion. Auto-calculated conformance score with printable HTML report export.

FreeNo SignupNo Server UploadsZero Tracking
Audit Information

0%

Score

0

Pass

0

Fail

0

N/A

55

Untested

WCAG 2.2 Level AA Checklist
Set all:

1. Perceivable

1.1.1Non-text ContentA
1.2.1Audio-only and Video-only (Prerecorded)A
1.2.2Captions (Prerecorded)A
1.2.3Audio Description or Media Alternative (Prerecorded)A
1.2.4Captions (Live)AA
1.2.5Audio Description (Prerecorded)AA
1.3.1Info and RelationshipsA
1.3.2Meaningful SequenceA
1.3.3Sensory CharacteristicsA
1.3.4OrientationAA
1.3.5Identify Input PurposeAA
1.4.1Use of ColorA
1.4.2Audio ControlA
1.4.3Contrast (Minimum)AA
1.4.4Resize TextAA
1.4.5Images of TextAA
1.4.10ReflowAA
1.4.11Non-text ContrastAA
1.4.12Text SpacingAA
1.4.13Content on Hover or FocusAA

2. Operable

2.1.1KeyboardA
2.1.2No Keyboard TrapA
2.1.4Character Key ShortcutsA
2.2.1Timing AdjustableA
2.2.2Pause, Stop, HideA
2.3.1Three Flashes or Below ThresholdA
2.4.1Bypass BlocksA
2.4.2Page TitledA
2.4.3Focus OrderA
2.4.4Link Purpose (In Context)A
2.4.5Multiple WaysAA
2.4.6Headings and LabelsAA
2.4.7Focus VisibleAA
2.4.11Focus Not Obscured (Minimum)AA
2.5.1Pointer GesturesA
2.5.2Pointer CancellationA
2.5.3Label in NameA
2.5.4Motion ActuationA
2.5.7Dragging MovementsAA
2.5.8Target Size (Minimum)AA

3. Understandable

3.1.1Language of PageA
3.1.2Language of PartsAA
3.2.1On FocusA
3.2.2On InputA
3.2.3Consistent NavigationAA
3.2.4Consistent IdentificationAA
3.2.6Consistent HelpA
3.3.1Error IdentificationA
3.3.2Labels or InstructionsA
3.3.3Error SuggestionAA
3.3.4Error Prevention (Legal, Financial, Data)AA
3.3.7Redundant EntryA
3.3.8Accessible Authentication (Minimum)AA

4. Robust

4.1.2Name, Role, ValueA
4.1.3Status MessagesAA
Export Report
Export
Embed code
<iframe src="https://wcagkit.com/embed/audit-export" width="100%" height="600" frameborder="0" title="Accessibility Audit Report Export - wcagkit"></iframe>
<p style="font-size:12px;text-align:center;margin-top:4px;">
  <a href="https://wcagkit.com/tools/audit-export" target="_blank" rel="noopener">Powered by wcagkit</a>
</p>
Attribution preview

Powered by wcagkit

How to Use Accessibility Audit Report Export

  1. 1

    Enter audit details

    Provide the website URL, auditor name, date, and target conformance level (A or AA).

  2. 2

    Evaluate each criterion

    Go through the WCAG 2.2 checklist and mark each success criterion as Pass, Fail, or Not Applicable.

  3. 3

    Add notes

    Document findings, observations, and recommendations in the notes field for each criterion.

  4. 4

    Export the report

    Print the report directly or download it as an HTML file with print-optimized formatting.

Frequently Asked Questions

This tool includes all WCAG 2.2 Level A and Level AA success criteria, organized by the four principles: Perceivable, Operable, Understandable, and Robust. When targeting Level A only, Level AA criteria are hidden from the checklist.

The score is calculated as the percentage of tested criteria that pass. Not Applicable criteria are excluded from the calculation. Full conformance requires all applicable criteria to pass with zero failures. Untested criteria are tracked separately and do not count toward the score.

Yes. The report structure follows the WCAG-EM (Website Accessibility Conformance Evaluation Methodology) approach, which provides a structured framework for evaluating website accessibility. The generated report includes audit metadata, per-criterion results, a summary score, and a recommendations section for failed criteria.

Currently the tool does not persist data between sessions. We recommend completing the audit in one session and exporting the report when finished. The report contains all your findings and notes in a standalone HTML file.

No. All data stays in your browser. The report is generated entirely client-side using JavaScript. No audit data, website URLs, or findings are transmitted to any server.

Related Tools

Conducting a WCAG 2.2 Accessibility Audit

A thorough accessibility audit evaluates a website against the Web Content Accessibility Guidelines success criteria. WCAG 2.2, the latest version published by the W3C, includes 55 success criteria at Levels A and AA. This tool provides a structured checklist for documenting your evaluation of each criterion, calculating an overall conformance score, and generating a professional audit report.

The WCAG-EM Methodology

The Website Accessibility Conformance Evaluation Methodology (WCAG-EM) provides a standardized approach to evaluating websites. It involves defining the evaluation scope, exploring the website to understand its structure and functionality, selecting a representative sample of pages, auditing each page against the target conformance level, and reporting the results. This tool supports the auditing and reporting phases by providing a complete criterion-by-criterion checklist and automated report generation.

Understanding the Four POUR Principles

WCAG organizes its success criteria under four principles, often abbreviated as POUR. Perceivable means information must be presentable in ways all users can perceive, covering text alternatives, time-based media, adaptable content, and distinguishable elements. Operable means user interface components must be operable by all users, covering keyboard access, timing, seizures, navigation, and input modalities. Understandable means content must be understandable, covering readable text, predictable behavior, and input assistance. Robust means content must be interpretable by assistive technologies, covering parsing and compatibility.

Tips for Effective Auditing

Test with real assistive technology, not just automated tools. Use keyboard-only navigation to verify all functionality is accessible. Test with at least one screen reader (NVDA on Windows, VoiceOver on Mac). Check zoom behavior at 200% and 400%. Verify that all interactive elements have visible focus indicators. Test form validation and error handling with assistive technology. Document specific failures with screenshots and code references in the notes field for each criterion.

After the Audit

The generated report serves as both a compliance document and a remediation roadmap. Share it with your development team to prioritize fixes based on severity and user impact. Level A failures typically represent the most critical barriers and should be addressed first. Schedule a follow-up audit after remediation to verify that issues have been resolved and no new issues have been introduced.