Last reviewed August 25, 2026

Accessibility

Threadseer is designed so people can navigate the workspace by keyboard, see where focus is, use high-contrast themes, reduce motion, and work across different Power BI visual sizes.

What Threadseer supports

Limits to know

The exact 0.1.0.116 report has been checked in Edge across all ten workspace tabs, with Enter and Space transition selection, and at 200% and 400% browser zoom. Firefox behavior was also owner-attested against the exact report. A final-candidate screen-reader, forced-colors, and reduced-motion pass remains required before Marketplace submission.

Threadseer runs inside Microsoft Power BI. Final focus order, zoom, screen-reader behavior, theme contrast, and export behavior also depend on Power BI, the browser or WebView2, the report design, and operating-system accessibility settings.

A dense process map or wide analysis table may need a larger visual or Power BI focus mode. When a graphical path is difficult to inspect, use Cases and the supporting table views for a text-based route to the same evidence.

Report an accessibility problem

Use the Get Help guide and public bug form for a non-confidential example. Include the Threadseer and Power BI versions, assistive technology and version, input method, visual size or zoom level, what you expected, and what happened.

Before you share anything: GitHub issues are public. Do not upload report files, event logs, screenshots containing case identifiers, tenant details, personal information, credentials, or proprietary field names. Use a blank report and synthetic data.

If an accessibility request requires personal, account, purchase, legal, or other non-public information, do not place it in a public issue. A verified private support contact will be published before public sale.