Falsehoods programmers think about web accessibility

Falsehoods programmers think about accessibility

There exists a lot of lists of Falsehoods programmers think about X but while searching for ones for accessiblitiy
I noticed there was a limited amount though I did find [Common web accessiblity myths](https://www.boia.org/blog/common-web-accessibility-myths).
It should be noted that this is not my special field, I am just very intrested in a more accessible Internet. The list is also
not in any specific order. Also please notice that programmer here could as well be "People in the tech industry"

Standard disclaimer: My native language is not English and it might show in some places, also sometimes my vocubulary is limited.

Also people with more knowledge please add and edit this list. 
When I created this I thought that gists allowed pull requests.
Apperently this is not the case but comment or reach me at virre.annergard@gmail.com to update or add.

---

1. Accessiblity on the Internet is just about vision.
2. There is no commercial benefit of making our website accessible.
3. Automatic testing is enough to cover accessiblity. 
4. Following guidelines means we are fully accessible. 
5. All blind users will use a screen reader
6. All blind users will use a braile printer
7. Only blind users use a screen reader
8. The same accessiblity solution works for all users
9. The same accessiblity soulutio works for all users have the same disability. 
10. Only govermental organisations needs to care about accessiblity. 
11. Accessiblity solutions is only on the developers.
12. Accessiblity solutions is only on the editors. 
13. Accessiblity have to be ugly
14. Accessibilty on the web is only about websites
15. Following guidelines and automatic testing is enough for making an accessible site.
16. Once a website is accessible it is accessible for ever.
17. A user only have one disability. 
18. The only people who benefit from focus styles are keyboard-only users.
19. People who prefer to use keyboard navigation only do so because they cannot use a mouse. 
20. Disabled people understand CSS and Javascript and are capable of writing userscripts for their browser.
21. Keyboard navigation is slow.
22. Smartphones don't have physical keyboards, so focus styles can be removed at small breakpoints.
23. Hover styles will work as focus styles.
24. Screen reader users do not have javascript enabled.
25. `tabindex=0` is all you need to make something keyboard accessible.
26. Videos subtitles/captions are just for deaf people.
27. Deaf people speak American Sign Language in all countries where the main oral language is English.
28. All touchpad users have multi-touch capability, and can perform multi-touch gestures. 
29. All mice have scroll wheels.
30. The HTML5 outline algorithm has actually been implemented by web browsers, so you can just use H1 everywhere.
31. Screen reader users don't use a mouse.
32. If Javascript detects a mouseover event, that means the user is using a mouse.
33. If Javascript detects a "tab" keypress, that means the user is blind and is using a screen reader.
34. The user probably knows about a browser add-on which will magically fix this problem in our website. 
35. Users want this link to open in a new window.
36. It's OK to disable the browser's context menu.
37. I used a large font, so it's OK to disable the browser zoom.
38. Keyboard-only users don't produce Javascript scroll events.
39. Screen reader users read the page content by pressing the tab key. So we should put `tabindex="0"` on every element to make the page accessible to screen reader users.
40. Deaf people in the US speak American Sign Language.
41. This image is purely decorative
---

Resources
[https://www.w3.org/WAI/]
[https://www.w3.org/WAI/standards-guidelines/wcag/]

----

Thank yous:
https://github.com/fuzzbomb