University of Reading cookie policy

We use cookies on reading.ac.uk to improve your experience, monitor site performance and tailor content to you.

Read our cookie policy to find out how to manage your cookie settings.

Non-compliance with the accessibility regulations

What you could experience

Keyboard navigation

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)

Resize Text at 200%

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)

Reflow

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)

Images, Images of Text

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)

Pause, Stop, Hide

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

Colour Contrast

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

Missing Info and Relationships

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)

Forms

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)

Links in context

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)

Focus order

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

Labels or Instructions

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

Link in carousel

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)

Button, images used as links

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)

Combo box, list box, search box, radio, menu

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

ARIA attributes

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)

WCAG 2.2 New Criteria Compliance

We have been improving our websites to comply with the new success criteria introduced in WCAG 2.2. However, we have identified some of the issues you may experience:

Accessible authentication

Some of our sites may still use authentication mechanisms that are not compatible with WCAG 2.2 criteria. For example, contact us form requiring user to solve a math equation to submit (WCAG 3.3.8)

Focus obscured

Some of our pages contain panels that obscure the focus, which can make it difficult for keyboard navigation (WCAG 2.4.12)

Small clickable area

Some of our pages contain interactive elements (eg. images, buttons, links) that may not have sufficient target size (WCAG 2.5.8)

Dragging movements

Some of our pages contain dragging interactions. We are replacing these with single pointer interactions; for example, adding text boxes to complement the sliders. (WCAG 2.5.7)