Writing accessible software is very challenging, and a lot of the documentation that has historically been available was typically sub-par. I usually try advoca

Writing accessible software is very challenging, and a lot of the documentation that has historically been available was typically sub-par. I usually try advocating in favor of web accessibility, but in many cases developers just don't know any better. I'd definitely count myself among those that still have a lot to learn. I've noticed that the w3c is starting to push hard on improving the status quo, especially during the last few months. The latest WAI-ARIA Authoring Practices draft [0] is superb. It includes examples, documentation on the different keyboard interactions, and suggested aria properties. As the documentation quality increases, it gets easier to raise awareness among developers. My experience has generally been that once you raise the point and you provide a clearly defined solution, many people are happy to make changes. For example, I've occasionally convinced friends with inaccessible video to either publish transcripts or write articles / blogs with the equivalent knowledge. [0] https://www.w3.org/TR/wai-aria-practices-1.1/ https://www.w3.org/TR/wai-aria-practices-1.1/