There are many preconceived ideas about accessibility. We wanted to take a moment to address some of the most common myths.
Myth 1: accessibility is a constraint on design
An accessible website does not have to be unattractive or boring. In our view, accessibility stimulates creativity rather than limiting it. It pushes us to think differently, be more original, and encourages innovation. Accessibility invites us to rethink how we design websites in order to make them easier to use. This is not a design compromise, quite the opposite. Good design is not limited to aesthetics; it must first and foremost serve the user experience. A website can look great, but if it makes it harder for users to complete the task they came to accomplish, it misses the mark.
Moreover, most accessibility work happens in the code and is invisible to the naked eye. One of the practices that most directly affects visual design is color contrast, meaning that text must have sufficient contrast against its background. This does not mean text must be black on a white background. A wide range of colors can be used, but for example, light text on a white background should be avoided. In short, any design compromises required are generally minimal, while having a positive impact on the overall user experience.
Myth 2: accessibility only benefits a small group of users
Accessibility improves the experience for all users. Many features that are now widely adopted were originally designed to meet accessibility needs. Captions are a good example: many people use them even if they are not hard of hearing.
One of the core principles of accessibility is ensuring that a website is usable regardless of users’ physical, sensory, or cognitive abilities. This leads to more flexible websites that allow users to interact with content in different ways. For example, some users rely on keyboard-only navigation out of necessity, while for others it’s simply a preference. In both cases, being able to navigate a site easily using a keyboard increases user satisfaction.
Also, we should not assume that no users with disabilities visit our website. In reality, it’s impossible to know, as the use of assistive technologies cannot be detected on the web, and 80% of disabilities are invisible. Actually, people with disabilities make extensive use of the web because it enables them to accomplish tasks that were previously difficult or even impossible.
It’s also important to remember that disabilities can be temporary or situational, like a broken arm or difficulty reading a screen in bright sunlight, and that anyone can acquire a disability at some point in their life. In Quebec, 21% of the population aged 15 and over has a disability that limits daily activities, a proportion that rises to 29.8% among those aged 65 and over.
Finally, accessibility is also beneficial for your business. Because accessible websites rely on clear, semantic HTML, they are easier for search engines to understand, which contributes to better SEO. Committing to accessibility also strengthens your reputation around inclusion and expands your potential customer base.
Myth 3: accessibility is the final step in a website project
Although most accessibility-related work occurs during development, it must begin at the design stage. It’s difficult for developers to make a design accessible if accessibility was not considered from the outset. It’s even harder to make a website accessible once it has already been completed. Accessibility is not an add-on that can simply be layered on top of existing code. In some cases, complex components must be completely rebuilt to make them accessible.
That is why accessibility must be considered at every stage of a project. The earlier it is integrated into the process, the easier and less costly it is to implement. According to IBM, fixing an issue after launch can cost up to 30 times more than if it had been identified during the design phase.
Accessibility is also not a one-time checkbox that can be ticked and forgotten. Every time content or design changes are made, new accessibility issues can be introduced. In addition, accessibility standards continue to evolve, and new best practices emerge over time. Accessibility is therefore an ongoing process, based on continuous and incremental improvements.
Web accessibility should no longer be viewed as an optionnal compromise, but rather as a quality standard. Treating accessibility as a burden means overlooking its true impact: a better user experience, broader reach, and a more sustainable platform. When integrated proactively, accessibility becomes simple, effective, and an essential part of any web project.