|
Details of the non-compliance
|
WCAG 2.1 Success Criteria Failure
|
How we will resolve
|
|
We do not provide a descriptive text transcript (including all relevant visual and auditory clues and indicators) for non-live, web-based audio.
|
This fails WCAG 2.1 success criterion 1.2.1 (Audio-only and Video-only (Pre-recorded))
|
All new content we create after 23rd September 2020 will satisfy WCAG 2.1 success criterion 1.2.1 (Audio-only and Video-only (Pre-recorded)) .
|
|
We do not provide a descriptive text transcript OR an audio description audio track for non-live, web-based video.
|
This fails WCAG 2.1 success criterion 1.2.3 (Audio Description or Media Alternative (Pre-recorded))
|
All new content we create after 23rd September 2020 will satisfy WCAG 2.1 success criterion 1.2.3 (Audio Description or Media Alternative (Pre-recorded)) .
|
|
We do not provide audio descriptions for all video content
|
This fails WCAG 2.1 success criterion 1.2.5 (Audio Description (Pre-recorded))
|
We are aiming to satisfy WCAG 2.1 success criterion 1.2.5 (Audio Description (Pre-recorded)) by February 2021.
|
|
We do not provide a sign language video for all media content that contains audio.
|
This fails WCAG 2.1 success criterion 1.2.6 (Sign Language (Pre-recorded))
|
We will assess future content to understand whether we are able to meet this standard.
|
|
When an audio description track cannot be added to video due to audio timing (e.g., no pauses in the audio), we do not provide an alternative version of the video with pauses that allow audio descriptions is provided.
|
This fails WCAG 2.1 success criterion 1.2.7 (Extended Audio Description (Pre-recorded))
|
We will assess future content to understand whether we are able to meet this standard.
|
|
We do not provide a descriptive text transcript for all pre-recorded synchronized media. We only provide a descriptive text transcript for all pre-recorded media that has a video track
|
This fails WCAG 2.1 success criterion 1.2.8 (Media Alternative (Pre-recorded))
|
We will assess future content to understand whether we are able to meet this standard.
|
|
Not all of our pages are readable and functional when the text size is doubled.
|
This fails WCAG 2.1 success criterion 1.4.4 (Resize text)
|
We are aiming to satisfy WCAG 2.1 success criterion 1.4.4 (Resize text) by the end of February 2021.
|
|
We have not produced audio of speech with no or very low background noise so the speech is easily distinguished.
|
This fails WCAG 2.1 success criterion 1.4.7 (Low or No Background Audio)
|
We will assess future content to understand whether we are able to meet this standard.
|
|
We use images of text for purposes other than for pure decoration ( or where a particular presentation of text is essential to the information being conveyed..
|
This fails WCAG 2.1 success criterion 1.4.9 (Images of Text (No Exception))
|
We will assess future content to understand whether we are able to meet this standard.
|
|
Not all page functionality is available using the keyboard.
|
This fails WCAG 2.1 success criterion 2.1.3 (Keyboard (No Exception))
|
We will assess future content to understand whether we are able to meet this standard.
|
|
Automatically moving, blinking, or scrolling content that lasts longer than 5 seconds cannot be paused, stopped, or hidden by the user.
|
This fails WCAG 2.1 success criterion 2.2.2 (Pause, Stop, Hide).
|
We are aiming to satisfy WCAG 2.1 success criterion 2.2.2 (Pause, Stop, Hide). by the end of February 2021.
|
|
Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) cannot be paused, stopped, or hidden by the user nor can the user manually control the timing of the updates.
|
This fails WCAG 2.1 success criterion 2.2.2 (Pause, Stop, Hide).
|
We are aiming to satisfy WCAG 2.1 success criterion 2.2.2 (Pause, Stop, Hide).by the end of February 2021.
|
|
It is not visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can not see where you are).
|
This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible)
|
We are aiming to satisfy WCAG 2.1 success criterion 2.4.7 (Focus Visible) by the end of February 2021.
|
|
Where the web page is part of a sequence of pages or within a complex site structure, there is no indication of the current page location, for example, through breadcrumbs or specifying the current step in a sequence (e.g., "Step 2 of 5 - Shipping Address").
|
This fails WCAG 2.1 success criterion 2.4.8 (Location)
|
We are aiming to satisfy WCAG 2.1 success criterion 2.4.8 (Location) by the end of February 2021.
|
|
There are links (or form image buttons) with the same text that go to different locations.
|
This fails WCAG 2.1 success criterion 2.4.9
|
We are aiming to satisfy WCAG 2.1 success criterion 2.4.9 by the end of February 2021.
|
|
The language of page content that is in a different language is not currently identified using the lang attribute (e.g., <blockquote lang="es">).
|
This fails WCAG 2.1 success criterion 3.1.2 (Language of Parts)
|
We are aiming to satisfy WCAG 2.1 success criterion 3.1.2 (Language of Parts)
by the end of February 2021.
|
|
Words that may be ambiguous, unknown, or used in a very specific way are not always defined through adjacent text, a definition list, a glossary, or other suitable methods.
|
This fails WCAG 2.1 success criterion 3.1.3 (Unusual Words)
|
We will assess future content to understand if we wish to meet this standard.
|
|
Expansions for abbreviations are not provided by expanding or explaining the definition the first time it is used, using the <abbr> element, or linking to a definition or glossary.
|
This fails WCAG 2.1 success criterion 3.1.4 (Abbreviations)
|
We will assess future content to understand if we wish to meet this standard.
|
|
A more understandable alternative is not provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
|
This fails WCAG 2.1 success criterion 3.1.5 (Reading Level)
|
We will assess future content to understand if we wish to meet this standard.
|
|
If the pronunciation of a word is vital to understand that word, its pronunciation is not provided immediately following the word or via a link or glossary.
|
This fails WCAG 2.1 success criterion 3.1.6 (Pronunciation)
|
We will assess future content to understand if we wish to meet this standard.
|