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.0 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.0 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.0 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.1 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|
|A||1.1.1 – Non Text Content||Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.||Pass||90%||
A few exceptions noted. To be fixed by update in early-mid 2023.
|A||1.2.1 – Audio-Only and Video-Only||For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:
|A||1.2.2 – Captions (Pre-recorded)||Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.||Pass||95%||There are a small number of videos that don’t contain captions. Documented to be fixed in early-mid 2023.|
|A||1.2.3 – Audio Description or Media Alternative (Pre-recorded)||An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.||Pass||95%||There are a small number of videos that don’t contain descriptions of actions in the video.
Documented to be fixed in early-mid 2023.
|AA||1.2.4 – Captions (Live)||Captions are provided for all live audio content in synchronized media.||Pass||100%|
|AA||1.2.5 – Audio Description||Audio description is provided for all prerecorded video content in synchronized media.||Pass||90%|
|AAA||1.2.6 – Sign Language (Pre-recorded)||Sign language interpretation is provided for all prerecorded audio content in synchronized media.||Fail||0%|
|AAA||1.2.7 – Extended Audio Description (Pre-recorded)||Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.||Fail||0%|
|AAA||1.2.8 – Media Alternative (Pre- recorded)||An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.||Fail||0%|
|AAA||1.2.9 – Audio Only (Live)||An alternative for time-based media that presents equivalent information for live audio-only content is provided.||N/A||N/A|
|A||1.3.1 – Info and Relationships||Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.||Pass||90%||Some unlabeled elements found, location within a table is not accessible to screen readers. Documented to be
fixed in early-mid 2023.
|A||1.3.2 – Meaningful Sequence||When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.||Pass||100%|
|A||1.3.3 – Sensory Characteristics||Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound||Pass||90%||Some issues found within Kidspeak only/|
|A||1.4.1 – Use of Colour||Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.||Pass||100%|
|A||1.4.2 – Audio Control||If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.||Pass||100%|
|AA||1.4.3 – Contrast (Minimum)||The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
|Pass||90%||Several exceptions documented which will be fixed by a release in early-mid 2023.|
|AA||1.4.4 – Resize Text||Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality||Pass||95%||Transparent Language Education Edition only: When opening a class message after increasing the zoom to 200% the body of the message cannot be seen. Will be addressed in upcoming release in 2022.|
|AA||1.4.5 – Images of Text||If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:
|AAA||1.4.6 – Contrast (Enhanced)||The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:
|AAA||1.4.7 – Low or No Background Audio||For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:
|AAA||1.4.8 – Visual Presentation||For the visual presentation of blocks of text, a mechanism is available to achieve the following:
|AAA||1.4.9 – Images of Text (No Exception)||Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.||Pass||100%|
Principle 2 – Operable
User interface components and navigation must be operable.
|Level||Guideline||Description||Pass/Fail||Support Level||Notes On Exceptions|
|A||2.1.1 – Keyboard||All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.||Pass||95%||There are several areas in Transparent Language Online where keyboard operation of an element does not work correctly or lacks some aspect of functionality. These exceptions are almost entirely outside of the learning activities and not within the most commonly used areas of the system.
Exceptions to be addressed in updates in early-mid 2023.
|A||2.1.2 – No Keyboard Trap||If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.||Pass||100%|
|AAA||2.1.3 – Keyboard (No Exception)||All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes||Pass||100%|
|A||2.2.1 – Timing Adjustable||For each time limit that is set by the content, at least one of the following is true:
|A||2.2.2 – Pause, Stop, Hide||For moving, blinking, scrolling, or auto-updating information, all of the following are true:
|AAA||2.2.3 – No Timing||Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.||Pass||90%|
|AAA||2.2.4 – Interruptions||Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.||Pass||100%|
|AAA||2.2.5 – Re-authenticating||When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.||Fail||70%|
|A||2.3.1 – Three Flashes or Below||Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.||Pass||100%|
|AAA||2.3.2 – Three Flashes||Web pages do not contain anything that flashes more than three times in any one second period.||Pass||100%|
|A||2.4.1 – Bypass Blocks||A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.||Pass||100%|
|A||2.4.2 – Page Titled||Web pages have titles that describe topic or purpose.||Pass||100%|
|A||2.4.3 – Focus Order||If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.||Pass||90%||Some issues with mobile site layout on desktop and in a couple other areas. Issues to be addressed in early-mid 2023.|
|A||2.4.4 – Link Purpose (In Context)||The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.||Pass||100%||One exception noted that is to be fixed in a release in early-mid 2023.|
|AA||2.4.5 – Multiple Ways||More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.||Pass||100%|
|AA||2.4.6 – Headings and Labels||Headings and labels describe topic or purpose.||Pass||95%||One heading has is missing. To be fixed in by release in early-mid 2023.|
|AA||2.4.7 – Focus Visible||Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.||Pass||90%||There are several areas in Transparent Language Online where visible indication that an element is in focus is not clear. These exceptions are almost entirely outside of the learning activities and not within most commonly used areas of the system.
Exceptions to be addressed in updates throughout 2022.
|AAA||2.4.8 – Location||Information about the user’s location within a set of Web pages is available.||Pass||100%|
|AAA||2.4.9 – Link Purpose (Link Only)||A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.||Pass||90%|
|AAA||2.4.10 – Section Headings||Section headings are used to organize the content.||Pass||100%|
Principle 3 – Understandable
Information and the operation of user interface must be understandable.
|Level||Guideline||Description||Pass/Fail||Support Level||Notes on Exceptions|
|A||3.1.1 – Language of Page||The default human language of each Web page can be programmatically determined.||Pass||100%|
|AA||3.1.2 – Language of Parts||The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.||Pass||85%||Language tags missing for lesson titles, descriptions and vocab items. To be fixed by a release in early-mid 2023.|
|AAA||3.1.3 – Unusual Words||A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.||Pass||100%|
|AAA||3.1.4 – Abbreviations||A mechanism for identifying the expanded form or meaning of abbreviations is available.||Pass||100%|
|AAA||3.1.5 – Reading Level||When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.||Pass||100%|
|AAA||3.1.6 – Pronunciation||A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.||Pass||90%|
|A||3.2.1 – On Focus||When any component receives focus, it does not initiate a change of context.||Pass||100%|
|A||3.2.2 – On Input||Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.||Pass||100%|
|AAA||3.2.3 – Consistent Navigation||Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.||Pass||100%|
|AA||3.2.4 – Consistent Identification||Components that have the same functionality within a set of Web pages are identified consistently.||Pass||100%|
|AAA||3.2.5 – Change on Request||Changes of context are initiated only by user request or a mechanism is available to turn off such changes.||Fail||70%|
|A||3.3.1 – Error Identification||If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.||Pass||100%|
|A||3.3.2 – Labels or Instructions||Labels or instructions are provided when content requires user input.||Pass||100%||Some fields found without labels or with screen reader incompatible labels. Documented to be fixed in early-mid 2023.|
|AA||3.3.3 – Error Suggestion||If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.||Pass||100%|
|AA||3.3.4 – Error Prevention (Legal, Financial, Data)||For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:
|AAA||3.3.5 – Help||Context-sensitive help is available.||Pass||100%|
|AAA||3.3.6 – Error Prevention (All)||For Web pages that require the user to submit information, at least one of the following is true:
Principle 4 – Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
|A||4.1.1 – Parsing||In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.||Pass||100%|
|A||4.1.2 – Name, Role, Value||For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.||Pass||90%||A few elements are missing programmatically
determinable labels. Some checkboxes can’t be read by