Non-compliance with the accessibility regulations

Some elements on our pages cannot be accessed via keyboard, as well as the focus is not always visible. This makes it difficult to identify which element is being selected. This also includes selecting the main menu. Known keyboard traps: View Course menu, selecting University’s switchboard number, Tweeter feed.
(WCAG 2.1.1, WCAG 2.1.2, WCAG 2.4.7)

Some of our pages have difficulties to correctly display some elements of the page when at 200%. This also affects our navigation that becomes inaccessible for keyboard users.
(WCAG 1.4.4)

Some of our pages don’t reflow correctly and images might be cropped or cut off. Some mobile users may experience issues with menu navigation.
(WCAG 1.4.10)

Some of our images, including text images, are missing meaningful alternative text or are not correctly marked as decorative images.
(WCAG 1.1.1, WCAG 1.4.5)

Our carousels are missing stop or pause buttons. This may cause difficulties to use the page by some users.
(WCAG 2.2.2)

Some of our pages have poor colour contrast. This may make it difficult to see the content properly.
(WCAG 1.4.3)

Some users with Assistive technologies may struggle to navigate on our pages, as we are aware of missing ARIA parent and child roles to perform accessibility functions and provide structural context to our users.
(WCAG 1.3.1)

Our iframe for the form is not fully accessible and is missing descriptive, meaningful and unique titles. This may cause navigation issues to our screen reader users.
(WCAG 2.4.1, WCAG 4.1.2)

Some of our link names are not accessible by screen readers and are not descriptive enough to tell our users where that link will take them.
(WCAG 2.4.4, WCAG 4.1.2)

On some pages, the focus is not clearly visible and in the correct order when using the keyboard.
(WCAG 2.4.3)

Our placeholder text for Search disappears when being typed into.
(WCAG 3.3.2)

Some of our carousels have links presented. This may not be accessible to screen reader users when they are navigating via lists.
(WCAG 4.1.1)

Some of our buttons are missing a descriptive accessible name, so screen reader users may not understand the use of the item.
(WCAG 4.1.2)

ARIA input fields and toggle fields are missing accessible names that detail the purpose.
(WCAG 4.1.2)

On some of our pages are incorrectly used ARIA attributes, which may cause errors in assistive technology and make difficult navigation to our users.
(WCAG 4.1.2)