Accessibility

Accessibility

by Jon Hardisty -
Number of replies: 2
Hi all

I've been looking at a few packages for a learning resource we're developing related to visual impairment issues and am very impressed with what Moodle has to offer. Although the primary audience for the resource isn't visually impaired people themselves, as a charity working in this sector we can't produce something that isn't fairly accessible. Having installed and tried Moodle out using JAWS, I think this would stop us using it in its current form.

We don't really have the resources (or in my case, the ability sad ) to modify Moodle ourselves for accessibility, but I've noticed some fairly encouraging posts in the forums about work on version 2.0.

I wondered if this is the right place (can't seem to find a forum dealing specifically with accessibility) to post some feedback on what we're finding using the current version with access tech?

If anyone can give me some more specific information on what accessibility changes we might see in the next version, it would also be very helpful.

Thanks, Jon
Average of ratings: -
In reply to Jon Hardisty

Re: Accessibility

by Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
Hi, Jon.

I'll move this over to the Themes forum which is probably closest. I've asked before for auditing-type information which would be very useful as a checklist while developing Moodle 2.0 but the biggest baddies seem to be the frames (though see this: http://www.webaim.org/howto/frames/)

I would love Moodle 2.0 to get a clean report from http://www.wave.webaim.org/

See: http://moodle.org/mod/forum/discuss.php?d=2693 for more on the template system with XHTML.

My intention is the template will allow other tweaks to the interface like big or graphical buttons, etc.
In reply to Martin Dougiamas

Re: Accessibility

by Jon Hardisty -
Thanks.

I hadn't seen the post about themes controlled by CSS, this certainly sounds like it would make things easier to work with from an accessibility point of view.

I must admit we'd not tried any pages with frames in as I have been adding content on our test site as html text, it seems they only occur when viewing an uploaded document? However as your link points out they are generally navigable with more recent screenreaders if correctly titled.

I'd like to give a bit of feedback from the point of view of using Moodle with a screenreader if I may, probably mostly stuff from W3C guidelines you've already considered for 2.0... sometimes validation doesn't pick up on contextual problems with accessibility, though. We haven't really had the opportunity to do a full audit, but hope this is of some use smile The out of context links and alt tags on text items seem to be our main stumbling points...

1. A number of links don’t make sense out of context e.g. ‘more…’ Users often quickly navigate a page by asking JAWS to read out a list of the links on it, this doesn't really work if it just says “more… more… more…”

2. There are several images without alt tags or with alt tags which are confusing: ‘this course allows guest users to enter’ which links to a particular course – doesn’t say what it is.

3. Use of tables for layout not ideal. Although JAWS seems to read through the layout in a logical manner (suspect other screenreaders may not do this as well though), it also reads out the table and column number before each piece of text, which rapidly becomes annoying.

4. In most of the content areas (e.g. when “available courses” is displayed on the front page), what appear to be text links to courses, etc, have alt tags attached to them. JAWS only reads the alt tags which say ‘resource’ or ‘forum’ and you can’t distinguish between them. The text itself is not read out.

5. There is a very lengthy menu on the left before you get to the main course content – it’s very time consuming to go through this with a screen reader.

6. Problem with combi boxes, e.g. language box and menu which allows you select a course – JAWS automatically selects the first option when you simply want to read the options, normally it will display the full list and let you move down the options. No idea why this is happening, though!