As the Transparent Language Online system updates existing functionality and develops new capabilities, we methodically address the support of accessibility for learners with special needs. Transparent Language Online has not been tested for WCAG 2.2 compliance by third-party experts, although good programming practices and our own on-going internal testing, we are working to support more and more aspects of WCAG 2.2 compliance. Our team is building knowledge of these standards, so that where feasible we can support the broadest possible access to our learning system. Below is a listing of the WCAG 2.2 criteria for software application and web sites with our current assessment of Transparent Language Online status for each criterion. Any documented issues below will be fixed through our development process in the future.
For the breakdown of the WCAG 2.0 success criteria, click here.
For the breakdown of the WCAG 2.1 success criteria, click here.
Principle 2 – Operable
User interface components and navigation must be operable.
| Level | Guideline | Description | Pass/Fail | Support Level | Notes on Exceptions |
|---|---|---|---|---|---|
| AA | 2.4.11 Focus Not Obscured (minimum) | When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. | Pass | 90% | Most menus/modals are compliant. There are several issues documented to be fixed. Two have to do with menus not closing when they lose focus. There are two issues specific to tablets where menus extend off the page with keyboard navigation. Two mobile specific issues. |
| AA | Dragging Movements | All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. | Fail | 50% | Some areas of the application have no option to rearrange content with cursor without dragging. Several tasks entered to approve that. |
| AA | Target Size (Minimum) | Make controls easier to activate. Ensure targets meet a minimum size or have sufficient spacing around them. | Pass | 99% | Only one date picker menu is too small in a section of the application that isn't heavily used. To be fixed. |
Principle 3 – Understandable
Information and the operation of user interface must be understandable.
| Level | Guideline | Description | Pass/Fail | Support Level | Notes on Exceptions |
|---|---|---|---|---|---|
| A | If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism. |
Pass | 99% | One issue with consistency in a place not frequented by many users. To be fixed. | |
| AA | Accessible Authentication (Minimum) | A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test. Object Recognition The cognitive function test is to recognize objects. Personal Content The cognitive function test is to identify non-text content the user provided to the Web site. |
Pass | 100% |
