|Page||Issue||Description||Remediation Recomendation||Sakai JIRA|
|Left navigation||Colour contrast should be 4.5:1 at minimum.||The Active menu item is indicated with a different colour than the other menu items. The colour contrast is insufficient (2.67:1).||Gonzalo check out (fixed)||https://jira.sakaiproject.org/browse/SAK-11540|
|My workspace||Skip link||jump to content link doesn’t work on this page||Resolved/Non-issue||Resolved/Non-issue|
|Welcome Tutorial||Modal dialog||When a user first logs in they get a welcome dialog that includes a tutorial. The cursor focus is not moved to the modal dialog when it first appears, making it very difficult for a screen reader to find it. It is actually added to the DOM at the very end of the code order. It is the last thing that you navigate to on the page after going through all the footer links. In addition the persistence (always visible) of the modal window means it appears to ‘jump’ as you scroll down the page. This is very visually distracting. The keyboard focus will need to be managed.||• modal can be activated via keyboard, |
• focus must be managed so that it is brought to the dialog when launched and that it remains inside the dialog as the user tabs through the controls and reads the content.
• content (including images) is accessible,
• can be closed pressing ESC key,
• focus returns to launching point when the dialog is closed.
Possible solution: Use jquery modal dialogs; many accessibility features already incorporated into the framework. E.g. http://hanshillen.github.com/jqtest/#goto_dialog
|Profile||Mouse only rollover||The edit button becomes visible only when the mouse is rolled over a specific profile item. The edit button should be visible at all times, or it should, at minimum become visible on keyboard focus as well as on mouse hover. A screen magnifier user (ZoomText) would have difficulty finding the button as they pan their view window across the screen. A voice recognition user would not be able to activate the edit button because it is not visible. The information ‘buttons’ are also activated only on mouse hover. They take keyboard focus but do not open.||https://jira.sakaiproject.org/browse/PRFL-842|
|Profile||Editor||The form fields in the editor are missing the label for / id association.||Fix labels, change from TinyMCE to other editor||Migrated to CKeditor|
|Profile||Editor||Tables are used to lay out the form.||Currently not a strict WCAG 2 Level AA issue|
|Profile||Editor||• TinyMCE editor not fully keyboard accessible.|
• Keyboard trap. Cannot back-tab once focus is in the text editor.
|Removed in lastest version|
|Profile||Editor||Datepicker is not keyboard accessible. ||https://jira.sakaiproject.org/browse/PRFL-843|
|Messages||Error messages and form fields||Form fields are missing explicit labels|
|Messages||Error messages and form fields||Error messages do not take focus and might be difficult to find for some users.||https://jira.sakaiproject.org/browse/MSGCNTR-836|
|Schedule:Add Event||Form fields||• Some form fields have labels. This can be improved by including the mandatory notification (*) in the form label.|
• Form fields without visible labels should still have either hidden programmatic labels or titles. Related fields should be wrapped in a fieldset E.g.
|Noted||<textarea name="description" id="description" wrap="virtual" rows="30" cols="80"></textarea>|
|Schedule:Add Event||Error messages||Error messages do not take focus and appear in the middle of the screen making it difficult for screen reader or users of screen magnification software to find the message.||https://jira.sakaiproject.org/browse/SAK-24429|
|Announcement, Instructor workspace||Table||• The table summary does not match the table contents.||https://jira.sakaiproject.org/browse/SAK-24430|
|Tables - general||Table markup||• In general the table header rows are marked with TH. Row headers are not marked up. For simple data tables this has minimal impact for end users however the schedule and calendar tables often have a blank row header for ½ hour time slots. This is most likely to reduce visual clutter but the lack of a row header makes it difficult for a non-visual user to orient themselves. |
• Tables often have hidden columns. A screen reader will announce the total columns in a table and this does not match the actual table makeup. Etc. Resources table; 10 columns but only 7 have content.
|Tests & Quizzes||Form labels||Form field labeling is inconsistent: |
• Radio buttons have a label for / id association. These should also be part of a fieldset with the question as a legend.
• Text input fields are missing the label for / id association.
|Tests & Quizzes||Keyboard accessibility||Keyboard accessible and logical order is inconsistent:|
• Tab and reading order is not logical for multiple choice questions.
Matching questions are not accessible.
• The select boxes are missing programmatic labels. A non-visual user would have difficulties determining what the matching options are because of how the interactive and static text is displayed.
|Matt to verify issue|
|Tests & Quizzes||Keyboard accessibility||Error messages do not take focus and appear in the middle of the screen making it difficult for screen reader or users of screen magnification software to find the message.||https://jira.sakaiproject.org/browse/SAM-2218|