+44 01509 974112 info@mpilearning.com
Select Page

Accessibility Statement

Accessibility Statment for MPI Learning

This accessibility statement applies to www.mpilearning.com.

This website is run by MPI Learning (Maximum Performance International LTD). We want as many people as possible to be able to use this website. For example, that means you should be able to:

change colours, contrast levels and fonts using browser or device settings
zoom in up to 400% without the text spilling off the screen
navigate most of the website using a keyboard or speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
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 this website is

We know some parts of this website are not fully accessible:

  • you cannot modify the line height or spacing of text
  • most older PDF documents are not fully accessible to screen reader software
  • live video streams do not have captions
  • you cannot skip to the main content when using a screen reader
  • there’s a limit to how far you can magnify the map on our ‘contact us’ page

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

  • email info@mpilearning.com
  • call +44 01509 974112

We’ll consider your request and get back to you in 30 days.

If you cannot view the map on our ‘contact us’ page, call or email us for directions.

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

MPI Learning is committed to making its 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.1 AA standard or Web Content Accessibility Guidelines version 2.2 AA standard], due to the non-compliances listed below.

  • Elements that behave as buttons but are built using other tags such as span, div, a or others, should include a “role” attribute that equals to “button”.
  • Links that open in a new tab or a new window should either have an “aria-label” attribute or a screen-reader only element explaining to screen-readers that this opens in a new tab.
  • Elements that visually appear as titles but are coded with a non-heading HTML Tag should include a “role” attribute that equals to “heading” or have their tags fixed.
  • Interactive elements such as links, buttons and form fields should all be navigable using the keyboard by either using a focusable element (a, button, input, etc.) or including the “tabindex” attribute that equals to “0”.
  • Interactive elements that can be navigated using the keyboard should be surrounded by a visual outline whenever they are focused.
  • Every page should include hidden links that by clicking on them (either using keyboard navigation or a screen-reader), the user will “skip” certain blocks directly to main landmarks such as main content, menu or footer.
  • Menu items that have a dropdown menu include an “aria-haspopup” attribute that equals to “true”.
  • Menu items that have a dropdown menu include an “aria-expanded” attribute that equals to “false” that changes to “true” and back when opening or closing the dropdown.
  • Background images that are not just for decoration purposes and should have the same treatment as standard images and include a “role” attribute that equals to “img” and an alternative text description in an “aria-label” attribute.
  • Font icons, SVG or images that are being used as spacers, decorations or their purpose is already described by the content should include a “role” attribute that equals to “presentation” or “none”.
  • Required form fields should include an “aria-required” attribute that equals to “true” so blind users using screen-readers know their validation.
  • All forms should have a submission button that is built as an input type “submit” or a “button” element, or include a “role” tag that equals to “button”. Buttons can be hidden if the form can be submitted using the Enter key.
  • The meta viewport tag should allow vision impaired users to pinch-zoom at least double the standard scaling using the user-scalable=”yes” and maximum-scale={2 or higher} content strings.
  • Landmarks such as main content and footer should be built using their corresponding HTML5 element or include a description using an “aria-label” attribute and a “role” tag that equals to “contentinfo” or “main”. Landmarks such as search and navigation are tested in other sections.
  • Elements that have texts should meet a minimum contrast ratio of 4.5:1 between their foreground (usually text color) and background color.

Non-accessible content

The content listed in this pdf is non-accessible for the reasons listed in the previous section. 

Accessibility report pdf

Non-compliance with the accessibility regulations

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images by January 2025. When we publish new content we’ll make sure our use of images meets accessibility standards.

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

PDFs and other documents

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.

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

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

What we are doing to improve accessibility

We are working towards full accessibility but in the mean time we have enabled accecibility tools that can be turned on or off using the tab on the right of the website.

Preparation of this accessibility statement

This statement was prepared on 06/10/23. It was last reviewed on 05/10/23.

This website was last tested on 06/10/23.

The test was carried out by AccessScan. The most viewed pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.

You can read the full accessibility test report Accessibility report pdf

Skip to content