Accessibility
Web accessibility problems
The defects that make a page unusable with a screen reader or a keyboard, plus the European Accessibility Act statement obligation that has applied since June 2025.
11 checks · 3 with framework-specific fixes
Every check on this surface
- How to label form fields accessiblyForm fields have labels · weight 9
- How to write alt text for imagesImages have alt attributes · weight 8
- Why my icon buttons have no accessible nameLinks and buttons have accessible names · weight 7
- How to stop disabling pinch zoomPinch-zoom is not disabled · weight 7
- Why my site needs a viewport meta tagViewport meta tag is present · weight 6
- Do I need an accessibility statementAccessibility statement is published · weight 6
- How to add a skip to content linkA skip link bypasses the navigation · weight 4
- How to support prefers-reduced-motionMotion respects prefers-reduced-motion · weight 4
- Why heading levels should not skipHeading levels do not skip · weight 4
- Why a page needs a main landmarkPage has a main landmark · weight 4
- Why duplicate element ids break accessibilityElement ids are unique · weight 3
Check all of this against your own site
The audit runs these together with the other groups and returns what failed, what it costs you, and the fix for your framework.
No signup. Results in 30 seconds.