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.1 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.1 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.1 criteria for software application and web sites with our current assessment of Transparent Language Online status for each criteria.
For the breakdown of WCAG 2.0 success criteria, Click here.
Principle 1 – Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
|Level||Criteria||Description||Pass/Fail||Support Level||Notes On Exceptions|
|AA||1.3.4 Orientation||Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.||Pass||100%|
|AA||1.3.5 Identify Input Purpose||The purpose of each input field collecting information about the user can be programmatically determined when:
- The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
|AA||1.4.10 Reflow||Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
- Vertical scrolling content at a width equivalent to 320 CSS pixels;
- Horizontal scrolling content at a height equivalent to 256 CSS pixels.
Except for parts of the content which require two-dimensional layout for usage or meaning.
|AA||1.4.11 Non-Text Contrast||The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
- User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
- Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
|AA||1.4.12 Text Spacing||-Line height (line spacing) to at least 1.5 times the font size;
-Spacing following paragraphs to at least 2 times the font size;
-Letter spacing (tracking) to at least 0.12 times the font size;
-Word spacing to at least 0.16 times the font size.
|Pass||90%||Changing text spacing can cause UI misalignment in some instances.
To be addressed in upcoming release in early-mid 2023.
|AA||1.4.13 Content on Hover or Focus||Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
- Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
- Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.
|Pass||95%||Two small issues with non-compliant info tooltips. To be addressed in upcoming release in early-mid 2023.|
Principle 2 – Operable
User interface components and navigation must be operable.
|A||2.1.4 Character Key Shortcuts||If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
A mechanism is available to turn the shortcut off;
A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
Active only on focus
The keyboard shortcut for a user interface component is only active when that component has focus.
|Pass||95%||One violation found, issue to be fixed by release in early-mid 2023.|
|AAA||2.2.6 Timeouts||Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.||N/A||N/A|
|AAA||2.3.3 Animation from Interactions||Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality, or the information being conveyed.||N/A||N/A|
|A||2.5.1 Pointer Gestures||All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.||N/A||N/A|
|A||2.5.2 Pointer Cancellation||For functionality that can be operated using a single pointer, at least one of the following is true:
- No Down-Event: The down-event of the pointer is not used to execute any part of the function;
- Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
- Up Reversal: The up-event reverses any outcome of the preceding down-event;
- Essential: Completing the function on the down-event is essential.
|A||2.5.3 Label in Name||For user interface components with labels that include text or images of text, the name contains the text that is presented visually.||Pass||90%|
|A||2.5.4 Motion Actuation||Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
- Supported Interface: The motion is used to operate functionality through an accessibility supported interface;
- Essential: The motion is essential for the function and doing so would invalidate the activity.
|AAA||2.5.5 Target Size||The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:
- Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
- Inline: The target is in a sentence or block of text;
- User Agent Control: The size of the target is determined by the user agent and is not modified by the author;
- Essential: A particular presentation of the target is essential to the information being conveyed.
|AAA||2.5.6 Concurrent Input Mechanisms||Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.||N/A||N/A|
Principle 4 – Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
|AA||4.1.3 Status Messages||In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.||Pass||95%||Some feedback messages and status messages
unreadable by screen readers.