XClose

Accessibility

Menu

Inside UCL My Details accessibility statement

This accessibility statement applies to Inside UCL - My Details.

Inside UCL - My Details, is a UCL owned application. 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 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 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 Inside UCL Team, if there is a process in place to acknowledge your contact, you will receive an email stating who is dealing with your query. This response should also outline an potential timescales by which you can expect a reply.

We aim to respond to all contacts within 3-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 the WCAG (Web Content Accessibility Guidelines) 2.2 AA standard.

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

Sitewide issues

Reflow

From 250% the screen changes and shows the user white space at the top of the screen. The only way you can then use the side bar link is by using the breadcrumb link at the top of the screen which will confuse people. This fails WCAG 1.4.10 Reflow (AA).

Focus Visible

When tabbing from item to item, the Focus box only shows above or below on certain elements (Payslips and Disability) as something is obscuring the focus somehow. This fails WCAG 2.4.7 Focus Visible (AA).

Headings

On each page visited, there are either no Headings present or 2 Headings at level 1. Each page should only contain one H1. This fails WCAG 2.4.6 Headings and Labels (AA).

Dialogue Boxes

A user should have a defined start point in a dialogue and be able to tab through within a dialogue box rather than moving to the page behind. This fails WCAG 1.3.1 Info and Relationships (A).

My Details homepage

A user has the ability to change their profile picture. To do this they must activate the link that is not labelled or even in the tab order, so this is not possible for keyboard only users to achieve. This fails WCAG 1.3.1 Info and Relationships (A), WCAG 2.4.4 Link Purpose (In Context) (A), and WCAG 2.1.1 Keyboard (A).

Basic Details page

When a user moves on to particular edit/combo boxes using a screen reader, nothing is read. The individual Screen Reader forms mode is not being applied, so a screen reader user would not know any text is there to change or be able to move through any of the options available. This fails WCAG 1.3.5 Identify Input Purpose (AA).

Contact Details page

When editing the contact details section, the County field in Main address is missed. This fails WCAG 1.3.2 Meaningful sequence (A), WCAG 1.3.5 Identify Input Purpose (AA), and WCAG 2.1.1 Keyboard (A).

When the alternative address link is activated, when the user presses tab your focus misses all the section on the form and moves the user to the delete alternative address link at the bottom of the form. This can be recreated if using the keyboard only. This fails WCAG 1.3.5 Identify Input Purpose (AA).

If the user misses any of the mandatory fields out in this section an error message occurs and reads out. The problem on some fields are that te message is the same so users cannot distinguish which field has the error. This fails WCAG 3.3.1 Error Identification (A).

Emergency Contact Details page

When using either Add Emergency Contact or Edit Emergency Contact buttons – any of the susequent combo boxes are missed in the tab order. This fails WCAG 2.4.3 Focus Order (A) and WCAG 2.1.1 Keyboard (A).

Equality, Diversity and Inclusion (EDI) page

When the Edit details button is pressed the subsequent form field boxes appear but are not tab-able meaning a keyboard user could not fill them in. This fails WCAG 2.1.1 Keyboard (A).

Disability page

Under the Current records section there is an End Record option that should be a button but is classed as a link. For consistency this should be changed to a button. This fails WCAG 3.2.4 Consistent Identification (AA).

Payslips page

At the top of the page there is a title just before the list of payslips that is not a heading. If this is changed to a Heading navigation be better for user groups.  This fails WCAG 2.4.6 Heading and Labels (AA).

There is also a link at the top of the page titled Important Information. This opens a modal/dialogue box with some textual information. Inside the modal the text tells users to report a problem using the Burger menu option, but this burger menu is a graphic only and does not get read with readers, so some user groups will miss this detail. This fails WCAG 1.3.3 Sensory Characteristics (A) and WCAG 1.3.1 Info and Relationships (A)

There are back and forward links at the top next to the title that are labelled ‘Link’, so users do not know what they are.  This fails WCAG 2.4.4 Link Purpose (In Context) (A).

There are several links on this page that are labelled View. These open each payslip. But as the link just states view, certain user groups would not know month they are opening so would find this confusing. This fails WCAG 2.4.4 Link Purpose (In Context) (A). 

The download payslip link just states ‘link’. This fails 2.4.4 Link Purpose (In Context) (A).

The checkboxes to select a particular month's payslip is labelled for screen reader users, but the label is for the incorrect month (Screen readers read the month previous). This fails WCAG 2.4.4 Link Purpose (In Context) (A) and 2.4.6 Headings and Labels (AA). 

There is no option to skip over the list of payslips links. This would help you get to download last 3 months button and download selected button quicker. This fails WCAG 2.4.1 Bypass Blocks (A).

Contract Details page

There is an information section where the graphic is not labelled, so some user groups will know know the context. This fails WCAG 1.3.1 Info and Relationships (A).

Bank Details page

Please see Reflow on site wide issues.

My Appraisal page

There are 2 links on this particular page that would not make sense if they were to be read in separation from the other text. This fails WCAG 2.4.4 Link Purpose (In Context) (A).

The Access your appraisal looks like a button, but is classes as a link. Consistency is needed for all user groups so this should be changed to a button. This fails WCAG 3.2.4 Consistent Identification (AA).

Skills page

When adding a skill you need to fill in an edit box. This box has no label so some user groups would not know what they are filling in. This fails WCAG 3.2.4 Consistent Identification (AA).

If a skill has been added to this page, a keyboard user cannot get to the delete option. This fails WCAG 2.1.1 Keyboard (A).

Interests page

On the Interests page, the same problems occur as on the Skills Page.

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 UCL developer. 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.

Preparation of this accessibility statement

This statement was prepared on 1 August 2024. It was last reviewed on 1 August 2024. This application was last tested on 1 August 2024. The test was carried out by UCL Digital Accessibility Team.

What we’re doing to improve accessibility

University College London (UCL) are working 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.