See a Sample A11yCheck Scan Report

Questions answered by this guide

• ?What does an A11yCheck report actually look like?
• ?What information does each finding include?
• ?Does a report show severity or confidence?
• ?What does a report say about parts of the course that weren't tested?
• ?Can I see an example before I scan my own course?

What you'll learn

• A report is organized into three pillars: Accessibility, Course Quality, Course Engagement, never blended into one score
• Every finding shows where it occurs, what's wrong, and what to change, in plain language
• A report always states what was actually reviewed, it never implies a pass on something that wasn't tested

What's inside

Anyone deciding whether to run a real scan and wanting to see what a report actually looks like first

1. 01The sample course
2. 02What review types were run
3. 03Sample Accessibility findings
4. 04Sample Course Quality findings
5. 05Sample Course Engagement findings
6. 06What this report does not claim

Why it matters

Seeing a real example of what a report contains, and doesn't contain, before running your own scan sets the right expectations: what level of detail to expect, how findings are organized, and how honestly the report handles the limits of an automated review.

Example

Best practices

• Illustrative sample course: a 12-slide Storyline compliance-training course ("Workplace Safety Basics"), not a real customer course.
• Review types actually run in this sample: Accessibility, Course Quality, and Course Engagement, all three, since that's the default "before you publish" combination described in the Before You Publish Checklist.
• Sample Accessibility findings: 3 images with missing alt text (Critical), one custom hover tooltip with no accessible description (Low), one button reachable only by mouse, not keyboard (Major), text contrast of 3.2:1 against a required 4.5:1 on the quiz feedback slide (Major).
• Sample Course Quality findings: one external "Learn more" link returning a 404, two slides sharing 91% of the same text (a likely accidental duplicate), inconsistent button corner-radius between slide 4 and the rest of the course.
• Sample Course Engagement findings (advisory): slide 8 flagged for high text density (approximately 210 words against a 25-second narration window), one click-to-reveal interaction on slide 5 flagged as likely decorative since it reveals text the learner could already read directly.

Common mistakes

• Expecting a single overall percentage to mean the same thing across all three pillars, it doesn't, each pillar's findings carry a different kind of confidence, see A11yCheck's Review Methodology.
• Assuming a finding with no fix yet applied means the course failed, a report is a list of what to review and fix before publishing, not a pass/fail exam result.

Practical checklist

• Check which review types were actually run before reading anything into a pillar that shows no findings, an empty pillar can mean either a clean pass or that it wasn't reviewed.
• Read each finding's location and object name, not just its title, before deciding how to fix it.
• Treat Accessibility and Course Quality findings as close to pass/fail, and Course Engagement findings as a prompt to look closer.
• Use the real WCAG citation on an Accessibility finding to verify it yourself if you want a second source, not just A11yCheck's word for it.

Frequently asked questions

Summary

A real A11yCheck report groups findings into three pillars, shows exactly where and what's wrong in plain language with a real fix, and always states what was actually reviewed rather than implying a pass on anything that wasn't tested.