Posted: 19 December 2018 | Last updated: 15 Feb 2021
Measures to support accessibility
itslearning takes the following measures to ensure accessibility of our platform:
- We include accessibility considerations throughout our internal policies
- We provide continuous accessibility training for our staff
- We assign clear accessibility targets and responsibilities
itslearning is designed to be compliant with WCAG 2.1 level AA.
The Web Content Accessibility Guidelines (WCAG) detail accessibility requirements for product designers and developers. It defines three levels of conformance: Level A, Level AA, and Level AAA.
Although our goal is WCAG 2.1 Level AA conformance, we have also applied some Level AAA Success Criteria. For example, our UI components are created to support both AA and AAA color contrast standards.
WCAG 2.1 Guidelines
Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
|1.1 Text Alternatives: Provide text alternatives for any non-text content.||Supports with exceptions||Not all elements have good text alternatives.|
|1.2 Time-based Media: Provide alternatives for time-based media.||N/A||The only time-based media is user-added media.|
|1.3 Adaptable: Create content that can be presented and navigated in different ways.||Supports with exceptions||Not all structures conveyed through presentation can be programmatically determined.|
|1.4 Distinguishable: Make it easier for users to see and hear content, including adequately separating the foreground from the background.||Supports with exceptions||There are examples of text with insufficient contrast.
In a few places color is used as the sole method of conveying information.
Principle 2: Operable
User interface components and navigation must be operable.
|2.1 Keyboard Accessible: Make all functionality available from a keyboard.||Supports with exceptions||With a few exceptions, all our content is keybord accessible.|
|2.2 Enough Time: Provide users enough time to read and use content.||Supports||No content is time-sensitive.|
|2.3 Seizures: Do not design content in a way that is known to cause seizures.||Supports||No flashing content.|
|2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.||Supports with exceptions||Not all long list have relevant bypass blocks.
Not all links can be determined from link text alone.
Not all headers are descriptive or can be programmatically determined. (see 1.3)
|2.5 Input Modalities: Make it easier for users to operate functionality through various inputs beyond keyboard.||Supports with exceptions||Not all events are on the up event, making it harder to cancel the event.
Not all labels have a name that match the visual label.
Principle 3: Understandable
Information and the operation of user interface must be understandable.
|3.1 Readable: Make text content readable and understandable.||Supports|
|3.2 Predictable: Make web pages appear and operate in predictable ways.||Supports|
|3.3 Input Assistance: Help users avoid and correct mistakes.||Supports with exceptions||Not all instructions are accessible.|
Principle 4: Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
|4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.||Supports with exceptions||Not all status messages can be programmatically determined.|
Compatibility with Browsers and Assistive Technology
itslearning is designed to be compatible with the following assistive technologies:
- Chrome with Jaws on Windows
- Firefox with NVDA on Windows
- Safari with Voice Over on macOS
Accessibility of itslearning relies on the following technologies to work with a customer’s particular combination of web browser and any assistive technologies or plugins in use:
Limitations and alternatives
Despite our best efforts to ensure accessibility of itslearning, there may be some limitations. Please contact us at [email protected] with any feedback or if you encounter any accessibility barriers.
Our principal method of assessment was through a rigorous internal self-evaluation. An external evaluation of a sample of core functionality was performed by Funka in January 2019. Based on their feedback we have already improved text and color contrasts in many parts of the platform, and are working on improving consistency by introducing common components that are accessible.