What Does it Mean to Make Web Content Accessible?
All members of our Brock community navigate through and experience the world differently, and as such may have different needs for learning and accessing web content. For example, some members of our Brock community may use assistive technology and/or require accommodations to aid their learning.
Information that is presented solely through visual means will be inaccessible to blind users that require text to be read by a screen reader. Similarly, audio-only content will be inaccessible to deaf users. Improving the accessibility of the web content allows a more users with diverse needs to access and understand that content, thereby reducing barriers to teaching and learning.
Accessibility & Sakai
Different areas Brock's learning management system (LMS), Isaak-Sakai, include features that have been implemented for accessibility, including those that support students registered with Student Accessibility Services who use assistive technology and/or require accommodations. More information on these features can be found below.
If you have questions about the accommodation process for students with disabilities please contact Student Accessibility Services.
Guidelines for Accessible Content
Creating accessible content is not only a best practice, but also a legal requirement.
- Perceivable: information must be presented to users in ways they can perceive (e.g. Ensuring content is accessible to users who are deaf and/or blind)
- Operable: user interface components, navigation, and structure must be operable (e.g. Making all functionality accessible via keyboard)
- Understandable: information and the operation of user interface must be understandable, and structural elements should be used in a meaningful way (e.g. Making web pages appear and operate in predictable ways)
- Robust: content must be robust enough so that it can be interpreted reliably by a wide variety of technologies, including assistive technologies (e.g. Ensuring content is compatible with current and future user agent software and other assistive technologies)
Basic Accessibility Features in Sakai
Access Keys in Sakai
Access keys allow keyboard users to jump to a specific part of a web page. If an access key is available for a given link or button, the access key will be announced by a screen reader when that link or button receives focus. The exact keyboard commands to trigger an access key depend on both your operating system and internet browser.
To invoke access keys:
- In Internet Explorer and Chrome on Windows, use Alt plus the indicated letter or number
- In Firefox for Windows, use Alt+Shift plus the indicated letter or number.
- In Safari or Firefox for Mac OS X, use Ctrl plus the indicated letter or number.
- In Chrome for Mac OS X, use Ctrl+Alt plus the indicated letter or number.
"Portal-Based" or Main Area Access Keys
Access keys available throughout Sakai include:
- Help tool: Access key - 6
- Skip to content: Access key - C
- Skip to tools list: Access key - L
- Skip to worksites: Access key - W
Tool-Specific Access Keys
Access keys that are available for most form-based tools include:
- Delete, remove, or cancel: Access key - X
- Edit or revise: Access key - E
- Refresh: Access key - U
- Save: Access key - S
- View or preview: Access key - V