Last reviewed September 24, 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

Workspace tabs and interactive controls can be reached by keyboard and show a visible focus indicator.
Arrow, Home, and End keys move between workspace tabs.
Variant selections retain keyboard focus when Power BI acknowledges the report filter. Tab continues from the selected control.
Tables use headings, labelled controls, and page-by-page navigation that assistive technology can identify.
Process-map elements have text labels and keyboard focus in addition to color and visual styling.
Threadseer follows high-contrast and reduced-motion preferences when Power BI provides them.
Status, refresh-needed, loading, cancellation, error, and data-quality messages do not rely on color alone.
Layouts adapt to compact, standard, and Power BI focus-mode sizes.

Limits to know

Compatibility with every screen reader and operating-system accessibility configuration is not guaranteed. No formal accessibility conformance assessment is claimed. If a control or view is difficult to use, report the specific environment and task using the contact options below.

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. Email Wittenauer Software LLC at jasonwittenauer@wittenauersoftware.com. Do not email Power BI report files, event logs, credentials, tenant or customer data, or proprietary field names.