Accessibility statement for suffolk.gov.uk
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)
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:
- many PDF documents aren’t fully accessible to screen reader software
- live video streams don’t have captions
- our decision tree tools are difficult to navigate using just a keyboard
- some images don't have descriptions of what the image shows
- colour contrast makes it hard to read text in some parts of the website
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 firstname.lastname@example.org
- 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 email@example.com.
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 don’t have a text alternative, so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (Non-text content).
We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
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 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 the same link text is used for links going to different destinations, so people might not know the difference. This doesn’t meet WCAG 2.1 success criterion 2.4.4 (Link Purpose, In Context).
We plan to make link destinations clear all pages by September 2020. When we publish new pages we’ll make sure link text meets accessibility standards.
On some pages there are empty headings, which may confuse people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (Information and Relationships).
We plan to remove all empty headings on pages by September 2020. When we publish new content we'll make sure heading use meets accessibility standards.
PDFs and other documents
Some of our PDFs and Word documents are essential to providing our services, but 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).
By September 2020, we plan to either fix these or replace them with accessible HTML pages. Any new PDFs or Word documents we publish should meet accessibility standards.
On some pages the colour of the text and the colour of the background are not in sufficient contrast to each other. This doesn’t meet WCAG 2.1 success criterion 1.4.3 (Contrast, Minimum).
We plan to improve colour contrast by September 2020.
On some pages the language has not been set in the code. 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.
We believe that the cost required to fix some of the following issues now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment in the future, for example when supplier contracts are up for renewal.
Interactive tools and transactions
Some of our interactive decision tree tools are difficult to navigate using a keyboard. For example, because some element not highlighted when tabbing through the tool. This doesn’t meet WCAG 2.1 success criterion 2.4.7 (Focus Visible).
Some of our forms are built and hosted through third party software and ‘skinned’ to look like our website. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (Information and relationships).
Other web development issues
On some pages HTML is used to format content rather than CSS. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (Information and Relationships).
On some pages 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).
On some pages the italics-tag 'i' is used to highlight text. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (1.3.1 Information and Relationships).
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).
On some pages the tabbing order is not logical. This doesn’t meet WCAG 2.1 success criterion 2.4.3 (Focus Order).
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).
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, posters or campaign materials that might still be published and accessed through our website.
Any new PDFs or Word documents we publish should meet accessibility standards.
Live video streams don’t have captions. This doesn’t meet WCAG 2.1 success criterion 1.2.4 (Captions - live).
We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
How we tested this website
This website was last tested in September 2019. The test was carried out by the Digital Content Team within Suffolk County Council.
We used a combination of methods to test the accessibility of suffolk.gov.uk:
- automated software (Siteimprove) to crawl and find accessibility issues on our website
- manual sampling and testing of pages to find issues that software might miss
We tested our main website platform, available at www.suffolk.gov.uk.
This statement was prepared on 6 September 2019. It was last updated on 11 October 2019.