Myth #1: People with disabilities don’t use the web.
Truth: In some cases the internet is the only way how disabled people can communicate to the world. This is why the pandemic awakened conversations on not just “remote work” but “web accessibility”
Myth #2: Web accessibility is just a developer’s responsibility.
Truth: It’s a team effort. Designers create accessible UIs, developers build it, QA engineers do the accessibility testing, PMs make sure that accessibility is included in the team processes, legal team checks if a product is risk free from an accessibility perspective, content managers adjust content to be compliant.
Myth #3: Accessibility only affects a small group of users.
Truth: Around 15% of the world’s population, or estimated 1 billion people, live with disabilities.
Myth #4: Making a website accessible is costly and time-consuming.
Truth: It depends on when you do it. It may not be the case if accessibility is considered from the beginning of the project and a development team has proper skills. When accessibility has become a habit, the development time doesn’t change or changes a little.
Myth #5: We can quickly add accessibility before the release.
Truth: Wrong move. In some cases, making features accessible at the end of development process may require the full refactoring.
Myth #6: Accessibility only helps people with disabilities.
Truth: Fortunately it helps everyone. It’s a known fact that applying accessibility principles improves overall user experience and makes a website more convenient to use. Solve for one, extend to many.
Credits and More myths at https://a11ymyths.com/