Thanks for turning the results of your report into issues. That makes it much easier for us to work on.

It's great to see these issues identified. None of them seem overly complicated and the reports are very objective.

I invite you and everyone to contribute to fixing these issues.

Who are Deque, and can we add the person who wrote the report as watcher to all these tracker issues, so we can get more information in areas where what they wrote is unclear? In some cases, what they seem to be suggesting is in contradiction to what we have worked out over the years working with accessibility experts to make the quiz more accessible. (The OU has more disabled students that the rest of the UK higher education sector combined.)

Also, please can you publish the username and password for http://accessibility.mroomstest.net/mod/quiz/view.php?id=30, so we can see the example they were testing. Thanks.

Deque is a consultancy company that provides certification with the National Federation of the Blind in the US. You can find them at http://www.deque.com/ and about their certification at http://www.deque.com/services/nfb-certification-web-accessibility.

For http://accessibility.mroomstest.net you can use the following logins:
Teacher:
username: teacher50
password: demo

Student:
username: user0
password: demo

This site is running moodle 2.2.5 not to 2.3.2. I have been trying to review all tickets with demo.moodle.org or a local site before submitting them with a version of 2.3.2.

I see that Moodle 2.4 is now officially released, yet so many of these accessibility issues remain unresolved. I'm somewhat surprised and definitely curious why these issues aren't being given more priority than they are. Perhaps I'm just misunderstanding the process.

Thanks.

Hi, B.

Actually we're further through this issue than I thought we would be at this time.

Accessibility is a serious priority for us, but we (as a community and people at Moodle HQ) have to balance issues here with security issues, blocker issues and other priorities affecting the user community. Prior to this issue being reported, we had a period of development working on accessibility, but this is not something that can be continued indefinitely. We may have a chance to do such a push again in future.

In saying that, I encourage all interested developers to consider working on sub-tasks if this issue and any other accessibility issue. Many of these issues are high priority but not huge changes to Moodle. The more people we have working on this, the quicker it will get done.

We are planning to make another push on these subtasks in the next sprint (perhaps at the expense of new features in 2.6) so you should see action on these soon.

We'll be starting with the File Picker, but I could really use feedback on the ones that people find most important.

There have been a number of meta-issues reporting accessibility issues over the last couple of years. Most tasks reported have been completed, but there have been some left-overs that need to be sorted out.

I have shifted the remaining sub-tasks of this issue to MDL-40738 so that we can include it in an accessibility push.