If you’re doing #openscience but not considering accessibility then your science is not open. A reminder that neither @rstudio nor @ProjectJupyter are fully accessible, although both are making concerted efforts.
Don’t exclude people.
This also serves as a reminder to me that I need to consciously continue to do better. Working to consider accessibility needs to be learned since so many of us unconsciously accept our experience as the norm. We can participate in real-time spoken discussions
We can decipher weirdly formatted graphs, we can quickly understand the visual flow of a poster, and we can understand when bold text is a new heading, and when it’s just bold text.
If you use assistive technology to add context to research products you don’t have that advantage. If you are producing research products that can’t be understood by assistive technology *you are actively excluding people*.
If you are generating #jupyternotebooks or #rmarkdown documents that can’t pass one of the many online accessibility tests ( https://www.w3.org/WAI/ER/tools/ ) you need to do some work.
I need to do some work too. This is important work. Your science is too important to exclude people. People are too important to be excluded.
You can follow @sjGoring.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: