The following is a list of Accessibility improvements made in the October 2023 release:

Keyboard focus / Interactive elements 

Interactive elements have been made entirely compatible with a keyboard. Improvements made:  

• Focus is appropriately managed when page is dynamically updated - Login/Public Pages 
• Interactive elements now have an accessible name - Dashboard
• Interactive elements are provided with appropriate names - Signatures Grid 
• Interactive elements now have an accessible name - Signatures Grid 
• Interactive elements now have an accessible name - Learning Plan 
• Interactive element now has accessible role - Learning Plan 
• Power BI Reports - Interactive elements receive keyboard focus - Caseload Dashboard
• Power BI Reports - Interactive elements receive keyboard focus - Compliance Dashboard 
• Power BI Reports - Interactive elements receive keyboard focus - Employ Dashboard
• Power BI Reports - Interactive elements receive keyboard focus - Funding Dashboard
• Power BI Reports - Interactive elements receive keyboard focus - Quality Dashboard
• Power BI Reports - Tooltip is activated with keyboard – Funding Dashboard
• Power BI Reports - Tooltip is activated with keyboard – Quality Dashboard
• Disabled state buttons now have grey border colour.

Alternative text 

Non-text content must have appropriate alternatives. This is required for the content to be understood by all users. Images, icons and so on may otherwise be miscommunicated by assistive technology. There were informative icons that had no text alternative. Improvements made:  

• Informative image offers appropriate text alternative - Login/Public Pages

Programmatically unidentified element 

Interactive elements need a programmatically determined name, role, and value. These properties must also be accurate and appropriate. Improvements made:  

• Menu semantics appropriately used on list box - Dashboard 
• Selected element is programmatically identified in list boxes - Dashboard 
• Current element is programmatically identified - Signatures Grid
• Error message is associated with input fields - File Uploader 
• Menu semantics are used appropriately on list box - Signatures Grid 
• Menu semantics are used appropriately on list box - Learning Plan 
• Selected element is programmatically identified in list boxes - Signatures Grid
• Selected element is programmatically identified in list boxes - Learning Plan
• Current element is programmatically identified - Tasks
• Current element is programmatically identified - Resource Centre 
• Current page is programmatically identified - Learners Profile

Contrast 

When components have custom focus indication, such as a custom ‘outline’, the indication must pass colour contrast requirements with adjacent colours. Improvements made: 

• Regular text has sufficient contrast - Filters
• Custom focus indication contrast (background change) - Learning Plan 
• Custom focus indication contrast (grey/yellow outline) - Skills Radar

Heading  

If a relationship between elements is expressed with visual cues, it also needs to be programmatically determined. This enables assistive technology to communicate the relationships to users. Improvements made: 

• Heading marked up semantically - Enrolment Heading
• Accordion heading marked up semantically - Login/Public Pages

Hidden content 

When content has a meaningful order, an appropriate reading order needs to be programmatically determined. This enables those using assistive technology to effectively navigate the content and understand it. Improvements made: 

• Hidden content no longer exposed to assistive technology - Signatures Grid