Accessibility Statement

Accessibility Statement for Kingston Data

This accessibility statement applies to content published on data.kingston.gov.uk.

This website is run by the Insight and Data Team as part of the Chief Executive’s Department at The Royal Borough of Kingston upon Thames 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
  • use this website on most modern browsers and devices
  • navigate most of the website using only 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)

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:

  • older documents linked to our historical Joint Strategic Needs Assessment (JSNA) section are in PDF format 
  • tables do not have row headings
  • documents have poor colour contrast
  • heading elements are not consistent
  • images do not have captions or alt text
  • document attachments are not written in plain English

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print or braille, email data@kingston.gov.uk 

You will need to tell us:

  • the web address (URL) of the content you cannot access
  • your name and email address
  • the format you need

We’ll consider your request and get back to you within 10 working days.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements then please email data@kingston.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).

Technical information about this website’s accessibility

The Royal Borough of Kingston upon Thames 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 version 2.1 AA standard, due to the following non-compliances listed: 

  • Some images do not have captions or alt text. This means users of assistive technologies do not have context of what the images convey. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content)
  • Some content looks like headings but are not. This makes it difficult for screen reader users to navigate the page. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  • The frame doesn’t reflow when zoomed in at high levels. This fails WCAG 2.1 success criterion 1.4.10 (reflow)
  • Buttons are missing labels. This fails WCAG 2.1 success criterion 2.1.1 (keyboard).
  • We use inaccessible PDFs in the ‘JSNA’ section of the website. Non-HTML documents published on or after 23 September 2018 must have an accessible format. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content)
  • Our interactive tools are difficult to navigate using a keyboard only. This makes it difficult for users of assistive technology. This fails WCAG 2.1 success criterion 2.1.1 Keyboard and 2.4.7 Focus Visible Non-accessible Content

Non-accessible content

Interactive tools and transactions

The interactive tools in ‘Data by Theme’ 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.

Dashboards

Dashboard visualisations are created using Power BI and features have been tested by staff members of the Royal Borough of Kingston upon Thames using internally commonly available tools and standard keyboard controls. 

Every effort has been made to make dashboards as accessible as possible. However, it was not possible to overcome some issues. For example, Power BI has known accessibility limitations which will be kept under review to understand if capability to correct these is possible with the providers tools.

This feature does not meet the accessibility standards in the following ways: 

  • In some instances, longer strings of alternative text may be cut off when using a screen reader. As visualisations are regularly updated with new data, alternative text has been used to describe purpose rather than visible trends. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content)
  • When using assistive technologies, some text may not be recognised as headings (for example, page titles for which alternative text has been used as a mitigation). Also where heading levels have been assigned, these may not be programmatically determined in Power BI’s platform implementation. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)
  • The frame does not reflow when zoomed in at high levels. This fails WCAG 2.2 success criterion 1.4.10 (Reflow) and 1.4.4 (Resize Text)
  • Aspects of certain user interface components, such as slicer outlines and table scroll bars, do not meet the target colour contrast ratio with the page background. The same applies to certain graphical elements, as lighter colours form part of a scheme that has been adopted to ensure sufficient contrast between adjacent bar segments. This fails WCAG 2.2 success criterion 1.4.11 (Non-text Contrast)
  • There are no user options for adjusting text spacing and it is unclear if the use of external tools for this purpose will cause loss of content or functionality. This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing)
  • Tooltips that appear when hovering over data points cannot be dismissed by an alternative means to moving the pointer and the pointer cannot be moved over the additional content. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus)
  • Whilst the dashboards can be navigated using just a keyboard, this functionality can be complex when interacting with certain user interface components. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard)
  • Dashboard titles do not appear in the window title bar or as browser tab names. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled)
  • Navigation by keyboard provides a visible focus indicator, but when selecting a page title banner this can be difficult to see due to low contrast. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible)
  • Some selectable icons may not meet the minimum target size and in certain cases may not have sufficient spacing to mitigate this. This fails WCAG 2.2 success criterion 2.5.8 (Target Size)
  • The default language of each dashboard could not be programmatically determined to ensure identification by assistive technologies. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page)
  • When selecting slicer options, automatic changes in context can occur without pre-warning. This fails WCAG 2.2 success criterion 3.2.2 (On Input)
  • Some text boxes do not have programmatically determined names, particularly where visible headings have not been used. All text boxes do not have programmatically determined roles, due to the repurposing of alternative text to ensure screen readability of text box content. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)
  • Whilst status messages are not used for core functionality, it is unclear if potential error messages would be compatible with assistive technologies. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages)

We will be looking to review this section to see how we can make interactive tools more accessible.

Non-compliance with the accessibility regulations 

Interactive tools and transactions

The interactive tools in ‘Data by Theme’ 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 will be looking to review this section to see how we can make interactive tools more accessible.

PDFs and other documents

Many PDF documents within the ‘JSNA’ section are not accessible for a number of reasons, including missing text alternatives and missing document/table structure so they’re not accessible to a screen reader. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content), WCAG 2.1 success criterion 4.1.2 (Name, Role Value) and WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

We have undertaken a full audit of all the PDF documents accessible via the Kingston Data Website and identified 15 documents (out of 119)  that were produced on or after 23 September 2018 which would not currently be fully accessible. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

All PDF documents produced on or before 23 September 2018 have undergone an accessibility check and have an embedded accessibility report, it is our intention to revisit these documents and replace them with a more accessible version.

Images

Some of our pages and documents contain complex images such as diagrams, charts, graphs or infographics. Some of these may not be adequately described. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).

Disproportionate burden 

We currently are not claiming disproportionate burden on any area of the Kingston Data Website.

Content that’s not within the scope of the accessibility regulations

The vast majority of PDF documents (94 documents, or 86%) within the ‘JSNA’ section of the Kingston Data Website were produced before 23 September 2018. The accessibility regulations do not require PDFs or other documents published before this date to be fixed if they’re not essential to service provision. We intend to phase these documents out and replace them with new reports produced.

Maps

Maps are excluded from the accessibility regulations as long as any essential navigational information they provide is available.

What we’re doing to improve accessibility

We are reviewing and superseding legacy documents with accessible versions, and will update PowerBI dashboards to a more accessible format as Microsoft software updates allow.

Preparation of this accessibility statement

This statement was prepared on 03/07/2023. It was last reviewed on 18/02/2026. It will be reviewed again on 31/03/2027.

This website was last tested on 18/02/2026. The test was carried out by our test team at The Royal Borough of Kingston upon Thames council. 

We tested a selection of pages, making sure those tested reflected the variety of different page layouts used on our website.