XClose

Accessibility

Menu

EDRM accessibility statement

This accessibility statement applies to the UCL EDRM Webtop and React pages.

The EDRM Webtop and React pages are run by University College London (UCL). We want as many people as possible to be able to use this website, which means that you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate the website using just a keyboard
  • navigate the website using speech recognition software
  • listen to most of the website using a screen reader

The React website is built and run by UCL.

EDRM Webtop website is run by OpenText, and is therefore a third-party platform which means that some aspects of its accessibility are outside of our immediate control.

There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively. AbilityNet has advice on making your device easier to use if you have a disability.

Feedback and contact information

Please contact us if you have an accessibility query including:

  • If you are experiencing issues with accessing information or using the website
  • If you find an accessibility problem not listed on this statement
  • If you have positive feedback on the accessibility considerations made. 

When you contact the EDRM Team, there is a process in place to acknowledge your contact, tell you who is dealing with your query and give you a timescale by which you can expect a reply.

We aim to respond to all contacts within 5 working days.

Reporting accessibility problems with this website

We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.2 AA standards.

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

Read tips on contacting organisation about inaccessible websites.

Enforcement procedure

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).

If you are in Northern Ireland and are not happy with how we respond to your complaint, you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland

Technical information about this website's accessibility 

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

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Webtop portal

The following list refers to the Webtop portal of Documentum. The below statement items take into account the user has enabled the additional accessibility options on the login screen.

Please note that for all of these issues we are working with the supplier, OpenText, to make the relevant fixes.

Across the entire site

The language of the site has not been identified. This means that screen readers are unable to identify the language of the page. This also stops any automatic translation of content. This fails WCAG 1.1.1 Non-text Content (A).

Login page

On the login page a layout spacer image (which should have null/empty alternative text) does not have an alt attribute. Which means that currently it will be picked up by screen readers, causing delays to users. This fails WCAG 1.1.1 Non-text Content (A).

On the login page the version number contrast is very low. Adequate contrast of text is necessary for all users, especially users with low vision. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

The menu has multiple blank rows. These are read by screen readers, which makes navigating the site using a screen reader tedious and confusing. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 4.1.2 Name, Role, Value (A).

Login error message

Any error messages on the page (for example if the user gets their login details incorrect) are not announced to the screen reader. This could lead to confusion for a user trying to log in to the site. This fails WCAG 4.1.3 Status Messages (AA).

When using a screen reader the change password button does not clearly indicate that you will be taken to a new page. This could cause confusion for some users of the page. This fails WCAG 2.4.4 Link Purpose (In Context) (A) and WCAG 4.1.2 Name, Role, Value (A).

The page does not provide a descriptive title and is simply called Login. This can be confusing to users with screen readers who have multiple tabs open. This fails WCAG 2.4.2 Page Titled (A).

Home page

There are no page regions defined. Regions and ARIA landmarks identify significant page areas. Most web pages should have regions defined, particularly for the main content area. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 2.4.1 Bypass Blocks (A).

There is a first level heading missing from the Webtop site. This hinders page navigation for assistive technologies. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 2.4.6 Headings and Labels (AA).

Some text on the home page has insufficient colour contrast. This could cause users with low vision difficulty when using the page. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

Multiple active elements share the same id attribute, which can cause a user’s assistive technology to parse content inaccurately. This fails WCAG 4.1.2 Name, Role, Value (A).

Horizontal scrolling is required when the page reflows. This fails WCAG 1.4.10 Reflow (AA).

We are aware of the issue that turning on the systems built in additional accessibility options disables the users ability to import documents. This is a concern that we will be raising with the supplier, along with all issues mentioned above.

React portal

The following list refers to the React portal of Documentum. For all of the issues below, we have these logged and plan to implement fixes in an upcoming version release.

Home page

The ‘Type’ drop down and search field are unlabelled. This means that screen readers will be unable to detect what these fields are. This fails WCAG 1.1.1 Non-text Content (A), WCAG 1.3.1 Info and Relationships (A), WCAG 2.4.6 Headings and Labels (AA), and WCAG 3.3.2 Labels or Instructions (A).

The search bar is not clearly described as a search bar by a screen reader. This fails WCAG 1.3.1 Info and Relationships (A).

The menu, as well as the toggles on the document import screen, are unable to be interacted with when using a keyboard only. This could limit some users experience with this system. This fails WCAG 2.1.1 Keyboard (A).

A focus indicator is not present on all interactive elements of the page, making page navigation for those with low vision difficult. This fails WCAG 2.4.7 Focus Visible (AA).

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

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

This section covers issues that we do not need to fix right now. The law calls these exemptions.

Third-party content

Our websites contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third-party to improve its accessibility. This may include:

  • links to non-UCL websites
  • content/functionality on our website
  • content hosted on other websites, such as social media sites.

To help accessibility compliance across the sector, University College London supports searchBOX, a centralised, independent directory of third-party accessibility information. 

searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem. 

Users can access third-party accessibility statements using the free searchBOX Finder service. 

University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory. 

Our testing processes

We tested the website using a combination of manual and automated checks alongside reference to the existing conformance reports provided by OpenText. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the website owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated.

Preparation of this accessibility statement

This statement was prepared on 3 November 2022. It was last reviewed on 3 November 2022. The website was last tested on 1 November 2022. The test was carried out by the UCL EDRM Team.

What we’re doing to improve accessibility

The UCL EDRM Platform team are working with OpenText to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes.