Accessibility is often misunderstood. Below are some common myths about accessibility, along with the facts that explain them. Understanding these helps ensure that services, websites, and content are usable for everyone.
Around 15–25% of people need accessibility features, and anyone can acquire a disability at any time. Accessibility is not just for a few users; it improves the experience for everyone. Features such as clear content, simple navigation, and easy-to-find help make a website easier to use for all visitors, not only for those with disabilities.
Many disabilities are invisible. You cannot always tell who has a disability just by looking at them. Accessibility helps a wide range of users, including those with vision or hearing impairments, cognitive challenges, or motor difficulties. Making content and services accessible ensures no one is unintentionally excluded.
Including accessibility from the start of a project is usually much more cost-effective than retrofitting it later. Some improvements do have a cost, but planning often reduces redesign or redevelopment expenses. Additionally, accessible design can save money by reducing customer support requests and minimising confusion or errors for users.
Accessibility is about usability, not limiting creative design. Accessible websites can be visually appealing and engaging. Clear layouts, sufficient colour contrast, well-organised content, and intuitive navigation actually enhance design, making sites more enjoyable for all users while still meeting accessibility requirements.
Many countries have laws and regulations requiring accessibility, especially for public services. Even when it’s not legally required, accessible services are preferred by users because they are easier to use. Accessibility demonstrates inclusivity, professionalism, and respect for all users.
Screen readers perform best when websites use proper HTML structure and semantic markup. ARIA labels are helpful in certain situations, but cannot replace semantic HTML. Misusing ARIA can actually create accessibility problems rather than solve them. Proper coding and design are essential for effective accessibility.
Read more about ARIA in the technical accessibility section.
Accessibility add-ons or overlays rarely solve core issues and can sometimes make a site less accessible. True accessibility must be built into the website itself through proper design, coding, and content practices.
Read more about the problems with overlays
Automated testing tools are useful for identifying some accessibility problems, but they cannot catch everything. Human testing is essential to find issues that tools cannot detect, such as understanding content, using interactive elements, or navigating complex structures.
WCAG AA is a minimum standard and does not guarantee full accessibility. Accessibility is an ongoing process that should go beyond the basic requirements wherever possible. Regular testing, feedback, and improvements ensure that a website or service works well for all users.