Menu

Microsoft PowerBI - accessibility statement

This accessibility statement applies to applications developed using Microsoft PowerApps, built by Kent County Council (KCC).

This content is designed for everyone to find, read, and understand. It is compatible with assistive technologies and developed to meet the accessibility standards outlined in this statement.

View the site your way

There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively.

AbilityNet provide advice on making your device easier to use if you have a disability.

Feedback and contact information

Contact the owner of the application or contact our Contact Centre if you have an accessibility query including:

  • If you are experiencing issues with accessing information or using the app
  • If you find an accessibility problem not listed on this statement
  • If you have positive feedback on the accessibility considerations made
  • If you require content in an alternative format.

Complaints process

Once you have reported a problem with our content 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, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

Kent County Council is committed to making this 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 non-compliances listed below.

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 Web Content Accessibility Guidelines version 2.1 AA standard, and using accessibility tools built into Microsoft 365.

If you find something that does not work that we missed, remember to contact the system owner.

The content listed below is non-accessible for the following reason(s):

Non-compliance with the accessibility regulations

This section covers issues that we need to fix and are working to do so:

1. Screen readers

Screen readers do not announce information about icons in the fields list and in some cases, the screen reader can read more information than what is displayed.

This is not compliant with WCAG guideline 2.1 or  WCAG guideline 1.3.1.

2. Reflow

Not all content is accessible when the page is zoomed in at 400%. The navigation bar overlaps the content and users are unable to scroll with a mouse.

This is not compliant with WCAG guideline 2.1, WCAG guideline 1.4.4, or WCAG guideline 1.4.10.

3. Consistent navigation

Navigation is not consistent throughout ‘View’ mode and ‘Edit’ mode. This is reshuffled and changes the order it should be presented in.

This is not compliant with WCAG guideline 2.1 or WCAG guideline 3.2.3.

4. Name, role, value

Some buttons and controls do not have valid ID attributes and names. There is also an invalid control type defined for report names under ‘Open Report’.

This is not compliant with WCAG guideline 2.1 or WCAG guideline 4.1.2.

5. Status messages

Screen readers do not always announce when there are changes made in the filters that have been applied to the dashboard.

This is not compliant with WCAG guideline 2.1,  WCAG guideline 1.3.1, or WCAG guideline 4.1.3.

6. Disproportionate burden

Not applicable.

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

This section covers issues that we do not need to fix right now:

1. Documents and PDFs

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.

We will be ensuring that any newly published content is accessible and are working to either fix accessibility issues with existing documents that have been published since 23 September 2018, or provide an accessible alternative.

2. 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 on the same web page.

3. Heritage collection items

The accessibility regulations do not apply to reproductions of items in heritage collections that cannot be made fully accessible.

Our website contains reproductions of items in heritage collections. We have made best endeavours to make these accessible. Contact us if you require an alternative format.

4. Videos

The accessibility regulations do not apply to video content published before 23 September 2020.

All video content published from 23 September 2020 will meet accessibility requirements and we are working to make older video content accessible where possible.

Third party content

Some of our applications may contain 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 or functionality on our website that we do not control, develop, or fund
  • Content hosted on other websites, such as social media sites.

Preparation of this accessibility statement

This statement was prepared on 10 September 2021. It was last reviewed on 17 November 2022.