This accessibility statement applies to www.cambridge.gov.uk.
This website is run by Cambridge City 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 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’ve also made the website text as simple as possible to understand.
To help customers adapt this website to their specific needs, we have also installed the Recite.me toolbar which can be opened by selecting the ‘accessibility tools’ link in the website header. You can find more information about Recite.me on our Accessibility page.
AbilityNet has advice on making your device easier to use if you have a disability.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact webteam@cambridge.gov.uk.
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, find out about alternative formats. We’ll consider your request and get back to you within 7 days.
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 Deaf, hearing impaired or have a speech impediment.
Some of our offices and public spaces have audio induction loops, and if you contact us before your visit we can arrange an interpreter.
If you are a British Sign Language (BSL) user, you can use a free online service called SignLive to contact us through a professional interpreter.
Technical information about this website’s accessibility
Cambridge City 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
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
PDFs
Some of our PDFs do not meet accessibility standards. The actions identified are:
- Tag all PDFs (WCAG A 1.3.1)
- Ensure PDFs are machine readable (WCAG A 1.1.1)
- Ensure PDFs have a title (WCAG A 2.4.2)
- Specify headings for every PDF (WCAG A 1.3.1)
- Ensure PDFs specify a default language (WCAG A 3.1.1)
- Ensure PDF headings follow a logical order (WCAG A 1.3.1)
- Ensure the first heading in a PDF is a H1 (WCAG A 1.3.1)
- Ensure long PDFs use bookmarks to aid navigation (WCAG AA 2.4.5)
- Check PDFs have sufficient text contrast (WCAG A 1.4.3)
- Ensure PDF content is in a meaningful sequence (WCAG A 1.3.2)
Search
We use Google to provide the search on our website. The plug-in code adds a second search field to the search page, which is not fully accessible.
- Add a submit button to all forms (WCAG A 3.2.2)
Maps
Some of the controls on the Google maps on our site have controls that are close together, which can make it difficult to select the right element. We are working to replace Google Maps with another system.
Some of our embedded maps do not have a title, which can make it harder for people assistive technology to understand what the content is.
- Specify a title for all frames (WCAG A 2.4.1)
Form sign in page
Some of our forms start with a page that asks whether you want to sign in to complete it. The small size of a checkbox on this page could make it difficult for people to select it. We will make this element larger.
- Ensure interactive components are far enough apart (WCAG AA 2.5.8)
Breadcrumbs
Our breadcrumbs are too close together which could make it difficult to select them. We will make the text larger or increase the space in between the links.
- Ensure interactive components are far enough apart (WCAG AA 2.5.8)
Forms
Some form fields, have the same ‘ID’ in the page code, which can cause assistive technologies to stop working.
- Fix duplicate IDs (WCAG A 4.1.1)
Hamburger menu
At 200% zoom and more, once the hamburger menu has been expanded it cannot be closed and the keyboard focus becomes trapped within the menu.
- No keyboard trap (WCAG A 2.1.2)
At 400% zoom, once the hamburger menu is expanded the cookie icon covers all links within the hamburger menu.
- Reflow (WCAG AA 1.4.10)
Cookie banner
At 200% zoom, the keyboard focus is not visible when it tabs onto the section 'This website uses cookies' within the pop up cookie banner as the page loads.
At 400% zoom, the keyboard focus is not visible on any elements within the cookie banner (including when the cookie icon in the corner of the webpage is expanded).
At 400% zoom, the keyboard focus is not visible on the cookie icon in the bottom corner of the webpage.
- Focus visible (WCAG AA 2.4.7)
Homepage
This refers to the unordered list element that contains links such as 'Bin collection calendar', 'Report it', 'Pay' and 'Planning applications'. The list contains <hr> elements that are not allowed as direct children of a <ul> element.
- Info and relationships (WCAG A 1.3.1)
Subscribe to Cambridge City Council email alerts page
The lang attribute is missing from the webpage.
- Language of page (WCAG A 3.1.1)
Accessible text is missing from the textbox for 'Email address (mandatory)' and all checkboxes under 'Topics'.
- Info and relationships (WCAG A 1.3.1) and Name, role, value (WCAG A 4.1.2)
Cambridge City Council Employment Committee 9 October 2025 PDF
The document has elements that do not have sufficient colour contrast. This includes red text in the table on page 13, such as '3C Building Control' and 'Communities'.
- Contrast (minimum) (WCAG A 1.4.3)
The language is missing within the settings of the PDF document.
- Language of page (WCAG A 3.1.1)
There are tables in the document that do not have correctly marked up headers.
- Info and relationships (WCAG A 1.3.1)
The document has multiple images that do not have alternative text.
- Non-text content (WCAG A 1.1.1)
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. We are working to fix any remaining documents that fall under this category or replace them with accessible HTML pages.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services.
We endeavour to ensure that all new documents we publish will meet accessibility standards.
Documents provided by third parties
Some documents have been provided by third parties. We did not commission, create, or pay for these documents, so they are exempt from the accessibility regulations.
Live video
We do not plan to add captions to live video streams because live video is exempt from the accessibility regulations.
Maps
Our maps are either not used for navigational purposes, or we provide information in another format if they are, and so are exempt from the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 6 August 2019. It was last reviewed on 17 November 2025.
This website is continuously monitored by the Communications and Engagement team. We use the Silktide website monitoring software to report accessibility issues against the WCAG 2.2 AA Standard.
