The following accessibility issues are known to affect parts of this website. We are actively working to identify, prioritise and resolve these issues as part of our ongoing commitment to accessibility and compliance with WCAG 2.2 AA. The list below summarises areas where we currently only partially conform, or do not yet conform, to the relevant success criteria. This applies to both the website itself and embedded or downloadable PDF files.
Guideline 1: Perceivable
- 1.1.1 Non-Text Content
Not all non-text content has relevant or useful alternative text.
- 1.2.2 Captions
Not all pre-recorded videos have captions provided.
- 1.2.3 Audio Description or Media Alternative
Not all pre-recorded videos have a transcript or alternate audio description.
- 1.3.1 Info and Relationships
Not all relationships, structure and information are conveyed in a way that can be interpreted by assistive technologies.
- 1.3.2 Meaningful Sequence
In some areas, the sequence of content is not always programmatically determined, which may affect navigation for keyboard and assistive technology users.
- 1.4.3 Contrast (Minimum)
A small amount of specific content does not meet the minimum required contrast.
- 1.4.13 Content on Hover or Focus
Additional content displayed within our navigation menu cannot currently be dismissed using the Escape key, which may obscure content beneath it.
Guideline 2: Operable
- 2.1.1 Keyboard
Not all functionality and navigation is fully operable through keyboard-only input.
- 2.2.2 Pause, Stop, Hide
Not all automatically updating or dynamic content is available to pause, stop or hide natively.
- 2.4.1 Bypass Blocks
We do not currently provide a mechanism to bypass repeated content, such as the main navigation menu, for keyboard and assistive technology users.
- 2.4.3 Focus Order
Focusable components do not always receive focus in the correct order.
- 2.4.4 Link Purpose (In Context)
The purpose of some links may not be clear from their text or surrounding context.
- 2.5.7 Dragging Movements
Some content on mobile devices does not have an alternative usage method to dragging movements.
Guideline 3: Understandable
- 3.2.2 On Input
In some cases, changing a form field or user interface component may trigger a change of context without prior warning.
- 3.3.1 Error Identification
Input errors may not always be identified and described to the user with text.
- 3.3.2 Labels or Instructions
Required user input may not always be given context via labels or instructions.
Guideline 4: Robust
- 4.1.2 Name, Role, Value
Not all user interface components have names and roles that can be programmatically determined. Their states, properties and values may also not be correctly exposed to assistive technologies.
- 4.1.3 Status Messages
Status messages cannot always be programmatically determined, and therefore cannot be presented to the user by assistive technologies without receiving focus.
We are actively reviewing and addressing these issues as part of our ongoing accessibility improvement work. Where possible, accessibility issues are prioritised according to their impact on users and the complexity of remediation.