Thanks all for the discussion of accessibility and Evan for the PR to improve the accessibility of the lessons.
In our workshop checklists: http://www.datacarpentry.org/checklists/ we have an Accessibility section ( http://www.datacarpentry.org/accessibility/) that also mentions talking with the students in advance. Hosts can also be helpful, as they often have resources at their university that can help with physical arrangements. If there's other things we should add to the Accessibility checklist or information we could add to that section, that page is a good resource for other instructors, so it would be great if anyone wanted to file an issue or add a PR https://github.com/datacarpentry/datacarpentry.github.io/tree/master/pages Best, -Tracy On Sat, Sep 24, 2016 at 2:12 AM, Leighton Pritchard < [email protected]> wrote: > Thanks Nelle, > > That’s really good advice, and very much appreciated! > > We’ve had some additional advice off-list, and your last point - > communicate with the student ahead of time to find out their needs - is > maybe the most humane and practical piece of advice anyone could give for > this and similar situations. > > Many thanks, > > L. > > On 20 Sep 2016, at 18:48, Nelle Varoquaux <[email protected]> > wrote: > > On 20 September 2016 at 08:59, Leighton Pritchard > <[email protected]> wrote: > > Hi all, > > We’ll be teaching a workshop soon, with a visually-impaired (blind) > student. > This is a new experience for me, and I was wondering if any of you might be > able to share some advice for teaching strategies/approaches to delivering > material that could be useful? > > > I've never taught to a blind student, but I've got a bunch of friends > who are blind, so here is a couple of things to keep in mind: > > - Make sure you give all explanation orally. That'll be hard > considering you'll probably show a lot of code. I'd suggest sharing > your material with him/her beforehand making sure every piece of code > you'll type is in there (or record what you are typing and upload it > somewhere everytime you save). > - 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. > - Make sure that the tables, chairs and cables are quite tidy and > aren't moved around too much. > > In practice, all my blind friends are very autonomous, so I wouldn't > worry too much. You can also ask that student directly: he/she may be > able to give you some advice. > > Cheers, > N > > > -- > Leighton Pritchard > [email protected] > gpg/pgp:0xDECACFFC > > > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
