Accessibility

1. Using this website
This website is run by Middlesbrough Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • Zoom in up to 200% without the text spilling off the screen
  • Navigate most of the website using just a keyboard
  • Navigate most of the website using speech recognition software
  • Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
  • View the website using any device e.g. mobile phone, tablet, desktop computer

AbilityNet has advice on making your device easier to use if you have a disability.

Please note this website may not function correctly if you are using an older browser i.e. Internet Explorer. It is recommended for those users using Internet Explorer that they instead use Google Chrome or Microsoft Edge.

2. How accessible is this website?

Most of this website is currently compliant with the W3C WCAG 2.1 AA accessibility standard. However, there are some parts of this website that are not fully accessible:

  • Some links are missing discernible text

3. What to do if you can’t access parts of this website
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille: email digital@middlesbrough.gov.uk. We’ll consider your request and get back to you within 10 working days.

4. Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact the Middlesbrough Council Digital Team by emailing the issue to digital@middlesbrough.gov.uk.

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

6. Technical information about this website’s accessibility
Middlesbrough Council 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, due to the non-compliances listed under section two of this page.

7. How we test this website
This website is tested every 7 days. The tests are carried out by the Middlesbrough Council Digital team using online accessibility reporting tools and manual testing. Required changes that are discovered as a result of these tests will be implemented within two months.

8. Non-compliance with the accessibility regulations and what we are doing to improve accessibility

Our accessibility road map below shows the issues which are currently in place on this website and how we aim to fix them.

  • Some links are missing discernible text. The website will be reviewed and text will be added where required. We aim to fix this by September 2022.

 

The below items previously identified as not being accessible have now been fixed:

 

The following elements have been fixed in relation to accessibility Fixed date
The moving logo in the header of the website was not accessible as it could not be stopped from moving August 2020
The skip to content button was not fully visible August 2020
The logos in the footer were missing Alt tags to explain what they were August 2020
The text used within the footer did not have sufficient colour contrast August 2020
The button to select cookie preferences previously was missing a name December 2020
Some image elements did not have alt text to explain what they are to those using assistive technology June 2021
Images were missing link text to explain their purpose, this previously made the website difficult to use for those using a screen reader June 2021
Elements should not have a tab index greater than zero. This issue was relating to the cookie acceptance button and has now been resolved August 2022

This statement was prepared on 16/06/2020. It was last updated on 11/08/2022.