Accessibility statement for Suffolk Resilience
This accessibility statement is for SuffolkResilience.com
This website is run by the Suffolk Resilience Forum Partnership Manager and support team.
We want as many people as possible to be able to use this website. For example, this 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 use the ‘content guidelines’ from Suffolk.gov.uk to help website editors improve accessibility.
Make your device easier to use
‘Ability net’ 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 g the settings in your browser (such as Chrome or Safari).
How accessible this website is
We know some parts of this website are not fully accessible, for example some:
- Images contain text which you may not be able to read
- Links do not make sense on their own
- PDF documents are not fully accessible to screen readers
- Videos do not have captions or audio description
- Interactive tools are difficult to navigate using just a keyboard
What to do if you can not 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 SuffolkResilienceForum@suffolk.gov.uk
- Call 01473263610
We will 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 our more about Interpreting and Translating Services
Reporting accessibility problems with this website
We are always looking to improve the accessibility of this website.
If you find any problems that are not listed on this page or think we are not meeting accessibility requirements, contact the Suffolk Resilience Forum by e-mailing: SuffolkResilienceForum@suffolk.gov.uk or calling 01473 263610
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 are 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 you visit, we can arrange a British Sign languages (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
We are committed to making the 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 standard, due to the non-compliance listed below.
Non accessible content
the content listed below is non-accessible for the following reasons:
Noncompliance with the accessibility regulations
Some images do not have a text alternative (alt text), so the information in them is not available using a screen reader. This does not meet WCAG 2.1 success criterion1.1.1 (non-text content). We plan to add text alternatives for all images by December 2022. When we publish new content, we will ensure our images meet the accessibility standards.
Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This does not meet WCAG success criterion 1.4.5 (Images of Text). We plan to remove or replace images containing text by December 2022. When we publish new content, we will make sure our use of images meets accessibility standards.
On some pages the same link text is used for different link destinations. This does not meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We plan to resolve this uses on all pages by December 2022. When we publish new pages, we will ensure the link text meetings accessibility standards.
On some pages the purpose of each link can not be determined from the link text alone. This does not meet MCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We plan for all link text to make sense in isolation by December 2022. When we publish new pages, we will ensure the link text meets accessibility standards.
On some pages, tables do not have a description set using the caption element. This does not meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. We plan for all tables to have descriptions by December 2022. When we publish new tables, we will make sure they meet accessibility standards.
PDFs and other documents
Some of our PDFs and other documents are not formatted so they are accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, role value). By December 2022, we plan to fix the top 10% most viewed documents. Any new documents we publish should meet accessibility standards where they are required for essential services or users who are likely to have disabilities or impairments.
On some pages there is not sufficient contrast between the colour of the text and the background, making it hard to read the information. This does not meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum). We plan to improve colour contrast by December 2022.
On some Pages the language has not been set in a way that can be understood by a screen reader. This does not 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 December 2022.
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 does not mee WCAG 2.1 success criterion 1.3.1 Information and Relationships. We plan to resolve this issue by December 2022.
On some pages the tabbing order is not logical when navigating using a keyboard. This does not meet WCAG 2.1 success criterion 2.4.3 Focus Order. We plan to resolve this issue by December 2022.
On some pages HTML is used to format content rather than CSS – (Cascading Style Sheets). This does not meet WCAG 2.1 SUCCESS CRITERION 1.3.1 Information and Relationships. We plan to fix this issue by December 2022.
On some pages the iFrame has no ‘title’ attribute or the ‘title’ attribute is empty. This does not meet WCAG 2.1 success criterion 4.1.2 Name, Role, Value. We plan to fix these issues by December 2022.
On some Pages the italics-tag ’I’ is used to highlight text. This does not meet WCAG 2.1 success criterion 4.1.2 Information and Relationships. We plan to fix this issue by December 2022.
We do not categorise any of the accessibility issues on Suffolk.gov.uk as a disproportionate burden to fix within the meaning of the regulations, with the exception of PDFs and other documents.
Suffolk County Council have published a disproportionate burden assessment that explains:
- Carrying out detailed accessibility checks of Suffolk.gov.uk, plus their interactive tools and transactions – as this is their most important content
- Carrying out basic checks of their other websites, as paying for detailed checks would be a disproportionate burden on their organisation
- Plan to fix the top 10% most viewed documents on Suffolk.gov.uk by September 2020 and ensure that any new document required to access an essential service is accessible.
Content that is 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 other documents do not meet accessibility standards. For example, they may not be structured so they are accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 Name, Role Value.
The accessibility regulation does not require us to fix PDFs for other documents published before 23rd September 2018 if they are not essential to providing our services.
We plan for the top 10% most viewed PDFs and other documents published since 23rd September 2018 (and essential service documents published before) to meet accessibility standards by December 2022.
Live video streams may not include captions. This does not 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 pre-recorded videos published before 23rd September 2020 do not include captions. This does not meet WCAG 2.1 success criteria 1.2.2. Captions (Pre-recorded). We may not add captions to these videos because pre-recorded video published before 23rd September 2020 is exempt from meeting the accessibility regulations.
Some pre-recorded videos published before 23rd September 2020 may require, but do not include, audio description. This does not meet WCAG success criteria 1.2.5 Audio Description (Pre-recorded). We may not add audio description to these videos because pre-recorded video published before 23rd September 2020 is exempt from meeting the accessibility regulations.
Any pre-recorded video content we publish after 23rd September 2020 will meet accessibility standards.
Online maps and mapping services are exempt from meeting the accessibility regulations. From 23rd September 2020 we will ensure that where maps are intended for navigational use essential information is provided in an accessible digital manner.
For archived content, which is no longer updated, you can contact us to request historical data in an accessible format.
How we tested this website
This website was last tested in September 2020.
We used a combination of methods to test the accessibility of Suffolk.gov.uk, including
- Automated software (Webaim.org)
- Manual sampling
This statement was prepared on the 21st September 2020. It was last updated on 22nd September 2020.