Accessibility

Find out how accessible our website is, how to report accessibility issues and what to do if you can’t access parts of this website.

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)

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 files may not be suitable for users of assistive technology.

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 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

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 digitalcontentteam@suffolk.gov.uk.

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).

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.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 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 (website) 

PDFs and other documents

Many of our PDFs and other document types may not be suitable for users of assistive technology. This fails WCAG success criterion 4.1.2 Name, Role Value. We plan for all our website documents to be accessible by September 2021. 

Label is not connected to a form control

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 fails WCAG success criterion 1.3.1 Info and Relationships. We plan to resolve this issue by December 2020. 

"Aria-describedby" has incorrect (ID) reference

On some pages the WAI-ARIA 'aria-describedby' attribute has a reference to an ID that does not exist or an ID that is not unique. This fails WCAG success criterion 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 2.4.4 Link Purpose (In Context), 3.3.2 Labels or Instructions, and 4.1.2 Name, Role, Value. We plan to resolve this issue by December 2020. 

HTML is used to format content

On some page presentational attributes such as 'border', 'align', or 'bgcolor' are used. CSS should be used for styling instead. This fails WCAG success criterion 1.3.1 Info and Relationships. We plan to resolve this issue by December 2020. 

Form elements are not grouped

On some pages when a form contains elements that are logically connected they have not been grouped. This fails WCAG success criterion 1.3.1 Info and Relationships, and 3.3.2 Labels or Instructions. We plan to resolve this issue by December 2020. 

Invalid WAI-ARIA role, state or property

On some pages a WAI-ARIA element contains a role, state or property that is invalid or not allowed on this type of element. This fails WCAG success criterion 4.1.2 Name, Role, Value. We plan to resolve this issue by December 2020. 

Select box has no description

On some pages drop down menus (select boxes or role="listbox") do not always have a description that is explicitly associated with the field to make sure that users of assistive technologies will also know what the field is for. This fails WCAG success criterion 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, and 4.1.2 Name, Role, Value. We plan to resolve this issue by December 2020. 

Buttons for 'select box'

On some pages a drop down box (select) is present without a submit button. This fails WCAG success criterion 3.2.2 On Input. We plan to resolve this issue by December 2020. 

Field label is not visible

On some pages the input field does not have a visible label indicating the purpose of the input field. This fails WCAG success criterion 3.3.2 Labels or Instructions. We plan to resolve this issue by December 2020. 

Non compliance with the accessibility regulations (transactions) 

In addition to testing suffolk.gov.uk, we've carried out detailed accessibility checks of digital transactions associated with the Suffolk County Council website.

Non compliance for these transactions has been grouped by their portals or technology platforms. 

Citizen Portal (Capita)

This portal provides online services such as applying for:

  • school places
  • free school meals 
  • funded school travel

In this case, a full accessibility statement has been published independently of suffolk.gov.uk. Read the Citizen Portal accessibility statement.

Adult and children's portals (Liquidlogic)

For other transactions, we have not published a separate accessibility statement for practical purposes.

We provide multiple portals for adult and children's services, including the Suffolk Adult Care Portal and Suffolk Children and Young People's Portal.

These portals cover transactions such as:

  • requesting social care support
  • reporting a safeguarding concern 
  • making a referral for early help services (CAF)

The accessibility issues affecting adult and children's transactions are typically consistent across all portals provided by the same external supplier. The main issues include:

  • Text does not always have a contrast ratio of at least 4.5:1 against its background colour. This fails WCAG success criterion 1.4.3 Contrast minimum.
  • User Interface components and graphical objects do not always have contrast ratio of at least 3:1. This fails WCAG success criterion 1.4.11 Non-Text Contrast.
  • It's not always possible for someone using a keyboard or touch device to complete all tasks in a service. This fails WCAG success criterion 2.1.1 Keyboard.
  • It's not always possible for someone navigate through content in a way that makes sense. This fails WCAG success criterion 2.4.3 Focus order.
  • It's not possible for keyboard users to move focus directly to the start of the main content area of the page when there's repeated content at the top of the page. This fails WCAG success criterion 2.4.1 Bypass blocks.

We have carried out some accessibility fixes across these portals, and are working with our supplier to resolve the remaining issues by September 2021. 

Microsoft Dynamics 

There are a range of digital transactions we provide that have been developed using Microsoft Dynamics, for example: 

Our accessibility checks based on sample of transactions using this platform have revealed several instances of non-compliance with WCAG success criteria. The main issues include: 

  • Text does not always have a contrast ratio of at least 4.5:1 against its background colour. This fails WCAG success criterion 1.4.3 Contrast minimum.
  • Some elements do not have any labels associated with them. This fails WCAG success criterion WCAG 2.4.6 Headings and Labels.
  • Some fields do not have accessible names. This fails WCAG success criterion 4.1.2 Name, Role, Value.
  • It’s impossible to tab out using the keyboard on one of the modals in the Schools Fixed Penalty Notice online service (internal only). This fails WCGAG success criterion 2.1.2 No Keyboard Trap

We're currently going through the process of rebuilding these transactions on a new digital services platform provided by a third-party supplier (Goss). All accessibility issues associated with Dynamics will be fixed in the new versions of the transactions, which will be available by September 2021. 

Disproportionate burden

We don't 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). 

We've published a disproportionate burden assessment that explains: 

  • we carried out detailed accessibility checks of suffolk.gov.uk and our interactive tools and transactions - as this is our most important content
  • we carried out basic checks of our other websites - as paying for detailed checks would be a disproportionate burden on our organisation
  • we planned to fix the top 10% most viewed documents on suffolk.gov.uk by 23 September 2020 - as fixing every document would be a disproportionate burden on our organisation

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 other documents may not be suitable for users of assistive technology. This fails WCAG 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 planned to fix the top 10% most viewed PDFs and other documents published since 23 September 2018 (plus any essential service documents published previously) by 23 September 2020. 

Video

Live video streams may not include captions. This fails WCAG 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 fails WCAG 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 fails WCAG 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. 

Maps 

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.

Archived content

Our elections website elections.suffolk.gov.uk is archived and not within scope of the accessibility regulations. The website is no longer updated, but you can contact us to request historic data in an accessible format. We plan to launch a new elections website in time for the county council elections scheduled for May 2021. 

What we’re doing to improve accessibility

We've fixed many accessibility issues on suffolk.gov.uk in the lead up to the regulations deadline of 23 September 2020, and we'll continue to improve the current version of our website going forward.

However, we've also started the process of replacing suffolk.gov.uk with a new website platform. It may be more practical and cost-effective to ensure some accessibility issues are fixed in the next version of suffolk.gov.uk, which we hope to launch by December 2021. 

Preparation of this accessibility statement

This statement was prepared on 6 September 2019. It was last reviewed on 23 September 2020.

A detailed accessibility check of www.suffolk.gov.uk was last carried out in September 2020 by Suffolk County Council's Digital Content Team.

We carried out our testing based on a sample of our most used pages, forms, documents and other media.

We used a combination of methods to check this website, including: 

  • automated software (Siteimprove)
  • manual sampling (using WAVE and other tools)