A11y Lens is intended as a practical testing and learning aid. It helps identify common patterns and likely issues, but it does not replace expert review or user testing.
Key limitation
Accessibility compliance depends on code, context, content quality, interaction design, and real-world assistive technology behavior. No automated scanner can evaluate all of that.
Automated testing has limits
Independent research and industry practice consistently show that automated tools detect only a portion of accessibility issues. Many WCAG success criteria, such as meaningful alternative text, sensible focus order, usable error recovery, and cognitive clarity, require human judgment.
Use A11y Lens as one layer of review
- Run automated checks early and often during development.
- Perform manual keyboard, screen-reader, zoom, and reduced-motion testing.
- Validate complex widgets and task flows with disabled users whenever possible.
No legal advice
Content on A11y Lens is educational and does not constitute legal advice. Compliance under the ADA, Section 508, EN 301 549, the European Accessibility Act, or other laws depends on your jurisdiction, procurement requirements, and audit scope.
If you need legal interpretation or a formal conformance opinion, consult a qualified accessibility specialist or attorney.
Accuracy of reference material
We aim to link to authoritative sources such as W3C, WebAIM, MDN, and regulatory guidance. Even so, standards and implementation advice can change over time. Always confirm important requirements against the primary source.