What this example teaches
- How to summarize automated findings without overclaiming compliance.
- How to turn findings into developer tickets and client summaries.
- How to keep manual review tasks visible.
Report summary without overclaiming
Bad
The site passed our accessibility scan and is compliant.A first-pass scan cannot prove compliance or full accessibility.
Better
The scan found no critical machine-detectable issues on the tested page. Manual review is still needed for keyboard flow, screen reader clarity, PDFs, media, and content quality.The summary reports what was tested and what remains unknown.
First-pass summary with priorities
Bad
There are 14 issues. Fix them.This does not help a team decide what to do first.
Better
First-pass scan: 2 critical, 5 major, 6 moderate, 1 notice. Start with unlabeled form fields and unnamed buttons, then review image alt text and contrast.The summary gives priority and direction.
Developer ticket
Bad
Accessibility broken on contact page.The ticket is too vague to assign or verify.
Better
Title: Add labels to contact form fields
Page: /contact/
Issue: Email and message fields have no connected labels.
Fix: Add visible labels with matching for/id values. Retest keyboard focus and error messages.The ticket includes page, issue, fix guidance, and retest expectations.
Client summary
Bad
Your website has accessibility failures.This may alarm stakeholders without explaining scope or next steps.
Better
We found several common accessibility issues that can be fixed before a formal review: missing form labels, vague link text, and possible low contrast. These are first-pass findings, not a full audit.The summary is plain-English, scoped, and actionable.
Manual review checklist
Bad
Manual review: done.Manual review needs specific evidence and coverage.
Better
- Keyboard: tab order, visible focus, skip link
- Screen reader: page title, headings, form labels, errors
- Content: alt text quality, link purpose, plain language
- Media/docs: captions, transcripts, PDFs
- Third-party tools: booking, payment, mapsThe checklist names the areas automation cannot fully prove.
What still needs human review
- Keyboard flow, screen reader experience, focus management, form recovery, content clarity, PDFs, captions, and third-party embeds.
- Whether the automated issue severity matches real user impact on the specific page.
- Whether fixes have been retested in the live design and workflow.
Related tools
Related issue library pages
- Image is missing alt text
- Form field is missing a label
- Button has no accessible name
- Possible low contrast text