Moodle

META: Accessibility compliance for 2.3

Details

  • Affected Branches:
    MOODLE_21_STABLE

Description

We need to spend some quality time looking at accessibility for 2.x, going for the low-hanging fruit and going for some certification of Moodle 2.2 at the highest level possible.

This bug should have subtasks added.

Issue Links

This issue will be resolved by:
MDL-33197 book chapters need unique page titles Minor Open
MDL-33199 print view of book has not headings Minor Open
MDL-33198 book chapter titles should be headings Minor Open
This issue has a non-specific relationship to:
MDL-27209 Medium priority accessibility problems in Moodle 2 Minor Open
Progress
Resolved Sub-Tasks Unresolved Sub-Tasks

Sub-Tasks

1. better visual cues for selecting completion tracking Sub-task Open Open moodle.com
 
2.
 more verbose alt text for completion tracking Sub-task Closed Closed Rajesh Taneja
 
3.
 unlabelled form elements for choices Sub-task Closed Closed Ankit Agarwal
 
4. choice responses are difficult to read for screen reader users Sub-task Development in progress Development in progress Rossiani Wijaya
 
5. Remove skip links in docked blocks Sub-task Open Open moodle.com
 
6.
 Block headings not accessible to screen readers when docked Sub-task Closed Closed Sam Hemelryk
 
7. Content of docked blocks are not accessible to screen readers. There is no prompt highlighting expandable items. Sub-task Open Open Sam Hemelryk
 
8.
 Hide Block tab should be a button rather than an image. Sub-task Closed Closed moodle.com
 
9. Provide feedback to screen readers that the navigation block is expandable / collapsible Sub-task Open Open Sam Hemelryk
 
10. Provide feedback to screen readers when nodes are expanded or collapsed Sub-task Open Open Sam Hemelryk
 
11. Bullets are hidden in high contrast mode Sub-task Open Open Sam Hemelryk
 
12. Collapsible menus difficult to access with Voice software Sub-task Open Open moodle.com
 
13. Remove alt text from custom bullets in navigation tree Sub-task Open Open Sam Hemelryk
 
14. form validation and error recovery Sub-task Open Open moodle.com
 
15. file picker is not accessible Sub-task Open Open Dongsheng Cai
 
16.
 text input fields missing labels Sub-task Closed Closed Rossiani Wijaya
 
17. select input elements are missing labels Sub-task Reopened Reopened Rossiani Wijaya
 
18. orphaned form labels Sub-task Open Open moodle.com
 
19. read-only text input fields rendered as plain text and not as a read-only input field Sub-task Reopened Reopened Ankit Agarwal
 
20. language change jump menu has accessibility problems Sub-task Open Open Adrian Greeve
 
21. contextual help menu is not easily accessed by screen reader users Sub-task Open Open moodle.com
 
22. quiz matching questions are missing form labels Sub-task Open Open Tim Hunt
 
23. short answer questions in quiz do not have labels Sub-task Open Open Tim Hunt
 
24. Folder resource has numerous accessibility problems Sub-task Open Open Dongsheng Cai
 
25. user report grade view has inaccessible table Sub-task Open Open Andrew Davis
 
26. more descriptive heading text for questions Sub-task Open Open Tim Hunt
 
27. more descriptive alt text for flagging quiz questions Sub-task Open Open Tim Hunt
 
28. notify screen reader users when questions are flagged Sub-task Open Open Tim Hunt
 
29. the quiz timer needs to be labeled as a timer with ARIA Sub-task Open Open Tim Hunt
 
30. more descriptive text for "not yet answered" text Sub-task Open Open Tim Hunt
 
31. quiz summary table should have additional table headers Sub-task Open Open Tim Hunt
 
32.
 quiz navigation block uses background color to convey information Sub-task Closed Closed Tim Hunt
 
33. text is too verbose in calendar table summary Sub-task Development in progress Development in progress Frédéric Massart
 
34. hovering over calendar events is not keyboard accessible Sub-task Open Open moodle.com
 
35.
 table for calendar does not have a summary Sub-task Closed Closed Rossiani Wijaya
 
36. buttons have unnecessary labels on forgot password page Sub-task Reopened Reopened Ankit Agarwal
 
37.
 same ID used on multiple buttons Sub-task Closed Closed Ankit Agarwal
 
38. no semantic structure on "My Home" page Sub-task Open Open moodle.com
 
39. provide easier chat reading for screen reader users in accessible chat activity Sub-task Open Open moodle.com
 
40. multipage items need unique page titles Sub-task Open Open moodle.com
 
41. using a screen reader can cause irradic screen behavior Sub-task Open Open moodle.com
 
42. blink and justifytext CSS rules should be removed Sub-task Open Open Mary Evans
 
43. modal windows have accessibility problem Sub-task Open Open moodle.com
 
44. consistency in denoting start of the main content Sub-task Open Open Sam Hemelryk
 
45. screen reader profile setting is unnecessary Sub-task Open Open moodle.com
 
46. TinyMCE generates invalid nested list code Sub-task Open Open moodle.com
 
47. view profile page needs table headers Sub-task Development in progress Development in progress Frédéric Massart
 
48.
 need unique link text in calendar Sub-task Closed Closed Rajesh Taneja
 
49. empty heading tags in recent activity page Sub-task Development in progress Development in progress Frédéric Massart
 
50.
 headings are out of order on recent activity page Sub-task Closed Closed Adrian Greeve
 
51. form input elements missing labels in recent activity page Sub-task Reopened Reopened Ankit Agarwal
 
52. no semantic structure in forums Sub-task Open Open moodle.com
 
53. difficult for screen reader users to find reply area in forum Sub-task Open Open moodle.com
 
54.
 lesson progress bar is not read by screen readers Sub-task Closed Closed Rossiani Wijaya
 
55.
 change heading levels in lesson Sub-task Closed Closed Rossiani Wijaya
 
56. report view selection menu is an unlabeled jump menu Sub-task Waiting for integration review Waiting for integration review Adrian Greeve
 
57. overview - activity report has list coding errors Sub-task Open Open moodle.com
 
58. need to have one accessible chat, not two tools Sub-task Open Open moodle.com
 
59. layout of accessible chat Sub-task Open Open moodle.com
 
60.
 don't use background images to convey important information Sub-task Closed Closed Michael de Raadt
 
61.
 be careful to use CSS rules for bolder text correctly Sub-task Closed Closed Michael de Raadt
 
62. use ARIA landmarks to aid in navigation for screen reader users Sub-task Open Open Sam Hemelryk
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Glenn Ansley added a comment -

Greg Kraus (gdkraus) and I will be entering a total of about 75 sub tasks to this over the remainder of the week. If you find that we need to change anything in the process, please let us know.

These issues are based off of Greg's Accessibility report of Moodle 2.1 for NC State University:
http://accessibility.oit.ncsu.edu/reports/moodle-2-1/Moodle2-1AccessibilityEvaluation.pdf

Our first goal is to get all the bugs into tracker and triaged and then to start providing patches as we implement them for our needs here at NCSU. Of course, any community assistance would be more than appreciated (code and discussion).

Show
Glenn Ansley added a comment - Greg Kraus (gdkraus) and I will be entering a total of about 75 sub tasks to this over the remainder of the week. If you find that we need to change anything in the process, please let us know. These issues are based off of Greg's Accessibility report of Moodle 2.1 for NC State University: http://accessibility.oit.ncsu.edu/reports/moodle-2-1/Moodle2-1AccessibilityEvaluation.pdf Our first goal is to get all the bugs into tracker and triaged and then to start providing patches as we implement them for our needs here at NCSU. Of course, any community assistance would be more than appreciated (code and discussion).
Hide
Permalink
Greg Kraus added a comment -

To view the report in other formats - http://accessibility.oit.ncsu.edu/reports/moodle-2-1/

Show
Greg Kraus added a comment - To view the report in other formats - http://accessibility.oit.ncsu.edu/reports/moodle-2-1/
Hide
Permalink
Martin Dougiamas added a comment -

Fantastic, thanks guys, I'll make sure our STABLE team helps a lot too.

Priorities will be very useful, thanks.

Show
Martin Dougiamas added a comment - Fantastic, thanks guys, I'll make sure our STABLE team helps a lot too. Priorities will be very useful, thanks.
Hide
Permalink
Greg Kraus added a comment -

All of the issues are entered now, so I'll go back and start adding some details.

Show
Greg Kraus added a comment - All of the issues are entered now, so I'll go back and start adding some details.
Hide
Permalink
Michael de Raadt added a comment -

Yes, thanks for doing this.

It may take us a while, but we will work through these.

Show
Michael de Raadt added a comment - Yes, thanks for doing this. It may take us a while, but we will work through these.
Hide
Permalink
Michael de Raadt added a comment -

Hi, Greg.

I've completed triaging the sub-tasks of this issue.

There are a few issues that I have left un-triaged because I wasn't sure what you meant or because I thought more detail would help. You can see these issues together using the following query.

http://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=parent+%3D+MDL-27843+and+labels+is+empty&runQuery=true&clear=true

The remaining issues I have put on either the Stable backlog or the Dev backlog. This is an indication of the significance of work involved (new code, database changes, needing room on the Moodle roadmap) and which team here at Moodle HQ might attack it. For people outside HQ, this can be ignored. A fix version relating to a Moodle version should be set once the code is integrated into one or more branches.

The stable team should be able to start working on some of these issues in the next sprint. If developers at NCSU are able to work on these issues also, that would be great. Please mark the issues as started when you do so we don't double-up on work. If you or other developers need greater access in the tracker to achieve this work, please contact me directly by email and I will arrange it.

Show
Michael de Raadt added a comment - Hi, Greg. I've completed triaging the sub-tasks of this issue. There are a few issues that I have left un-triaged because I wasn't sure what you meant or because I thought more detail would help. You can see these issues together using the following query. http://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=parent+%3D+MDL-27843+and+labels+is+empty&runQuery=true&clear=true The remaining issues I have put on either the Stable backlog or the Dev backlog. This is an indication of the significance of work involved (new code, database changes, needing room on the Moodle roadmap) and which team here at Moodle HQ might attack it. For people outside HQ, this can be ignored. A fix version relating to a Moodle version should be set once the code is integrated into one or more branches. The stable team should be able to start working on some of these issues in the next sprint. If developers at NCSU are able to work on these issues also, that would be great. Please mark the issues as started when you do so we don't double-up on work. If you or other developers need greater access in the tracker to achieve this work, please contact me directly by email and I will arrange it.
Hide
Permalink
Jenny Gray added a comment -

Following accessibility testing by expert testers at the Open University, Sam Marshall and I filed MDL-27209 and MDL-27197. You might like to take a look and see if there is overlap on your list above or any extras that you are able to include?

Show
Jenny Gray added a comment - Following accessibility testing by expert testers at the Open University, Sam Marshall and I filed MDL-27209 and MDL-27197. You might like to take a look and see if there is overlap on your list above or any extras that you are able to include?
Hide
Permalink
Michael Penney added a comment -

Hi Greg - I was going over your spreadsheet to check on the status of fixes, and could not find a an issue for:
"For screen reader users it is not clear that a new window has opened up when the File Picker appears on the screen." - is there an issue number for this?

Show
Michael Penney added a comment - Hi Greg - I was going over your spreadsheet to check on the status of fixes, and could not find a an issue for: "For screen reader users it is not clear that a new window has opened up when the File Picker appears on the screen." - is there an issue number for this?
Hide
Permalink
Greg Kraus added a comment -

Hi Michael,

For some of the items I conflated them into a single issue, especially if a whole system just needed to be redesigned. The file picker is a good example of this. There were numerous issues with it so I put them all into one.

http://tracker.moodle.org/browse/MDL-30841

Show
Greg Kraus added a comment - Hi Michael, For some of the items I conflated them into a single issue, especially if a whole system just needed to be redesigned. The file picker is a good example of this. There were numerous issues with it so I put them all into one. http://tracker.moodle.org/browse/MDL-30841

People

Vote (22)
Watch (19)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.5#665-sha1:422aead) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.