There is an all-in-one article including every part from this series (if you want prefer to read it all at once instead of "by installments")

Web Accessibility is a must in every web development project, yet it seems to remain a mystery for many web developers. Like it's something legendary instead of an essential skill needed for the job.

There are many misconceptions surrounding Web Accessibility, most of the time fueled by a lack of knowledge (or interest) in the matter. This article is a collection of some of those accessibility misconceptions or myths.

Content of the series:

• Accessibility is difficult
• Accessibility is expensive
• Accessible websites are ugly
• Accessibility is for blind people/screen readers
• Accessibility is for people with disabilities
• Automatic tests are enough for accessibility
• Accessibility overlays are enough to ensure Web Accessibility
• HTML is accessible by default
• No ARIA > Bad ARIA
• Prefers reduced motion means no motion

Thank you Todd Libby, Laurent Denoue, Cristian Diaz, InHuOfficial, and Maciej Pędzich, for all your insights, feedback, and (constructive) criticism when writing the article.

Cover image by Mike Hindle on Unsplash.