Common Myths and Misconceptions

Myth: “Accessibility is only for blind users.”

Reality: Blindness is one of many disability types. Accessibility also serves people who are deaf or hard of hearing, people with motor impairments, people with cognitive or learning disabilities, and people with temporary or situational limitations. Designing for one group often benefits many others too.

Myth: “If an automated checker gives us a passing score, we’re compliant.”

Reality: As covered in Module 4, automated tools catch roughly 30-40% of issues. A clean scan is a starting point, not a finish line. Manual and user testing are still necessary.

Myth: “An accessibility overlay (a bolt-on script or widget) will fix our site.”

Reality: Overlays sit on top of existing code without fixing the underlying structure. They can’t repair broken semantics, illogical navigation, or missing labels — and in some cases, they interfere with the very assistive technology they claim to support. Native browser and OS accessibility features, combined with properly built code, are a far more reliable foundation than layered-on tools.

Myth: “Once we fix it, we’re done.”

Reality: Accessibility isn’t a one-time project — it’s an ongoing practice. New content, new features, and code changes can all introduce new barriers. Sites need periodic testing and accessibility built into the ongoing workflow, not just a single audit.