XClose

Accessibility

Menu

ethics@ucl accessibility statement

This accessibility statement applies to ethics@ucl application.

ethics@ucl is an Infonetica owned application that UCL has developed and tailored to support the submission and processing of research ethics applications.

  We want as many people as possible to be able to use this application, which means that you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 400% 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

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 the Research Ethics Service 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 Ethics Team, Service, with an accessibility issue we aim to acknowledge your message within 1-2 working days setting out the proposed action and timescale.  For all other queries we aim to respond within 3-5 working days.

Reporting accessibility problems with ethics@ucl

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

Technical information about ethics@ucl 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 version 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

Login page

At increased levels of magnification a burger menu replaces the main navigation area. This includes drop down items that are not keyboard accessible or merge together on the page. This fails WCAG 1.4.10 Reflow (AA) and WCAG 2.1.1 Keyboard (A).

Password errors or other reset errors are not clearly communicated to screen reader users. This fails WCAG 3.3.1 Error Identification (A) and WCAG 3.3.2 Labels or Instructions (A).

No guidance is given for any new password created (what specific formats are needed) until an error occurs. This fails WCAG 3.3.1 Error Identification (A) and WCAG 3.3.2 Labels or Instructions (A).

For any password error or forgotten password encountered, colour contrast is too low, ranging from 3.89:1 to 4.26:1. Text at this size requires a contrast of 4.5:1 ratio or higher. This fails WCAG 1.4.3 Contrast (Minimum) (A).

There is a login button present on the screen that is classed as a button, and next to it the same looking element for New User is classed as a link. Consistency is needed for certain user groups. This fails WCAG 3.2.3 Consistent Navigation (AA).

Main application window

The main menu bar for the application has silver/grey text, meaning the contrast is below minimum standards. This fails WCAG 1.4.3 Contrast (Minimum) (A).

The main page does not reflow effectively. For example, of the 7 tiles on the left of the screen only two are visible and the burger menu is not keyboard accessible. This fails WCAG 1.4.10 Reflow (AA) and WCAG 2.1.1 Keyboard (A).

When the burger menu is available, the elements Contacts and Accessibility are not keyboard accessible. This fails WCAG 2.1.1 Keyboard (A).

In the actions sidebar there are a series of groups around each button making it difficult for some user groups to navigate. This fails WCAG 1.3.1 Info and Relationships (A).

Headings on the page are not structured in the correct way meaning related information is hard to interpret for some user groups. This fails WCAG 2.4.6 Headings and labels (AA).

Some pages are missing any naming structure in the page title. This fails WCAG 2.4.2 Page Titled (A).

In some areas of the application, there is a group list on the left side of the sceen. This list is large and would need to be tabbed over 64 items to move through and off it. There is no skip to link present. This fails WCAG 2.4.1 Bypass Blocks (A).

Create Project

When creating a project the dialogue box reads the incorrect Project name. This fails WCAG 2.5.3 Label in Name (A).

Focus is not tracked when magnifiying 200% or more on a dialogue box. This fails WCAG 1.4.10 Reflow (AA).

Project Overview

After a project has been created a new page opens to show the information. This particular page has issues including colour contrast and list items not being read out. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 1.4.3 Contrast (Minimum) (AA).

When in the project tree view list a user is not able to tab on to the sub menu items. This fails WCAG 2.1.1 Keyboard (A).

Heading structure on this area of the site needs adjusting. This fails WCAG 2.4.6 Headings and Labels (AA).

There is a table placed in the lower section of this page that tells a user the status of the application. Screen reader users cannot get to this data using the keyboard This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 2.1.1 Keyboard (A).

There are a series of tabs a user can navigate to on this screen. Whilst you can navigate to them and activate them amessage that tells screen reader users to press spacebar to activate. This does not work, even when the Screen Reader is turned off the spacebar does not work to move between the tabs. There is also not a record of which tab you are on in the page title so this would be confusing for some users. This fails WCAG 3.2.3 Consistent Navigation (AA) and WCAG 2.4.2 Page Titled (A).

From 250% elements on the page start to go missing or overlap other elements. This fails WCAG 1.4.10 Reflow (AA).

When adding a sub form, it is added to the tree view list that is not accessible to keyboard users. This fails WCAG 2.1.1 Keyboard (A).

Reviewer Journey

Many issues found on the reviewer journey are detailed above already. More information is available on request if needed from the initial audit performed by UCL.

Project tables

The help button in the top right of the table is not in the tab order so is missed. This will affect keyboard only users.  This fails WCAG 1.3.1 Info and Relationships (A).
 
There are a series of visual buttons to the top right of the table that allow a user to download the table in various formats. These buttons are links, so this could be confusing for some user groups. This fails WCAG 3.2.4 Consistent Identification (AA).

There is an edit box above the table with no label, meaning a user is unclear what to input in this section. This fails WCAG 1.3.5 Identify Input Purpose (AA) and WCAG 2.5.3 Label in Name (A).

If magnifying this page, from 110% a scroll bar is introduced to see all of the table fields. This makes the table impossible to use for some user groups This fails WCAG 1.4.10 Reflow (A).

The table on a page does not allow the user to move around the data. Even when using screen reader keystrokes. The way the table has been created is not a good user experience. A screen reader user for example, gets told the row information but not the column. You would normally expect both. This fails WCAG 1.3.1 Info and Relationships (A).

There is a flag option a user can use on the table row, but this is only accessible by mouse click. A screen reader user will not know the flag is on/off as this is only notified by the colour changing. This fails WCAG 1.4.1 Use of Colour (A) and WCAG 2.1.1 Keyboard (A).

By clicking any of the links inside the table, a new screen is loaded. This new page has a number of issues including: 

  • Left hand menu not keyboard accessible. This fails WCAG 2.1.1 Keyboard (A).
  • Edit boxes not being read out. This fails WCAG 1.3.5 Identify Purpose (AA).
  • Colour contrast issues. This fails WCAG 1.4.3 Contrast (Minimum) (AA).
  • Links names that do not make sense. This fails WCAG 2.4.4 Link Purpose (In Context) (A).
  • Graphic and/or charts not being read out. This fails WCAG 1.1.1 Non-text Content (A).

Inside the table, there is a Clock Status and Email graphic that cannot be tabbed to or opened by keyboard. Once either of these is opened the labels for the buttons are not correct or you cannot move through any dialogue. Closing the dialogue by pressing enter on the cancel button did not work either, a mouse click has to be used. This fails WCAG 2.1.1 Keyboard (A) and WCAG 2.4.6 Headings and Labels (AA).

When reviewing a project if the user tries to add a comment a dialogue appears. This dialogue box does not read out all of the options inside, or does not inform a user of its state. This fails WCAG 1.3.1 Info and Relationships (A).

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 may 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 this web application using a combination of manual and automated checks alongside the developer, Infonetica. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the web app 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. This is a living document which we will update as and when necessary and additionally review annually.

Preparation of this accessibility statement

This statement was prepared on 03 October 2024. It was last reviewed on 27 September 2024. This application was last tested on 27 September 2024. The test was carried out by Infonetica and UCL.

What we’re doing to improve accessibility

Infonetica are working with University College London (UCL) to fix any issues raised or provide alternatives for all issues we are made aware of and as identified by our periodic internal testing and auditing processes.