Accessibility
Alludo is a web-based platform that presents two key sources of content: platform-generated content and user-generated content. Platform-generated content manages and presents user generated content and is relatively static. The Alludo Web Content Checklist (below) covers platform-generated content.
User generated content is managed with the Froala WYSIWYG editor. The Froala editor provides extremely robust accessibility functionality. Click here to review the Froala editor accessibility support.
Alludo Web Content Accessibility Guidelines (WCAG 2.0) Checklist
This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Alludo’s conformance with the WCAG 2.0 standards, level AA.
Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Criteria |
Support Details |
Comments |
|---|---|---|
| 1.1 Text Alternatives: Provide text alternatives for any non-text content. | Supports with exceptions | Some elements do not have appropriate text alternatives. |
| 1.2 Time-based Media: Provide alternatives for time-based media. | N/A | |
| 1.3 Adaptable: Create content that can be presented and navigated in different ways. | Supports with exceptions | Some labels or instructions are not associated correctly, or the information presented to screen reader users is not equivalent. Reading and navigation order is usually logical and intuitive. |
| 1.4 Distinguishable: Make it easier for users to see and hear content, including adequately separating the foreground from the background. | Supports with exceptions | Color is not used as the sole method of conveying content. There are a few instances of text with insufficient contrast, even with high contrast settings enabled. |
Principle 2: Operable
User interface components and navigation must be operable.
Criteria |
Support Details |
Comments |
|---|---|---|
| 2.1 Keyboard Accessible: Make all functionality available from a keyboard. | Supports with exceptions | Most, but not all, content is keyboard accessible. |
| 2.2 Enough Time: Provide users enough time to read and use content. | Supports | Time-sensitive content was not encountered. |
| 2.3 Seizures: Do not design content in a way that is known to cause seizures. | Supports | Content does not flash. |
| 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are. | Supports |
Principle 3: Understandable
Information and the operation of user interface must be understandable.
Criteria |
Support Details |
Comments |
|---|---|---|
| 3.1 Readable: Make text content readable and understandable. | Supports with exceptions | Most platform pages have language specified |
| 3.2 Predictable: Make web pages appear and operate in predictable ways. | Supports | For the most part, navigation is consistent throughout the application. |
| 3.3 Input Assistance: Help users avoid and correct mistakes. | Supports with exceptions |
Important labels and instructions are not always 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.
Criteria |
Support Details |
Comments |
|---|---|---|
| 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies. | Supports with exceptions | HTML validation issues do not impact accessibility. |