Accessibility statement for University College of Estate Management (UCEM) website

This website is run by University College of Estate Management. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • zoom in up to 200% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • use accessiBe accessibility adjustment plugin to customise the site

We’ve incorporated an accessibility plugin, AccessiBe. It utilises an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs. Additionally, it utilises an AI-based application that runs in the background and optimises its accessibility level constantly. This application remediates the website’s HTML, adapts its functionality and behaviour for screen-readers used by blind users, and for keyboard functions used by individuals with motor impairments.

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible is this website?

We know some parts of this website aren’t fully accessible:

  • live video streams don’t have captions
  • we have not tested navigation of the website using speech recognition software
  • we aim to provide accessible PDFs, however, if you have any issues with accessing or using our PDFs, please contact us for a more accessible format

What to do if you can’t access parts of this website

If you need information on this website in a different format or you have a general question about accessibility contact:

We’ll consider your request and get back to you with an initial response in two to five working days.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting the requirements of the accessibility regulations, contact:

Enforcement procedure

If you need to escalate your issue further, contact:

  • Email: complaints@ucem.ac.uk
  • Complaints Officer, University College of Estate Management, Horizons, 60 Queens Road, Reading, RG1 4BS.

You can expect an acknowledgement within two working days and a full reply within 20 working days. If your complaint raises complex issues that cannot be answered within 20 working days, we will keep you informed of progress until we can fully respond.

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

University College of Estate Management is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non accessible content

The content listed below is non-accessible for the following reasons.

Non compliance with the accessibility regulations

Issues with PDFs and other documents

Some PDFs and Word documents may not meet accessibility standards – for example, they may not be marked up or are scanned images so they’re not accessible to a screen reader. We are making all new documents accessible and improving processes used to create content of this type. Please let us know if you have encountered an accessibility issue.

Issues with interactive brochures

We are aware that the content in the interactive brochures is not accessible. We have provided accessible alternatives. We are investigating alternative software to provide accessible interactive content.

Issues with images, video and audio

Live video streams don’t have captions. WCAG 1.2.4 Captions (live).

Captions are not always provided for all prerecorded audio content in synchronized media. This doesn’t meet WCAG 1.2.2 Captions (prerecorded). However, in most cases we are providing a transcript for the same.

Audio descriptions are not provided for all prerecorded video content in synchronized media. This doesn’t meet 1.2.5 Audio Description (prerecorded).

Captions on live video is exempt from meeting the accessibility regulations.

Content that’s not within the scope of the accessibility regulations

None.

HOW WE TESTED THIS WEBSITE

This website (www.ucem.ac.uk) was last tested in April 2021. This test was carried out by Onebite Ltd using the Accessibility Insights for Web extension for Chrome across two different pages of the site which have a variety of layouts to all content block types.

The testing was carried out on the development site prior to the website being launched. The live site is an exact copy of the development site.

As a further check, Onebite Ltd carried out accessibility testing using the AccessiBe plugin.

Failed tests

The following guidelines have been marked as failed as they do not meet the requirements of being WCAG 2.1 AA compliant.

The following items are not WCAG 2.1AA compliant due to code that is being added by the AccessiBe plugin. As the AccessiBe plugin is incorporated into the site specifically to significantly improve its accessibility, it was decided that the vast benefits it provide outweigh these few examples where its code has a negative impact.

We are in talks with the AccessiBe plugin providers with the aim of removing these last issues and will update this accessibility statement once that work is complete.

  1. Design pattern: A custom widget must have the appropriate ARIA widget role for its design pattern-WCAG 4.1.2. These buttons were coded as buttons where they function as a menu button.
  2. Parsing: Elements must have complete start and end tags, must not contain duplicate attributes, and must be nested according to their specifications-WCAG 4.1.1.
  3. CSS positioning: Meaningful content positioned on the page using CSS must retain its meaning when CSS is disabled-WCAG 1.3.2.
  4. In the social feed accessible name “Twitter New Window” was used for more than one URL links. This does not meet WCAG 2.4.4 Link Purpose (In Context)The following items are not WCAG 2.1AA compliant due to elements within the Flow Flow Lite plugin. As this plugin is incorporated to showcase up to date information about UCEM and it vastly improves the information available on the homepage, it was decided that it was beneficial to leave it on the site.We are in talks with the Flow Flow Lite plugin providers with the aim of removing these last issues and will update this accessibility statement once that work is complete.
  5. The cards in the social feed have a reply icon link, but do not have any fallback text to describe the link on screen readers. This does not meet WCAG 1.1.1 Non-text Content.
  6. The social feed reply and favourites are coded as H6. This does not meet WCAG 2.4.6 Headings and Labels.
  7. Graphics also need sufficient contrast that is 3:1. The background of the items in the social feed does not contrast sufficiently with the background of the website. This does not mean WCAG 1.4.11 Non-text Contrast. As these are two backgrounds, it was decided that this offers no detrimental effect to a user.

The following items are not WCAG 2.1AA compliant due to elements within the Content Views plugin. As this plugin is incorporated to showcase up to date information about UCEM and it vastly improves the information available on the website, it was decided that it was beneficial to leave it on the site. We are in talks with the Content Views plugin providers with the aim of removing these last issues and will update this accessibility statement once that work is complete.

8. Element is in tab order and does not have accessible text. This does not meet WCAG 2.4.4 WCAG 4.1.2.

WHAT WE’RE DOING TO IMPROVE ACCESSIBILITY

Our accessibility roadmap shows how and when we plan to improve accessibility on this website.

Item Timeline
Work with AccessiBe plugin providers to ensure compliance on failed elements 1 – 4. Ongoing work with supplier
Work with Flow Flow Lite plugin provider to ensure compliance on failed elements  5 – 7. Ongoing work with supplier
Work with Content Views plugin provider to ensure compliance on failed element 8. Ongoing work with supplier

This statement was prepared on 16 September 2019. It was last updated on 9 September 2021. This statement will be reviewed no later than twelve months from the last update.