Sorry, you need to enable JavaScript to visit this website.

Compliments and Comments Icon

Accessibility statement

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.

2. How accessible is this website?

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

  • Pages with embedded maps using our ESRI Maps product (these maps cannot be read by a screen reader)

  • Most of our older pdf documents

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:

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 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. Non-compliance with the accessibility regulations

Use of embedded maps
Maps embedded into a webpage are not fully accessible as they cannot be read by a screen reader. To enable users who access this website using a screen reader we will also provide the relevant information that the map holds within the webpage itself. For example a point on a map may contain the name of a location and the services provided there. This information will be simplified and made available to be read aloud by a screen reader. This will be implemented by the end of January 2020.

Ability to skip to content
A fully accessible website should have a link available in the top left of every page that allows the user to ‘Skip to content’. When clicked this should navigate the user to the start of the web page content. The link should be prominent and the first item that is read by a screen reader on every page on this website. This will be implemented by the end of January 2020.

Images containing text
Images used on a website should not contain text that is pertinent to the understanding of that page. Screen readers are unable to read text that is included within an image so should be contained within the page itself. All images on this website which contain text will be replaced with accessible versions by the end of February 2020.

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

PDFs and other documents

Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value). 

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages. 

The accessibility regulations don’t require us to fix PDFs or other documents published before September 2018 if they’re not essential to providing our services. For example, we don’t plan to fix old issues of the Love Middlesbrough magazine. 

Any new PDFs or Word documents we from this point forwards will now meet accessibility standards.

9. How we test this website

This website is tested every 7 days. The tests are carried out by the Middlesbrough Council Digital Team using SiteImprove's accessibility reports and other online accessibility reporting tools. Required changes that are discovered as a result of these tests will be implemented within two months.

10. What we are doing to improve accessibility

Our accessibility road map below shows how we aim to improve accessibility across this website.

Issue

Target fix date

Provide relevant guidance for those using a screen readers where embedded maps have been used. This guidance will explain the contents of the map.

January 2020

Make available a link at the top of each page to enable the user to ‘skip to content’. This will enable those using a screen reader to navigate straight to the content of the page rather than having to listen to the menu etc. on each individual page.  

January 2020

Make our PDFs accessible. All PDFs will be scanned using an accessibility checker. Information will either be transferred into a webpage instead of the PDF or the PDF document will be made fully accessible.

September 2020

Images containing text will be replaced with accessible images. Any text that is vital to the reading of a page will be available for a screen reader to access, any images that have text included will be removed or replaced.

February 2020

This statement was prepared on 16/10/2019. It was last updated on 16/10/2019.