I don't have experience actually trying to use the lesson pages with a
screen reader or text-to-speech, but from the point of view of
accessibility audits, they seem to pass pretty well. I typically just
quickly check using WAVE http://wave.webaim.org/ and "Accessibility
Developer Tools" Chrome extension.

The lessons have just two issues that could be fixed easily:

1. The search box on the top bar does not have a label, so the <input>
field would not be understandable to a screen reader. Should be able to fix
just by adding aria-label, like: <input type="text" id="google-search"
placeholder="Search..." aria-label="Search">

2. The previous + next navigation arrows at the top and bottom of the page
are flagged because they don't have any text, just a glyphicon. They are
<h3> and <a>, both of which need some text or alternative label so that a
screen reader can make sense of their purpose.They probably shouldn't be
<h3> since they don't have semantic meaning as a heading level, the page is
just using the <h3> as a simple way to add the same styling. Then I think
you can fix it by adding an aria-label to the <a> or a <div> around the
arrows (like aria-label="Next lesson"), or you can add text that is only
used for screen readers with bootstrap's .sr-only class.

Also, Google says the contrast between text and background in the top nav
bar is too low, but its not a critical flag.

> Message: 5
> Date: Wed, 21 Sep 2016 16:59:36 +0100
> From: Raniere Silva <rani...@rgaiacs.com>
> To: Nelle Varoquaux <nelle.varoqu...@gmail.com>
> Cc: Software Carpentry Discussion
>         <discuss@lists.software-carpentry.org>
> Subject: Re: [Discuss] Strategies/techniques for accessibility (visual
>         impairment)
> Message-ID: <87vaxpjlav....@ssi.home>
> Content-Type: text/plain
> Hi Nelle,
> thanks for you tips to Leighton.
> > - Make sure your material are accessible (in that case, readable with
> > a screenreader). Schema should be avoided. Text is fine. Most pdf are
> > accessible, most *simple* html is as well, but fancy javascript can be
> > problematic.
> I have the feeling that our online lessons aren't 100% accessible
> and having them 100% accessible is something that I'm in favour
> even if we need to raise the contribution bar a little.
> I don't have a screenreader and I failed to setup the speech-to-text
> last time that I tried. If you could ask one of your friends for 20-30
> minutes to have a look on any sessions/topics of our lessons,
> for example, http://swcarpentry.github.io/shell-novice/03-create/,
> http://swcarpentry.github.io/r-novice-gapminder/05-data-structures-part2/,
> or http://swcarpentry.github.io/python-novice-inflammation/06-func/,
> and email me all the issues I will record the issues on GitHub
> and try to address them for our next release.
> Cheers,
> Raniere
> ------------------------------
> Subject: Digest Footer
> _______________________________________________
> Discuss mailing list
> Discuss@lists.software-carpentry.org
> http://lists.software-carpentry.org/listinfo/discuss
> ------------------------------
> End of Discuss Digest, Vol 38, Issue 15
> ***************************************
Discuss mailing list

Reply via email to