I usually prefer text over video, and the point that audio-only content isn't accessible makes for a very compelling argument to always provide a text version. So, in addition to wider reach, it makes it easier to consume the content at a pace you're comfortable with, as well as return later and easily reference specific parts.
For the motion problem, Safari actually introduced a solution a few months ago: the prefers-reduced-motion media query [0]. Hopefully other browsers will follow along and add support. Relevant issues per browser: Firefox [1], Chrome [2], Edge [3]. It doesn't look like any vendor has signaled interest, though.
I don't understand the wall of text point. Sometimes a topic requires a lot of nuanced points and clarifications, which might require long sentences and paragraph. I'm all for making content as approachable as possible, but I don't know if you can reasonably apply it to everything? I think seeing a few examples would probably help me understand.
For the small font size problem, browsers provide a solution! In Safari you can specify a minimum font size in Preferences > Advanced > Accessibility > [x] Never use font sizes smaller than [number]. Firefox also support a minimum font size [4], although the option is a bit hidden.
Too lazy to comment on the remaining points, but this was a really insightful post. I think we need more content like this to help us understand these problems. I'd guess most cases of poor accessibility are due to a general lack of awareness on the part of the development team.
My experience has been that making web apps accessible can be very challenging. There's not much good documentation or examples available, so as soon as you try implementing something more complicated than a traditional website, things start to break down.
In the previous paragraph I was going to reference existing w3c docs to explain my point, so I looked up their latest docs only to find that they've made some huge improvements! Check out the WAI-ARIA Authoring Practices draft [5]. It looks like now every single widget has simple docs and multiple examples. Even if I haven't implemented any widgets with this, just by skimming through, it looks much more promising than any of the previous docs I've seen.]
For the motion problem, Safari actually introduced a solution a few months ago: the prefers-reduced-motion media query [0]. Hopefully other browsers will follow along and add support. Relevant issues per browser: Firefox [1], Chrome [2], Edge [3]. It doesn't look like any vendor has signaled interest, though.
I don't understand the wall of text point. Sometimes a topic requires a lot of nuanced points and clarifications, which might require long sentences and paragraph. I'm all for making content as approachable as possible, but I don't know if you can reasonably apply it to everything? I think seeing a few examples would probably help me understand.
For the small font size problem, browsers provide a solution! In Safari you can specify a minimum font size in Preferences > Advanced > Accessibility > [x] Never use font sizes smaller than [number]. Firefox also support a minimum font size [4], although the option is a bit hidden.
Too lazy to comment on the remaining points, but this was a really insightful post. I think we need more content like this to help us understand these problems. I'd guess most cases of poor accessibility are due to a general lack of awareness on the part of the development team.
My experience has been that making web apps accessible can be very challenging. There's not much good documentation or examples available, so as soon as you try implementing something more complicated than a traditional website, things start to break down.
In the previous paragraph I was going to reference existing w3c docs to explain my point, so I looked up their latest docs only to find that they've made some huge improvements! Check out the WAI-ARIA Authoring Practices draft [5]. It looks like now every single widget has simple docs and multiple examples. Even if I haven't implemented any widgets with this, just by skimming through, it looks much more promising than any of the previous docs I've seen.]
[0] https://webkit.org/blog/7551/responsive-design-for-motion/
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1365045
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=722548
[3] https://wpdev.uservoice.com/forums/257854-microsoft-edge-dev...
[4] https://support.mozilla.org/en-US/kb/font-size-and-zoom-incr...
[5] https://www.w3.org/TR/wai-aria-practices/