Triage External Metrics (TEM) accessibility statement

We want as many people as possible to be able to use this website.

For example, that means you should be able to:

• use your web browser to change colours, contrast levels, and fonts
• zoom in up to 400% with text staying visible on the screen, and most images scaling without resolution loss
• navigate most of the website using a keyboard
• navigate most of the website using speech recognition software
• read most of the website using a screen reader, including the latest versions of JAWS, NVDA, and VoiceOver
• read most of the website on devices without a screen, like a braille computer
• use the website even if Javascript is switched off

We’ve also made the website text as simple as possible to understand. Some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means.

If you have a disability then AbilityNet has advice to help you make your device easier to use.

We know that parts of this website aren't fully accessible. For example:

• some headings are tagged incorrectly for screen readers
• some content cannot be read by a screen reader
• some components display low contrast
• some content is not displayed correctly when zoomed
• some data visualisations are not read out clearly by screen readers

We are actively working to address these issues as part of ongoing improvements to accessibility.

If you need information on this website in a different format like an accessible PDF, large print, easy read, audio recording or braille email [email protected].

We will consider your request and get back to you as soon as possible.

We're always looking to improve the accessibility of the website.

If you find any problems not listed on this page, or think we're not meeting accessibility requirements, email [email protected] with details of problems you have encountered.

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, please contact the Equality Advisory and Support Service. 

We are committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard, except for the non-compliances and exemptions listed below.

The items listed below are non-compliant. Reasons are provided.

7.1 Issues with navigation and screen readers

Power BI does not allow dynamic text in alt text. This means that alt text can't include numbers that update when the underlying data updates for screen readers. This fails under **1.1.1 Non-text Content (Level A)**.

Keyboard focus indicators in Power BI bar charts may highlight either the bar or its category label, but not both simultaneously. This behaviour is controlled by the Power BI rendering engine and cannot be configured by report authors. This means that the user needs to visually match the colours to the legend. This fails under **1.4.1 Use of Color (Level A)**.

Power BI does not use conventional keyboard commands to traverse elements, and these cannot be changed. To avoid confusion, all elements are organised in a single flat hierarchy. This way the user only needs to use the `Tab` and `Shift` + `Tab` keys to navigate the page. Header buttons in the top right of each visual can be accessed with a keyboard but intermittently. We can't hide some of the header icons due to Power BI limitations. This fails under **2.1.1 Keyboard (Level A)**.

Power BI cannot mark up some headings so that they can be understood by screen readers. This includes the dashboard title and page title. This fails under **1.3.1 Info and Relationships (Level A)** and **2.4.6 Headings and Labels (Level AA)**.

Changes to the data shown on the page when the user applies filters are not conveyed to screen readers. This functionality is not natively available in Power BI. This fails under **1.3.3 Sensory Characteristics (Level A)** and **4.1.3 Status Messages (Level AA)**.

The *webpage* supports portrait and landscape orientation, but the *report page* layout is static. This is because Power BI report pages are freeform canvases and this cannot be changed. This fails under **1.3.4 Orientation (Level AA)**.

Other than `Enter`, `Esc`, `Space`, the only single-character shortcut is `?` to show keyboard shortcuts. These cannot be modified or switched off. This fails under **2.1.4 Character Key Shortcuts (Level A)**.

Non-interactive elements can be marked to be skipped by screen readers. But if this is applied to text elements, they are not read out by screen readers at all. This would cause confusion, and so we have marked only decorative elements as skipped. This fails under **2.4.3 Focus Order (Level A)**

We have configured the tab order to be as intuitive as possible. However, some visuals do not use the `Tab` or arrow keys in an intuitive way. This includes the tab indices in horizontal stacked bar charts and Sankey diagrams. This cannot be changed in Power BI. This fails under **2.4.3 Focus Order (Level A)**.

A native search feature is not available to add to a Power BI report. While the Power BI Service does have a search bar in the header, this doesn't direct the user to a relevant visual when search terms are entered. This fails under **2.4.5 Multiple Ways (Level AA)**.

Buttons in the top right corner of each card can overlap with elements underneath. We can't hide some of the header icons due to Power BI limitations. This fails under **2.4.11 Focus Not Obscured (Minimum) (Level AA)**.

All down events can be cancelled except for charts. This is because when the mouse is moved away from a datapoint while holding down the left click, it creates a selection boundary to select multiple datapoints for filtering. The only way to undo this is to release the click, then click twice on the datapoint to undo the filtering. This fails under **2.5.2 Pointer Cancellation (Level A)**.

The dashboards use ARIA labels in most places rather than standard HTML. This means some components have confusing roles. This is because Power BI converts report pages into HTML itself, and the developer cannot edit the resulting code. This fails under **2.1.1 Keyboard (Level A)** and **4.1.2 Name, Role, Value (Level A)**.

7. 2 Issues with content visibility and interactivity

In some cases, the text labels of non-selected data points are dimmed by Power BI and the contrast against the background colour is below the minimum requirement of 4.5:1. This cannot be changed. This fails under **1.4.3 Contrast (Minimum) (Level AA)**.

Text size and text spacing cannot be changed in the user interface. This includes the text in the report and in the hover tooltips. It can only be changed in the browser settings. This means that if the text size or text spacing is increased it may be truncated by the text box. Report pages are freeform canvases and text boxes do not resize to fit their content. This cannot be changed. This fails under **1.4.4 Resize Text (Level AA)** and **1.4.12 Text Spacing (Level AA)**.

Dashboard pages are set to 'fill width' by default. Browser zoom controls affect the Power BI Service interface but not the zoom level of the dashboard page itself. This fails under **1.4.4 Resize Text (Level AA)**.

If users zoom in using the browser zoom functions, they will need to scroll vertically and horizontally to view the content. This is because Power BI report pages are freeform canvases and this cannot be changed. This fails under **1.4.10 Reflow**.

The colour contrast ratio of the drop-down filter borders against the background is below the minimum requirement of 3:1. The border colour cannot be changed in Power BI. This fails under **1.4.11 Non-text Contrast (Level AA)**.

Menu buttons in the header of each card and some interactive elements in charts have a small target size. These are standard Power BI buttons and cannot be resized or resized sufficiently to be compliant. This fails under **2.5.8 Target Size (Minimum) (Level AA)**.

The markers in line charts are clickable and the click target area is below the minimum required size of 24x24px. The markers can also sometimes be closer than the minimum required distance of 24px. This fails under **2.5.8 Target Size (Minimum) (Level AA)**.

We are doing the following to improve the accessibility of our website:

• we have conducted an external audit to evaluate the current state of our online platform.
• we have had accessibility training to better understand existing accessibility issues that are currently present on our online platform.
• we are planning to fix the issues based on the external audit in the near future

This statement was prepared on 29 April 2026. It was last reviewed on 29 April 2026.

This website was last tested on 29 April 2026. The test was carried out by Dig Inclusion Ltd.

Read the full accessibility test report.