In this section
In this page
Known accessibility issues (learn.jbs)
Below we list learn.jbs elements that we know are not fully accessible and do not meet the WCAG success criteria, as well as what action we are taking to resolve the issue or if is not in scope at this time.
Issues with text
Line height
It is not possible for users to modify text spacing or line height (1.4.12 Text Spacing). We are working to update our themes and plugins to correct these issues.
Sufficient colour contrast
Some text and background combinations do not have sufficient contrast (1.4.3 Contrast). We have a work plan to themes and plugins to correct these issues.
Links
Some pages and document links are not meaningful, meaning it is not clear where the link with take you and does not make sense when it is read or listened to on its own (2.4.4 Link Purpose). We are working with content providers to create accessible versions of these documents and web content.
Buttons
Some buttons include text without the accessible name, the label, alternative text, aria-label, etc., in the visible text (2.5.3 Label in Name). We are working to update our themes and plugins to correct these issues where they are caused by issues with the theme code.
Issues with documents and other files
Some of our uploaded documents and other files that are essential to providing our services, do not meet accessibility standards. For example, they may not be accessible to screen readers.
We have a plan to either re-work these documents to make them accessible or replace them with accessible HTML pages wherever possible. Any new PDFs or Word documents we publish will meet accessibility requirements standards.
The accessibility regulations do not require us to re-work PDFs or other documents published before 23 September 2018 if they are not essential to providing our services. We are working with content providers to create accessible versions of these documents.
If you have trouble accessing these documents, you can refer to the guidance on how to create alternative accessible formats with Sensus access. This service is designed to allow disabled students and staff (or those supporting them) to create accessible alternative formats from inaccessible digital documents. We are working with content providers to create accessible versions of these documents.
Tables
There are some Excel documents and embedded tables that contain merged cells that are not accessible to some screen reader software (1.3.1 Info and Relationships). We are working with content creators to make accessible versions of the documents.
Document structure
Many of our PDFs and other documents do not meet accessibility standards. They may lack headings, page navigation, mark up, or structure in a way that is accessible to a screen reader. This includes documents (1.3.1 Info and Relationships). PDFs and other documents published before 23 September 2018 and any inactive courses are unlikely to be re-worked for accessibility issues unless they are essential to providing teaching and learning services.
Colour to convey meaning
Some of our documents have diagrams that use colour as the only means of conveying information. The information in these diagrams may not be perceived by users with colour deficiencies (1.4.1 Use of Colour).
Images of text
Some of our documents included images of text (1.4.5 Images of Text). We are working with content providers to create accessible versions of these documents.
Sufficient colour contrast
Some of our documents have diagrams that do not meet the colour contrast ratio of at least 3:1. (1.4.11 Non-test Contrast). We are working with content creators to create accessible versions of these diagrams.
Images, pre-recorded video, and audio
Some images in learn.jbs do not have appropriate alternative text. We plan to make relevant non-decorative images compliant.
Transcripts and captions
Some videos and audio in learn.jbs do not have the required caption controls or transcriptions available. (1.2.1 Audio-only and Video-only (Prerecorded), 1.2.2 Captions (Prerecorded), 1.2.3 Audio Description or Media Alternative (Prerecorded), 1.2.4 Captions (Live) and 1.2.5 Audio Description (Prerecorded)). We have changed our workflow to include transcripts and captions for all new videos and audio. For all new videos we will ensure closed captions and provide a transcript for all new videos. We use YouTube and Vimeo to embed video onto our webpages: We are not responsible for the accessibility of YouTube or Vimeos platforms.
Alternative text on images
Some images on our website do not have appropriate alternative text. We plan to make relevant non-decorative images compliant to the accessibility guidlines. Where we add new images, these will be made to meet accessibility standards.
We plan for all new images, shapes, and graphics to meet accessibility standards.
Live video
We do not provide closed captions to live video streams and do not plan to include then as part of our accessibility roadmap because live streams are exempt from the accessibility requirements.
Issues with focus indicator
Some elements do not always display effective focus indications when links, buttons, and other active controls receives focus. (2.4.7 Focus Visible). We are running manual and automated evaluations and adjusting focus indicators to ensure they meet the accessibility requirments.
Interactive tools and transactions
Navigation
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a label tag. (3.3.2 Labels or instructions). We are running manual and automated accessibility evaluations to identify where navigation with the keyboard is difficult and adjusting its mark-up.
Description tags
Some of our interactive elements do not have the required descriptive tags. This means some of our interactive elements do not inform screen reader users of the current state of the element.
We plan to make all existing interactive elements compliant. When we launch new interactive elements, we will make sure they meet this accessibility standard.