Your Accessibility Scan https://example.com 82 Partial alignment with WCAG 2.2 AA |
Your site has gaps worth addressing.Your site meets a lot of WCAG 2.2 AA, but I found issues that affect people using assistive technology. Most are straightforward to fix and would also improve alignment with the EAA and EN 301 549. |
| What I found | ||||
|
| Areas that need attention |
| IssueSome images are missing descriptions, so screen reader users cannot tell what they show Affects 5 pages: /, /about, /services +2 more |
| IssueSome text is hard to read because it does not have enough contrast against its background Affects 2 pages: /pricing, /contact |
| WarningSome form fields are missing labels, so visitors using screen readers may not know what to enter On /contact |
| IssueSome buttons are missing labels, so visitors using assistive technology cannot tell what they do Affects 2 pages: /, /services |
| WarningSome buttons or links are too small, making them difficult to tap on mobile devices Affects 2 pages: /blog, /about |
| IssueBroken link: https://acme.test/old On /about |
Why this mattersAccessibility issues stop some visitors from completing actions on your site — reading content, filling a form, finishing a purchase. They also affect alignment with the EAA (in force since June 2025), WCAG 2.2 AA, and EN 301 549. Most of these are fixable, and the fixes improve the site for everyone — not only people using assistive technology. |
Want a hand making sense of this?Book a free 15-minute call. I’ll walk through the results, point at what to prioritise, and outline a practical remediation plan. Book a free 15-minute call— Joe Gullo EAA Accessibility Consultant |
EAA · WCAG 2.2 AA · EN 301 549 Scanned 5 Jun 2026 by Joe Gullo Digital · Automated accessibility scan within tested scope. A manual review with assistive technology is recommended for full conformance. |