Accessibility statement for suffolkroadsafe.com
This website is run by Suffolk County Council.
We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% 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)
We maintain content guidelines to help website editors improve accessibility on suffolk.gov.uk.
Make your device easier to use
AbilityNet has advice on making your device easier to use if you have a disability or impairment.
This includes how to:
- make text larger
- magnify the screen
- change fonts and colours
- make your mouse pointer easier to see
- using your keyboard instead of a mouse
- making your device talk to you
You can translate this website to your preferred language by changing the settings in your browser (such as Internet Explorer, Chrome or Safari).
How accessible this website is
We know some parts of this website aren’t fully accessible, for example some:
- images contain text which you may not be able to read
- links don't make sense on their own
- PDF documents aren’t fully accessible to screen readers
- videos don’t have captions or audio description
- interactive tools are difficult to navigate using just a keyboard
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 email@example.com
- call 0345 606 6067
We’ll consider your request and get back to you as soon as possible.
You can call the number above if you need to talk to us using an interpreter. Find out more about our interpreting and translating services.
If you can’t view the map on our contact us page, call or email us for directions.
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 Content Team by emailing firstname.lastname@example.org.
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).
Contacting us by phone or visiting us in person
We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.
Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Find out more about our interpreting and translation services, including how to contact us to make a request.
Technical information about this website’s accessibility
Suffolk County 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 below.
Non accessible content
The content listed below is non-accessible for the following reasons.
Non compliance with the accessibility regulations
Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This doesn't meet WCAG success criterion 1.4.5 (Images of Text). We plan to remove or replace images containing text by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
On some pages tables do not have a description set using the caption element. This doesn't meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. We plan for all tables to have descriptions by September 2020. When we publish new tables we’ll make sure they meet accessibility standards.
PDFs and other documents
Some of our PDFs and other documents are not formatted so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (Name, role value). By September 2020, we plan to either fix these documents or replace them with accessible HTML pages. Any new PDFs or Word documents we publish should meet accessibility standards.
On some pages the language has not been set in a way that can be understood by a screen reader. This doesn’t meet WCAG 2.1 success criterion 3.1.1 (Language of Page). We plan to set the defined language for all pages on the website by September 2020.
On some pages the label for the form control is not explicitly connected to anything, since it refers to an element ID that does not exist on the page. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Information and Relationships. We plan to resolve this issue by September 2020.
On some pages the tabbing order is not logical when navigating using a keyboard. This doesn’t meet WCAG 2.1 success criterion 2.4.3 Focus Order. We plan to resolve this issue by September 2020.
The focus indicator when navigating using a keyboard is visible but not sufficiently clear. This doesn’t meet WCAG 2.1 success criterion 2.4.7 Focus Visible. We plan to resolve this issue by September 2020.
On some pages the iFrame has no 'title' attribute or the 'title' attribute is empty. This doesn’t meet WCAG 2.1 success criterion 4.1.2 Name, Role, Value. We plan to fix the these issues by September 2020.
On some pages the italics-tag 'i' is used to highlight text. This doesn’t meet WCAG 2.1 success criterion 4.1.2 Information and Relationships. We plan to fix the these issues by September 2020.
We don't categorise any of the accessibility issues on suffolk.gov.uk as a disproportionate burden within the meaning of the accessibility regulations.
Content that’s not within the scope of the accessibility regulations
You can find the complete list of content exempt from meeting the accessibility regulations on legislation.gov.uk.
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.
The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we don’t plan to fix old PDF newsletters that might still be published and accessed through our website.
We plan for all PDFs and other documents published since 23 September 2018 (and essential service documents published before) to meet accessibility standards by 23 September 2020.
Live video streams may not include captions. This doesn’t meet WCAG 2.1 success criterion 1.2.4 Captions (Live). We may not add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Some prerecorded videos published before 23 September 2020 do not include captions. This doesn’t meet WCAG 2.1 success criteria 1.2.2 Captions (Prerecorded). We may not add captions to these videos because prerecorded video published before 23 September 2020 is exempt from meeting the accessibility regulations.
Some prerecorded videos published before 23 September 2020 may require, but don't include, audio description. This doesn’t meet WCAG 2.1 success criteria 1.2.5 Audio Description (Prerecorded). We may not add audio description to these videos because prerecorded video published before 23 September 2020 is exempt from meeting the accessibility regulations.
Any prerecorded video content we publish after 23 September 2020 will meet accessibility standards.
Online maps and mapping services are exempt from meeting the accessibility regulations. From 23 September 2020 we'll ensure that where maps are intended for navigational use essential information is provided in an accessible digital manner.
This statement was prepared on 25 November 2019.