Tell us what you think of the website
Welcome to your brand new Council website for the Royal Borough of Kingston upon Thames.
Find out what personal information we collect and how it is held and processed when you register with us, contact us or use our services.
This accessibility statement applies to kingston.gov.uk
This website is run by the Royal Borough of Kingston upon Thames Web Team. We want as many people as possible to be able to use this website. For example, that means you should be able to:
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, email us on webmaster@kingston.gov.uk.
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, email us on webmaster@kingston.gov.uk. We’ll consider your request and get back to you in 10 working days.
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).
The Royal Borough of Kingston upon Thames is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
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 content listed below is non-accessible for the following reasons.
We are reviewing our site after launch to ensure that this list is more accurate.
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
Some tables in content do not have table row headers when needed. This means assistive technologies will not read the tables correctly. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
Some pages have form fields arranged in an illogical order, such as placing the "Submit" button before the email input field. This causes screen reader users to encounter the button before filling out required fields, disrupting the meaningful sequence of content. This fails WCAG 2.2 Success Criterion 1.3.2 (Meaningful Sequence).
Some pages have duplicate titles. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.4.2 success criterion (Page Titled).
Some pages are missing the lang attribute in the HTML tag, meaning screen readers cannot determine the language of the content. As a result, users may not receive the correct pronunciation or linguistic support, failing WCAG 2.2 Success Criterion 3.1.1 (Language of Page).
Some form controls, like dropdowns and checkboxes, lack accessible labels or ARIA attributes, leaving screen reader users unaware of their function. This fails WCAG 2.2 Success Criterion 4.1.2 (Name, Role, Value).
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
We are committed to improving accessibility across our website. To ensure we meet accessibility standards, we regularly conduct manual testing and content reviews to identify issues. Additionally, we use Acquia Optimize.
This statement was prepared on 18 August 2025. It was last reviewed on 18 August 2025.
This website was last tested on 18 August 2025 against the WCAG 2.2 AA standard.
The testing was carried out as a self-assessment by our web team and content designers. Manual testing was supported by automated checks using Acquia Optimize to help identify accessibility issues. We are also awaiting additional accessibility testing results from our CMS supplier, which will contribute to a more complete evaluation.
We are committed to ongoing improvement of our website’s accessibility and will continue to review and update this statement as further testing is completed.