Web Accessibility Compliance
Compliance to Section 508 (and the stated goal of meeting WCAG 2.0 A & AA Success Criteria) varies from tool to tool, and to a certain extent depends on how tools are configured. It's also true that much of a disabled user's experience --and how accessible Sakai feels to that user -- will be determined by the content uploaded to it, and so a course with good accessibility will also require some forethought on the part of an instructor or course designer.
Since the current Section 508 standards were implemented in 1999, the WCAG 2 Level A and AA Success Criteria, and their associated techniques for success, have become the internationally recognized standards to meet for accessibility conformance. If the WCAG 2 Level A and AA Success Criteria are met, then the Section 508 §1194.22 Standards will be met. It is possible to meet all Section 508 §1194.22 Standards, and not meet the WCAG 2 Level A and AA Success Criteria.
Generally Accessible Sakai Tools
Tools that follow most accessibility guidelines include:
- Chat Room
- My Workspace--Membership
- My Workspace--Preferences
- Site Setup
- Web Content
- Worksite Setup
Sakai Tools Requiring Improved Accessibility
Some tools still need work to improve their accessibility. These include the following:
- Administrative Tools (Users, Aliases, Sites, Realms, M, On-Line, Memory, Site Archive)
- Drop Box
- My Workspace--Profile
- Tests & Quizzes
Sakai has been tested with current versions of JAWS using both Internet Explorer and Firefox. Compliance has also been evaluated using manual code inspection, the Firefox Accessibility Extension add-on, the WAVE Web Accessibility Evaluation tool, and W3C Validator in order to continually improve accessibility.
Results from Previous Accessibility Reviews
- Sakai 2.2 Accessibility Review
- Sakai 2.3 Accessibility Review
- Sakai 2.4 Accessibility Review
- Sakai 2.5 Accessibility Review
- Sakai 2.6 Accessibility Review
- Sakai 2.7 Accessibility Review
- Sakai 2.8 Accessibility Review
- Sakai 2.9 Accessibility Review (2011)
- Interim Sakai 2.9 Accessibility Review Results (2012)
- Summary of Brock University’s Audit of Sakai CLE 2.9.1
- Review commissioned by Longsight Longsight-Accessibility-JT-2013.doc
As we find problems, we put them in the Jira queue for repair (jira is the system used for issue and bug tracking related to Sakai development).
- "Accessibility Issues" list in Jira (searches text for "accessibility")
- Alternate Accessibility Issues view in Jira (Issues with Component=Accessibility)
Note: The lists may contain some items that do not relate to accessibility, due to Jira's text based search mechanism.
Several issues remaining to be resolved:
The WYSIWYG editor does not provide a keyboard-based exit from the text input box.