The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
1. Buttons without discernible text
Pagination controls on listing pages (including news and course search) contain icon-only buttons that have no visible label, aria-label, aria-labelledby, or title attribute. Screen reader users cannot determine the purpose of these buttons.
This fails WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (Level A).
We plan to fix this in a future scheduled website release.
2. Select element without an accessible name
A sort-order dropdown on search and listing pages has no associated label, aria-label, or aria-labelledby attribute. Screen reader users cannot determine the purpose of this control.
This fails WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (Level A).
We plan to fix this in a future scheduled website release.
3. Insufficient colour contrast
Several brand colours used across the site fail minimum contrast requirements:
Text and headings in a yellow-green colour (#c1d522) on a white background achieve a contrast ratio of 1.63:1, far below the required 3:1 for large text and 4.5:1 for normal text.
Buttons and text elements using a yellow colour (#edbd03) on a white background achieve a contrast ratio of 1.76:1.
These issues affect a large number of pages across the site.
These fail WCAG 2.2 Success Criterion 1.4.3 Contrast (Minimum) (Level AA).
We plan to fix this in a future scheduled website release.
4. Links without discernible text
A number of links across the site use only an SVG icon as their visible content. Where the icon has aria-hidden="true" and no aria-label, aria-labelledby, title, or screen-reader-only text is provided, these links have no accessible name. Screen reader users cannot determine the destination or purpose of these links.
This fails WCAG 2.2 Success Criterion 2.4.4 Link Purpose (In Context) (Level A) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (Level A).
We plan to fix this in a future scheduled website release.
5. Touch target size below minimum
A number of interactive elements across the site — including links and buttons — have a clickable/touch target area smaller than the 24×24 CSS pixel minimum required by WCAG 2.2. This can make navigation difficult for users with motor impairments on touch devices.
This fails WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum) (Level AA).
We plan to fix this in a future scheduled website release.
6. Form inputs without labels
One or more form fields across the site do not have an associated visible label or accessible name. Users of screen readers cannot determine the purpose of these fields without independently identifying the surrounding context.
This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (Level A) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (Level A).
We plan to fix this in a future scheduled website release.
7. Frames without titles
A small number of <iframe> elements on the site do not have a title attribute. This makes it impossible for screen reader users to identify the purpose of the embedded content before navigating into it.
This fails WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (Level A).
We plan to fix this in a future scheduled website release.
8. Improper list structure
On some pages, list elements (<ul> or <ol>) contain child elements that are not <li> items. This can cause screen readers to misreport the number of list items or skip content entirely.
This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (Level A).
We plan to fix this in a future scheduled website release.
9. Missing language attribute on HTML element
On a small number of pages, the <html> element does not have a lang attribute declaring the primary language of the page. Screen readers and translation tools rely on this attribute to interpret and render content correctly.
This fails WCAG 2.2 Success Criterion 3.1.1 Language of Page (Level A).
We plan to fix this in a future scheduled website release.
10. Navigation menus and expandable content not keyboard accessible
Several areas of the site cannot be reached or used with keyboard navigation alone. The Tab key skips past the "Study Areas" and "Term Dates" navigation items; pressing Enter or Space does not open the dropdown menus; and once opened via mouse, the dropdowns cannot be closed using the Escape key. On the "How to Apply For a Course" page, Tab navigation reaches only the page header and footer — expandable FAQ sections and dropdowns within the main content cannot be reached or operated via keyboard. Course detail dropdowns on "View Course" pages are similarly skipped by Tab. On the Contact Us page, the Enquiry Form's "Reason for Enquiry" field options are skipped by Tab navigation, making it impossible to complete the form using keyboard only.
This fails WCAG 2.2 Success Criterion 2.1.1 Keyboard (Level A).
We plan to fix this in a future scheduled website release.
11. Cookie consent banner not fully keyboard accessible
The cookie preferences panel cannot be dismissed using the Escape key and must be closed by pressing Enter on the close (×) button only.
This may involve a third-party cookie management component; we are investigating what direct control is available.
This fails WCAG 2.2 Success Criterion 2.1.1 Keyboard (Level A).
We plan to fix this in a future scheduled website release.
12. Hover-triggered navigation content cannot be dismissed
Navigation dropdowns that appear on mouse hover cannot be dismissed by pressing the Escape key while the pointer remains in that area. Users with low vision who use screen magnification, or those who trigger a dropdown inadvertently, cannot easily dismiss the content.
This fails WCAG 2.2 Success Criterion 1.4.13 Content on Hover or Focus (Level AA).
We plan to fix this in a future scheduled website release.
13. Keyboard focus indicators have insufficient visibility
When navigating the site using a keyboard, the visible focus indicator is difficult to distinguish on several element types: a black outline against dark purple radio button controls is not sufficiently distinct; a blue border around arrow-style links is barely visible against similar background colours; and the outline on linked images is unclear when displayed over photographs. At higher zoom levels, the focus indicator on the cookie preferences panel also overlaps surrounding content.
This fails WCAG 2.2 Success Criterion 2.4.7 Focus Visible (Level AA) and WCAG 2.2 Success Criterion 2.4.11 Focus Appearance (Level AA).
We plan to fix this in a future scheduled website release.
14. Keyboard focus resets after pagination interaction
On the Course Search / Apply Now page, activating a paginated search result via keyboard causes focus to reset to the top of the page. The user must re-navigate through all search criteria fields before reaching the results area again, making repeated use of the search pagination impractical for keyboard-only users.
This fails WCAG 2.2 Success Criterion 2.4.3 Focus Order (Level A).
We plan to fix this in a future scheduled website release.
15. Images without meaningful alternative text
A number of images across the site do not have an alt attribute where one is needed, or have alt text that is present but not meaningful — for example, images labelled with generic values such as "Grad1". These descriptions do not convey the content or purpose of the image to screen reader users.
This fails WCAG 2.2 Success Criterion 1.1.1 Non-text Content (Level A).
We plan to fix this in a future scheduled website release.
16. Search field relies on placeholder text only
The search field on the home page and course search field on the Course Search / Apply Now page uses placeholder text as its only visible label. Placeholder text disappears when the user begins typing, leaving no persistent visible indication of the field's purpose.
This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (Level A) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (Level A).
We plan to fix this in a future scheduled website release.
