Report check
Power BI Report Accessibility Check
Paste your report link. We open every visible page the way a visitor would, click its bookmark buttons, hover the tooltips, press Tab through it, measure the contrast of each text item and chart colour, and count the visuals you used.
- Starting the checker
- Opening your report
- Checking pages
After a quiet spell the checker needs up to 30 seconds to start.
WCAG 2.2 results
Each row is one success criterion. The score is the share of checked items that pass; open a row to see what failed and on which page.
What a machine can't judge
Automated checks show where to look. They can't tell whether alt text describes the insight, whether colour alone carries meaning, or how a screen reader announces your visuals. This is not a WCAG certification.
Visuals used
Core visuals ship with Power BI. Custom visuals come from AppSource or a file and run in a sandbox, which is how we tell them apart.
Tab order, page by page
Where the Tab key takes a keyboard user, drawn on each page. Pick a page.
What we check
Five WCAG 2.2 success criteria that can be measured in a published Power BI report, plus an inventory of the visuals you used.
Alt text
WCAG 1.1.1Every visual that isn't marked decorative has alt text, so screen reader users know what it shows.
Text contrast
WCAG 1.4.3Each text item stands out from what's behind it: 4.5:1, or 3:1 for large text.
Chart colour contrast
WCAG 1.4.11Bars, lines and slices reach 3:1 against the background and against the colours they touch.
Keyboard access
WCAG 2.1.1Every data or interactive visual can be reached with the Tab key.
Tab order
WCAG 2.4.3Tab moves left to right, top to bottom, the way people read the page. We draw it on a screenshot of each page.
Buttons and tooltips
All five checksWe click every bookmark button and check each view it opens, and hover the charts to check report-page tooltips.
Visuals used
Inventory, not scoredHow many core and custom visuals each page uses, and which ones.
Find your report link
The checker needs a public link to the report itself. There are two ways to get one.
Use the bookmarklet
The community site blocks automated visitors, so we can't open your entry post. The bookmarklet reads the report link from the post in your own browser.
- Drag this button to your browser's bookmarks bar:
Check accessibility - Open your entry on community.fabric.microsoft.com.
- Click the bookmark. This page opens and starts the check.
Drag the button to your bookmarks bar; clicking it here does nothing.
Publish to web
- Open the report in the Power BI service.
- Choose File › Embed report › Publish to web (public).
- Copy the link, not the HTML code, and paste it above.
Reports that need a sign-in, including links from your workspace, can't be checked.
app.powerbi.com/view?r=…, app.fabric.microsoft.com/view?r=… and the community report viewer (…/iframeEmbed/…).Limits & privacy
The tool is free, so a few limits keep it fast for everyone.
- Up to 12 pages per reportLonger reports are checked from the first visible page on; the results say how many were left out.
- 10 checks per hourPer visitor. Checking the same link again within 10 minutes shows the earlier result.
- Results are kept for 1 hourBookmark the results page to come back to it. After an hour the results and screenshots are deleted.
- No sign-in, public reports onlyWe open the report like any visitor would. Nothing is stored beyond the hour.
- One check at a timeChecks wait in line; the page shows how many are ahead of yours.
- Button views and tooltips are sampledEach bookmark button is clicked once, for up to 8 views per page and 5 minutes per report. Tooltips are hovered on two data points per chart, so one that only shows for certain data can be missed.
- Custom visuals are partly visibleTheir text is checked for contrast, but their chart colours often can't be read.