Accessibility statement for londonmet.ac.uk

This accessibility statement applies to content published on the londonmet.ac.uk domain. It does not apply to content on student.londonmet.ac.uk, staff.londonmet.ac.uk or any other domains associated with London Metropolitan University. 

This website is run by London Metropolitan University and we want as many people as possible to be able to use it. So, with that in mind, you should be able to:

  • zoom in up to 300% without any problems
  • navigate most of the website using a keyboard
  • use most of the website using screen reader software

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

As a university committed to social inclusion, we endeavour to make our website as accessible as possible but, at present, we know there are some aspects of the website that aren’t fully accessible. We’re working to improve this, but these currently include:

  • the same link text being used for multiple link destinations
  • not being able to skip repeated content using screen reader software
  • the colour contrast on some pages being insufficient
  • a number of our older PDF and Word documents not being fully accessible
  • live streamed videos and some older videos lacking captions
  • the “Visit us” and “Meet the team” menu links on our course pages not always functioning as they should
  • the format of some tables not always being optimised for screen reader software
  • some headings being difficult for screen reader software to navigate
  • some images not having good alternative text
  • some buttons and form elements not being correctly identifiable through screen reader software

Feedback and contact information

If you need information on this website in an alternative format such as large print, audio recording or braille, please contact us by emailing marketing@londonmet.ac.uk.

We’ll look into your request and aim to respond within five working days.

Reporting accessibility problems with this website

We’re always striving to improve the accessibility of this website. If you find any problems that aren’t already listed in our accessibility statement, you can contact webteam@londonmet.ac.uk.

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. If you’re unhappy with how we respond to any complaint you make to us regarding accessibility, you can contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

London Metropolitan University 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.

Non-accessible content

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

  • Some pages feature link text that is used for links going to different destinations. This fails WCAG 2.1A 2.4.4 success criterion (Link Purpose (In Context)). We plan to fix this by December 2020.
  • Some pages contain anchors where the destination doesn’t exist. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by the end of November 2020.
  • Some images do not have adequate alternative text. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). When we publish new content, we’ll make sure our use of image alternative text meets accessibility standards.
  • There is not always a means of bypassing blocks of content that are repeated on multiple web pages, for example the main menu. This fails WCAG 2.1A 1.4.6 success criterion (Contrast (Enhanced)). We plan to fix this by the end of December 2023.
  • Not all content is included in the landmarks used for navigating a page using assisted technologies. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by the end of November 2023.
  • Some pages have iFrames without a 'title' attribute or the 'title' attribute is empty. This fails WCAG 2.1A 4.1.2 success criterion (Name, Role, Value). We plan to fix this by the end of October 2020.
  • Some drop-down menus don’t have a description that is explicitly associated with the menu to aid the use of assisted technologies. This fails WCAG 2.1A 3.3.2 success criterion (Labels or Instructions). We plan to fix this by the end of November 2020.
  • Some pages contain two or more landmarks that have not been named or have identical names. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by November 2023.
  • Some components, for example, the search bar, are not visually identified for keyboard navigation. This fails WCAG 2.1AA 2.4.7 success criterion (Focus Visible). We plan to fix this by the end of November 2020.
  • Some pages feature content, for example, tables, that use HTML formatting rather than CSS. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by November 2023.
  • Some pages don’t have a top-level heading. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by the end of September 2020.
  • On some pages, 'i' tags are used to insert icons. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by the end of October 2020.
  • Some pages use an element ID that is being used for another element on the page. This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We plan to fix this by the end of October 2020.
  • Some pages contain redundant WAI-ARIA attributes that have the exact same features as the HTML element they have been applied to. This fails WCAG 2.1A 4.1.2 success criterion (Name, Role, Value). We plan to fix this by November 2023.
  • Some pages contain an error container made with the WAI-ARIA role="alert" or aria-live="assertive" attributes, but it does not contain a WAI-ARIA attribute that will make sure all assistive technologies can read the error message after more than one invalid submission. This fails WCAG 2.1A 3.3.1 success criterion (Error Identification). We plan to fix this by November 2023.
  • Some pages contain WAI-ARIA elements containing a role, state or property that is invalid or not allowed on this type of element. This fails WCAG 2.1A 4.1.2 success criterion (Name, Role, Value). We plan to fix this by December 2022.
  • Some pages contain a form or drop-down menu with no submit button. This fails WCAG 2.1A 3.2.2 success criterion (On Input). We plan to fix this by the end of November 2023.

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

PDFs and other documents

Some of our PDF and Word documents contain key information, which is not always accessible.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix historic documents such as annual reports. However, where we deem a PDF or other document to be essential to providing our services, we will endeavour to make these accessible.

Any new PDFs or Word documents we publish will meet accessibility standards.

Live video

We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations. There may also be some videos published before 23 September 2020 that do not have adequate captions. These are also exempt from meeting the accessibility regulations. However, where a video contains key information, we will endeavour to add captions to these retrospectively.

Preparation of this accessibility statement

This statement was prepared on 17 September 2020. It was last reviewed on 15 October 2020.

The londonmet.ac.uk website was last tested on 15 October 2020. It was and continues to be tested for compliance with the Web Content Accessibility Guidelines V2.1 level A, level AA and level AAA, and these tests have been carried out internally using a number of third-party tools.