the format you need - for example, plain text, braille, BSL, large print or audio CD
We'll consider your request and get back to you in 5 working days.
Reporting accessibility problems with this website
We're always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we're not meeting accessibility requirements, email firstname.lastname@example.org or call 0191 427 7000. The Digital Team are responsible for dealing with these reports.
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).
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Images on some pages do not always have suitable image descriptions. Users of assistive technologies may not have access to information conveyed in images. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We use Google Maps to display locations in South Tyneside.
The image of the map provided by Google does not have alternate text. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). As content from Google Maps is not under the Council's control, we are unable to fix this, however, we provide the address of the location in text format.
The button to show the street map is using an ARIA attribute that is not allowed (aria-expanded="false"). This fails WCAG 2.1 success criterion 4.1.2 (name, role, value - non-text content). As content from Google Maps is not under the Council's control, we are unable to fix this.
Some frames don't have titles. This fails WCAG 2.1 success criteria 2.4.1 (bypass blocks) and 4.1.2 (name, role, value).
Some pages cannot be found through more than one type of navigation. This fails WCAG 2.1 success criterion 2.4.5 (multiple ways).
PDFs and non-HTML documents
Many documents are in less accessible formats, for example PDF. Non-HTML documents published on or after 23 September 2018 must have an accessible format. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
We plan to replace PDF and Word documents on our website with accessible HTML pages.
We are prioritising:
documents which have essential information about how to access our services
forms which can't be submitted online
documents which are regularly downloaded
When we plan to fix these issues
We are urgently fixing content which fails to meet the Web Content Accessibility Guidelines version 2.1 AA standard. We will update this page when issues are fixed.
We are making sure any new content or digital services we build meet accessibility standards.
Content that's not within the scope of the accessibility regulations
PDFs and non-HTML documents
Non-HTML documents published before September 2018 do not need to be accessible - unless users need them to use a service.
The accessibility regulations do not require us to provide a text only format for pre-recorded video published before 23 September 2020.