This statement was prepared on 15/06/2020. It was last updated on 10/08/2022.
- 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.
- How accessible is this website?
All of this website is compliant with the W3C WCAG 2.1 AA accessibility standard. Any future issues that are found relating to accessibility through regular routine testing will be added to this page.
- 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. - 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. - 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
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. - 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 added to this page and implemented within two months. - 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 when we aim to fix them.
There are currently no accessibility issues on this website. Any future issues discovered through routing testing will be added to this section.
9. The below items were all previously identified as not being accessible, these issues have now been fixed.
| Issue | Date Fixed |
|---|---|
| Certain videos did not have a transcript or subtitles available, these have now been added | August 2020 |
| The rotating image on the homepage previously could not be paused. This has been changed so it no longer automatically moves | July 2020 |
| Certain images and links did not have a name correctly assigned to assist those using a screen reader to inform what the image or link was for. These have now all been amended. | July 2020 |
| When previously accessing the website using a keyboard only it was not always clear which element had been selected. This has been corrected and a visible border is now placed round every element when accessing the website using a keyboard only. | August 2020 |
| The contact form did not previously give enough guidance to help those completing it. Help text is now in place, giving guidance on what should be entered within the form. | August 2020 |
| The cog that appears in the bottom left of the website once a user sets their cookie preferences did not have a name assigned | December 2020 |
| Previously some PDF documents available on this website were not accessible | January 2021 |
| The colour contrast between a couple of elements on the homepage was not sufficient. Inaccessible colours have now been replaced. | February 2021 |
| The arrow available from the slider element on the homepage did not have a name assigned correctly. This is now in place. | February 2021 |
| The size of the text used within the slider on the homepage was not the correct size. This has now been replaced as required. | February 2021 |
| Zooming and scaling on the website was previously disabled. This is now available | November 2021 |
| A video did not have a text alternative. This has now been added | March 2022 |
| Some users that use a keyboard only to view the homepage may have got stuck within the Facebook feed. This has been removed. | March 2022 |
| Some links on the homepage were missing discernible text. This has now been added | March 2022 |
| Some of the Accessible Rich Internet Applications (Aria) are not built for best practice, meaning some users with disabilities may struggle to navigate the website | March 2022 |
| An image on the homepage uses an image containing text. This has now been removed. | March 2022 |
| Elements should not have a tab index greater than zero. This has been resolved. | August 2022 |
| ID attribute value must be unique. This has been resolved. | August 2022 |
| Insufficient colour contrast for some headings used across the website. This has been resolved. | August 2022 |
| Links must have discernible text. This has been resolved. | August 2022 |
| ID attribute value must be unique. This has been resolved. | August 2022 |
| Headings should not be empty. This has been resolved. | August 2022 |
