Technical information about this website’s accessibility
Compliance status
These website(s) are partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reason(s):
(a) non-compliance with the accessibility regulations
Some navigation components currently deviate from WAI-ARIA authoring best practices—specifically regarding roles such as menubar and menuitem. While these elements may not be semantically optimal, they have been tested to confirm full keyboard navigation and operability with screen readers. We are actively reviewing these components and are working with our supplier to improve their semantic structure.
When viewing a saved application, the menu includes options to print or withdraw. These buttons are correctly labelled and fully operable via assistive technologies. However, automated accessibility tests have flagged them as not meeting the recommended minimum tap target size—specifically, that interactive elements should be at least 24px and appropriately spaced.
The portal’s data collection form is divided into six sections, with section headings presented as a navigable list. These headings are currently implemented using <input> elements, which are not semantically suitable for conveying structural hierarchy. Consequently, some assistive technologies may not recognize or announce them properly.
Testing has shown that SilkTide’s screen reader was unable to detect the section titles, whereas Windows' built-in Narrator performed more reliably and was able to identify all items. We are engaging with our third-party vendor to explore more accessible structural alternatives.
Additionally, we are aware of a read-only field containing the student ID number. This field is not navigable using the tab key, and browser-based screen readers have difficulty announcing its content.
If you encounter any issues with heading or field detection, we recommend using the screen reading functionality provided by your operating system, which has demonstrated more consistent performance than browser-based plugins.
These issues have been raised with our vendor, and we are awaiting a resolution. This statement will be updated as progress is made.
