Gradle Build Scan UI Accessibility vs IDE Tool Window Interoperability

Gradle's Build Scan UI, introduced in version 2.x, renders task results in HTML tables driven by JavaScript, raising concerns about screen reader announcement and keyboard operability. Documentation does not specify whether ARIA roles or proper focus management are applied, and IDE tool windows that surface Build Scan data may inherit inconsistent accessibility trees across Gradle 7.x and 8.x releases.

Embedding Build Scan URLs directly in console output versus providing a dedicated web link affects how assistive technologies can surface the information, creating an interoperability question between the console and the IDE.

Can Gradle ensure that Build Scan table cells are announced correctly by screen readers when displayed in IDE tool windows?

Does the console output need to provide Build Scan URLs as focusable links with proper ARIA attributes to support keyboard navigation?