This website is run by Royal Borough of Kingston upon Thames . 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)
Our website uses Google translate to offer information in other languages.
We provide some extra information on our website in Portable Document Format (PDF). You need Adobe Acrobat Reader to read these files, it can be downloaded free of charge from the Adobe website. Adobe also provide tools to convert PDF documents into plain text or plain HTML documents to help provide accessible information to people with sight difficulties:
We’ve also made the website text as simple as possible to understand.
AbilityNet has 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:
the text will not reflow in a single column when you change the size of the browser window
you cannot modify the line height or spacing of text
most older PDF documents are not fully accessible to screen reader software
live video streams do not have captions
some of our online forms are difficult to navigate using just a keyboard
you cannot skip to the main content when using a screen reader
there’s a limit to how far you can magnify the map on our ‘contact us’ page
What to do if you cannot 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:
020 8547 5000
We’ll consider your request and get back to you in 10 working days.
If you cannot view the map on our ‘contact us’ page, call or email us 020 8547 5000 [email protected] for directions.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [email protected] or complete our Report an accessibility issue form.
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.
Technical information about this website’s accessibility
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.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non accessible content
Non compliance with the accessibility regulations
Some of our Pre recorded video content does not have captions other than the Youtube subtitles
Which does not meet the of the Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded) of the WCAG 2.1 AA standards we plan to fix the problem by September 2020
Some of our online reporting forms are difficult to navigate when just using a keyboard
Which doesn’t meet Success Criterion 2.1.1 Keyboard of the WCAG 2.1 AA standards we plan to fix this by delivering a programme of replacement forms from our new supplier over the next 18-24 months
Our online reporting maps cannot be fully navigated with just a keyboard
Which does not meet of the Success Criterion 2.1.1 Keyboard of the WCAG 2.1 AA standards
We will review this as upgrades are rolled out on our mapping product
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
Colour contrast on some of our graphic representation on our data website This fails WCAG 2.1 success criterion 1.4.3 Contrast (Minimum)
Interactive tools and transactions
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Our forms are built and hosted through third party software and ‘skinned’ to look like our website. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships).
We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in the next 18-24 months.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2
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. By September 2020, we plan to either fix these 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’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live).
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
3rd party content
Our site includes 3rd party content and functionality.
Depending on our relationship with the 3rd party, we cannot always guarantee its accessibility.
Links to other websites
For the benefit of our users we link to other websites, including:
- news websites
- social media platforms
- official information sources, such as The Met Office, GOV.UK or NHS.UK.
We are not responsible for the accessibility of these or any other websites we do not manage.
Using 3rd party content or functionality on our website
We feature 3rd party content or functionality on our website, including:
- survey tools to collect feedback from users
- insight tools which tell us how people are using the website
- applications for creating forms and storing data.
Where we choose to feature 3rd party content or functionality on our website, we are responsible for ensuring it meets accessibility standards.
If we have paid for content to be created, or have a contractual relationship with the commissioner, we ensure accessibility guidelines are met as part of contractual obligations.
Where we are legally required to feature 3rd party content or functionality, we cannot reasonably accept responsibility for ensuring it meets accessibility standards. However, where it is within our control, we will make every reasonable effort to work towards meeting accessibility requirements
3rd party platforms
We often create content which is hosted on 3rd party platforms. This includes:
- content we create for social media, such as Facebook or Twitter
- video which we host on YouTube or Vimeo
- data we supply to national databases such as Roadworks.org.
We are responsible for ensuring the content we supply meets accessibility requirements; however, we are not responsible for the accessibility of the platform itself.
For example, when we add video to one of our YouTube channels, we will ensure any subtitling, captions and audio-description are included as required. However, we are not responsible for the accessibility of the video player itself.
How we tested this website
This website was last tested on October 2019. The test was carried out by Site improve and Socitm better connected assessment. We also manually review all amended or new content on the site.
The Top 100 pages are sample tested and findings are then checked more widely across the site.
our main website platform, available at www.kingston.gov.uk
Our data website https://data.kingston.gov.uk/transparency-code/
What we’re doing to improve accessibility
We are committed to working with our residents to deliver a website that is fit for purpose and accessible for all. We are replacing the current kingston council website, reviewing all content and ensuring as far as possible the site is compliant with WCAG 2.1 AA standards th
This statement was prepared on 13 November 2019. It was last updated on 13 November 2019.