Accessibility And Usability Compliance with WCAG Guidelines
Under the Disability Discrimination Act 1992, all organizations are required to ensure that the information and services are provided in a non-discriminatory accessible manner. As part of this, all Commercial-off-the-Shelf (COTS) software applications or Software as a Service (SaaS) must conform to Web Content Accessibility Guidelines (WCAG) 2.0 at levels A and AA and be compatible with Adaptive Technology (AT). The Web Content Accessibility Guidelines have been developed by the World Wide Web Consortium (W3C) under the Web Accessibility Initiative (WAI). The WAI develops strategies, guidelines, and resources to help make the Web (and web-based services) accessible to people with disabilities.
This document will help you in getting a better understanding of how Outgrow is compatible with Accessibility, Usability, and Adaptive Technology-related WCAG 2.0 guidelines.
Conformance to WCAG 2.0
A. Table shown below highlights how Outgrow is compliant with Level A Guidelines under WCAG 2.0 regulation:
| Guideline | Description | Compliant / Not Compliant | Additional Comments |
|---|---|---|---|
| 1.1.1 – Non-text Content | Text alternatives provided for non-text content | We are 100% compliant with this guideline. | |
| 1.2.1 – Audio-only and Video-only (Pre-recorded) | Alternatives provided for video-only and audio-only content. | We are 100% compliant with this guideline. | You can add video on the results or questions page, and can add alternative text for the video. |
| 1.2.2 – Captions (Pre-recorded) | Captions provided for videos with audio | We are 100% compliant with this guideline. | Outgrow supports 3rd party video platforms. The setting for displaying subtitles for the video needs to be enabled in the respective video platform. |
| 1.2.3 – Audio Description or Media Alternative (Pre-recorded) | Video with audio has a second alternative | We are 100% compliant with this guideline. | For each video that is added in the content by the user, an alternative text can be added using the questions text, help text or results page text field in the Outgrow builder dashboard. |
| 1.3.1 – Info and Relationships | Logical structure | We are 100% compliant with this guideline. | Our logical structure is in compliance with ADA/WCAG guidelines. |
| 1.3.2 – Meaningful Sequence | Content presented in a meaningful order | We are 100% compliant with this guideline. | |
| 1.3.3 – Sensory Characteristics | More than one sense is used for instructions. | We are 100% compliant with this guideline. | |
| 1.4.1 – Use of Colour | Presentations do not rely solely on colour | We are 100% compliant with this guideline. | |
| 1.4.2 – Audio Control | Audio does not play automatically | We are 100% compliant with this guideline. | |
| 2.1.1 – Keyboard | All content functionality is available through the keyboard interface. (Keyboard shortcuts are easily located in product menus) | We are 100% compliant with this guideline. | All content functionality is available through the keyboard interface. |
| 2.1.2 – No Keyboard Trap | No keyboard traps | We are 100% compliant with this guideline. | |
| 2.2.1 – Timing Adjustable | Time limits have user controls | We are 100% compliant with this guideline. | |
| 2.2.2 – Pause, Stop, Hide | User controls provided for moving content | We are 100% compliant with this guideline. | |
| 2.3.1 – Three Flashes or Below Threshold | No content flashes more than three times per second | We are 100% compliant with this guideline. | We don't support flashing of content in Outgrow. |
| 2.4.1 - Bypass Blocks | Provide a ‘Skip to Content’ link | We are 100% compliant with this guideline. | |
| 2.4.2 – Page Titled | Helpful and clear page titles | We are 100% compliant with this guideline. | |
| 2.4.3 – Focus Order | Logical order | We are 100% compliant with this guideline. | |
| 2.4.4 – Link Purpose (In Context) | Every link’s purpose is clear from its context | We are 100% compliant with this guideline. | |
| 3.1.1 – Language of Page | Page has a language assigned | We are 100% compliant with this guideline. | |
| 3.2.1 – On Focus | Elements do not change when they receive focus (Pop-up forms should be customisable in size and position when receiving focus) | We are 100% compliant with this guideline. | |
| 3.2.2 – On Input | Elements do not change when they receive input | We are 100% compliant with this guideline. | |
| 3.3.1 – Error Identification | Clearly identified input errors | We are 100% compliant with this guideline. | |
| 3.3.2 – Labels or Instructions | Elements are labelled and give instructions | We are 100% compliant with this guideline. | |
| 4.1.1 – Parsing | No major code errors | We are 100% compliant with this guideline. | |
| 4.1.2 – Name, Role, Value | All elements are built for accessibility | We are 100% compliant with this guideline. | We display hard and soft warnings in the Outgrow builder and content. |
B. Table shown below highlights how Outgrow is compliant with Level AA Guidelines under WCAG 2.0 regulation:
| Guideline | Description | Compliant / Not Compliant | Additional Comments |
|---|---|---|---|
| 1.2.4 – Captions (Live) | Live videos have captions | We are 100% compliant with this guideline. | Outgrow supports 3rd party video platforms. The setting for displaying subtitles for the video needs to be enabled in the respective video platform. |
| 1.2.5 – Audio Description (Pre-recorded) | Users have access to audio description for video content. | N/A | For each video that is added in the content by the user, an alternative text can be added using the questions text, help text or results page text field in the Outgrow builder dashboard. |
| 1.4.3 – Contrast (Minimum) | Contrast ratio between text and background is at least 4.5:1 (Adjustable font colour, colour scheme and adjustable high contrast between font and background) | We are 100% compliant with this guideline. | |
| 1.4.4 – Resize Text | Text can be resized to 200% without loss of content or function (Default font size is greater than or equal to 3mm and font type and colour are adjustable) | We are 100% compliant with this guideline. | |
| 1.4.5 – Images of Text | No images of text are used. | We are 100% compliant with this guideline. | |
| 2.4.5 – Multiple Ways | Several ways to find pages/tabs are offered | We are 100% compliant with this guideline. | Outgrow content follows a step by step approach. |
| 2.4.6 – Headings and Labels | Headings and labels are clear. | We are 100% compliant with this guideline. | |
| 2.4.7 – Focus Visible | Keyboard focus is visible and clear | We are 100% compliant with this guideline. | |
| 3.1.2 – Language of Parts | Users advised when the language on a page changes. | We are 100% compliant with this guideline. | |
| 3.2.3 – Consistent Navigation | Menus used consistently (Navigation aids [buttons, hyperlinks etc.]. are clearly visible and correctly labelled. Tab sequences are logical and enables activation of controls). | We are 100% compliant with this guideline. | |
| 3.2.4 – Consistent Identification | Icons and buttons are used consistently (All fields are clearly labelled and/or identified). | We are 100% compliant with this guideline. | |
| 3.3.3 – Error Suggestion | Fixes are suggested when users make errors | We are 100% compliant with this guideline. | |
| 3.3.4 – Error Prevention (Legal, Financial, Data) | Risk of input errors for sensitive data is reduced | We are 100% compliant with this guideline. | Risks are checked to ensure errors are reduced. |
IMPORTANT NOTE
1. We offer text magnification using ZoomText.
2. For visually impaired users, we support the usage of Screen Reader using JAWS for Windows.
Feel free to use our chat tool on the bottom right or reach out to us at [email protected] in case you have any questions, and our team can help you with a quick solution.
Updated about 1 year ago