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 400% 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 currently compliant with the W3C WCAG 2.1 AA accessibility standard. Any future issues discovered 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
Our accessibility road map below shows the issues which are currently in place on this website and how we aim to fix them.
- There are currently no accessibility issues on this website
The below items we previously identified as not being accessible have now been fixed.
Issue
Information can only be found by using the navigation there isn’t an alternative
Action
A sitemap has been added to the footer of the website so users can also navigate the website in this way as well as using the usual navigation
Fixed date
August 2020
Issue
The cog that appears in the bottom left of the website once a user sets their cookie preferences did not have a name assigned
Action
A name has been added to identify the purpose of the cog for those using a screen reader
Fixed date
December 2020
Issue
The image at the top of the homepage was missing an alt tag to explain the content and purpose of the image
Action
A name has been added to identify the image
Fixed date
February 2021
Issue
Some images on the homepage did not have alt text added correctly. The website has been reviewed and alt text has been added as required.
Fixed Date
November 2021
Issue
Elements should not have a tab index greater than zero. This issue was relating to the cookie acceptance button. This has now been resolved.
Fixed Date
August 2022
This statement was prepared on 16/06/2020. It was last updated on 11/08/2022.
