Accessibility Statement
This accessibility statement applies to Let’s Talk Kent (https://letstalk.kent.gov.uk).
This website is run by Kent County Council (KCC). We want as many people as possible to be able to use this website.
Our website is built to meet WCAG 2.2 AA standards. That means you should be able to:
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard or 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.
AbilityNet provides advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of this website are not fully accessible:
- you cannot modify the line height or spacing of text
- most older PDF documents are not fully accessible to screen reader software
- user navigating the website using a keyboard will not be able to go back or use the URL search bar on the login and sign in pages. This is known as a keyboard trap as users are unable to move focus away to other content.
Feedback and contact information
Whilst we have spent a lot of time making sure our software is accessible, we know it will not be perfect.
Please contact us if you have an accessibility query or a difficulty on the site including:
- if you are experiencing issues with accessing information or using the website
- if you find an accessibility problem not listed on this statement
- if you have positive feedback on the accessibility considerations made.
If you have a difficulty, please try to include the following information in your email to us:
- the URL for the page you are having problems accessing
- details about what you were trying to do, and why it was difficult or impossible to do it
- details about your computer and software. If you don't know, maybe a friend, relative, or colleague can help you. If not, you can skip this part. Include:
- the operating system you are using, and the version; for example, Windows Vista, Mac OS X, or Linux Ubuntu 9.10
- the browser software you use to view the Web, and the version; for example, Internet Explorer 6 (IE 6), Firefox 3.5, Chrome 3.0.195.38, Opera 10, Safari 4.0.4, etc.
- any settings you have customised; for example, “I set the Font Size to Largest in my browser”
- any assistive technology that you use, for example, screen reader, screen magnification software, voice recognition software for input.
All constructive feedback regarding the accessibility or usability of this website is very welcome and will be carefully considered.
Alternative formats
If you need information in an alternative format, such as braille or a language other than English:
- email alternativeformats@kent.gov.uk
- call 03000 421 553.
- text relay service number: 18001 03000 42 15 53.
This number goes to an answering machine, which is monitored during office hours.
If you identify a document that is not accessible, or you need information in an alternative format or language other than English, please contact our Alternative Formats team.
Complaints process
If you have reported a problem with our website or asked for an alternative format, but you are not happy with our response, you can use our complaints process to register your difficulty. This helps us improve our systems.
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, you can contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
KCC is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Non-accessible content
We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG 2.2 AA standards.
If you find something that does not work that we missed, remember to contact us. Some parts of the website may not work for everyone.
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’ listed below.
Non-compliance with the accessibility regulations
This section covers issues that we need to fix and are working to do so.
Images - Some images on the website do not have a text alternative or names assigned to them, so people using a screen reader cannot access the information. WCAG Guideline Failed: 1.1.1 (Non-text content). We are working to try and fix this issue by 31 March 2026.
Questionnaire button – A screen reader does not pick up if the questionnaire is closed. WCAG Guideline Failed: 1.3.1 (Information and Relationships). We are working to try and fix this issue by 30 June 2026.
Table headings - Some table headings on our consultation and engagement pages are not defined in HTML using the <th> element. WCAG Guideline Failed: 1.3.1 (Information and Relationships). We are working to try and fix this issue by 30 June 2026.
Timeline widget – The widget has a visual element representing the timeline progress, however there is no information provided to a screen reader from this graphic. WCAG Guideline Failed: 1.3.1 (Information and Relationships). We are working to try and fix this issue by 30 June 2026.
Search bar – Does not meet minimum contrast requirements for GUI components. WCAG Guideline Failed: 1.4.11 (Non-text Contrast). We are working to try and fix this issue by 30 June 2026.
Follow Project widget – The border of the subscribe input box does not meet minimum 3:1 contrast requirements for GUI components. WCAG Guideline Failed: 1.4.11 (Non-text Contrast). We are working to try and fix this issue by 30 June 2026.
Links and buttons – Some do not have visible focus. WCAG Guideline Failed: 2.4.7 (Focus Visible). We are working to try and fix this issue by 30 June 2026.
Password input box – The box has autocomplete turned off, which fails accessible authentication. WCAG Guideline Failed: 3.3.8 (Accessible Authentication). We are working to try and fix this issue by 30 June 2026
View Hub link – Not read by screen readers. WCAG Guideline Failed: 4.1.2 (Name, Role and Value) We are working to try and fix this issue by 30 June 2026.
Documents and PDFs - Some projects on the website may contain PDFs and other documents that may not be fully accessible. When we identify a document that does not meet accessibility guidelines, we will, were possible, offer a clearly labelled accessible version.
Documents designed for printing - Some documents on our site are not designed for reading online, for example, posters, leaflets or digital image files. These documents may not be accessible. We will offer a text-alternative for these documents, identify them as printable documents, and offer users an alternative format if requested.
Content that’s not within the scope of the accessibility regulations
This section covers issues that we do not need to fix right now.
Online maps - The accessibility regulations do not require us to fix online maps provided there is an accessible alternative. Our website uses online maps and where there is a map, the information being displayed is provided in an alternative format, where possible, on the same webpage.
Videos - All video content published on the platform will meet accessibility requirements.
Third-party content - Our website contains third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third party to improve its accessibility. This may include:
- links to non-KCC websites
- content/functionality on our website
- content hosted on other websites, such as social media sites.
Some of our third party partners publish their own accessibility statements:
- Facebook - Accessibility Statement
- Twitter – Accessibility Statement
- Instagram – Accessibility Statement
- Engagement HQ / Granicus
Preparation of this accessibility statement
This statement was prepared on 19 December 2022. It was last reviewed on 11 December 2025.
This website was last tested on 8 December 2025 against the WCAG 2.2 AA standard.
The test was carried out by KCC by a manual and by an automated audit. The most used pages were tested using automated testing tools by our Digital Accessibility team.