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?
All of this website is compliant with the W3C WCAG 2.1 AA accessibility standard. Any accessibility issue found in the future through regular testing will be added to section 8 of this statement.
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
- There are currently no accessibility issues on this website
The below items we previously identified as not being accessible have now been fixed.
| Issue | Action | Fixed date |
| Certain links did not have a suitable name assigned | All links have been re-built with a name assigned. This means that those users using a screen reader have full access to the website | August 2020 |
| Certain images were missing the alt attribute | All images now have alt text correctly in place | July 2020 |
| The button that is used to amend cookie preferences did not have a name correctly assigned | A name has been added to this element to identify it | December 2020 |
| The colour contrast used for the time within the social media blocks on the homepage is not sufficient | The colour of this element has been changed so it is fully accessible | February 2021 |
| The menu was not built using best practice, meaning that some users using a screen reader may find it difficult to use | The menu has been rebuilt so it is fully accessible to all | June 2021 |
| Elements should not have a tabindex greater than zero. | This issues was relating to the cookie acceptance button. This has been resolved. | August 2022 |
| ID attribute value’s must be unique. | This has been resolved | August 2022 |
This statement was prepared on 16/06/2020. It was last updated on 11/08/2022.
