Enable Proper Heading Structure in Power BI Reports (Issue: Accessible Headings)

[TimothyWharton]

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Info and Relationships (1.3.1). While it is possible to add visible headings, there is no way to apply a proper heading hierarchy programmatically. For example:

• There is no option to apply heading 1 formatting to the main text heading (ie. nest it within an h1 HTML element).
• Heading tags (h1-h6 HTML elements) can only be applied to entire text boxes, not specific text within them.
• A 'Power BI Report' visually hidden heading 2 (h2 HTML element) is automatically inserted and cannot be edited or removed.

Impact: This creates a significant barrier for screen reader users, preventing them from reliably identifying and navigating using headings. It also means reports cannot achieve WCAG 2.2 AA compliance.

Request: Please provide full support for semantic heading structures in Power BI reports, including the ability to apply heading levels (H1–H6) to individual text elements. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services.

[MaryanneBSA]

A workaround we have implemented is to use the JSON theme file in combination with a template (.pbit) file for our organisation. In the template we set heading 2 for the page title (a text box with only a title), heading 3 for the page subtitle (another text box with only a title), and then use the theme to set heading 3 for all subsequent visuals. Heading 1 is the report name and settings for this are controlled by Microsoft (sometimes appears as an aria label and not a heading). Not a perfect solution, but sharing in case it assists anyone in configuring more accessible reporting.