Issue Summary

Screen Reader Does Not Announce AI Response Generation Status After Selecting a Prepopulated Prompt.

Steps to Reproduce

1. Open the Jira Cloud homepage.
2. Navigate to the top navigation section and activate the "Ask Rovo" button.
3. Using a screen reader, navigate to the "What's Rovo Search?" prepopulated prompt and press Enter to activate it.
4. Observe that no status message or dynamic content updates are announced to screen reader users while the AI response is being generated.

Screen Recording

Ask Rovo Issue

Actual Results

When screen reader users activate the "What's Rovo Search?" prepopulated prompt in the "Ask Rovo" chat interface, the AI begins generating a response and the interface shows a status such as “Rovo Expert is thinking”. However, this status message is not announced to screen reader users, and dynamically updated content is not conveyed as it is generated.

As a result, screen reader users may be unaware that the system is processing the request and that new content is being added to the conversation.

This creates an inconsistent experience between visual and screen reader users, as important status updates and dynamic content changes are not programmatically communicated to assistive technologies.

Expected Results

All status messages and dynamic content updates should be programmatically conveyed to screen reader users.

Apply the following changes:

• Add an ARIA live region (role="status" or aria-live="polite") to announce chat status updates such as “Rovo Expert is thinking,” response generation start, and response completion.
• Keep the live region permanently present in the DOM so updates are consistently announced by screen readers.
• Update the live region text only on key state changes so screen readers announce the latest status.
  Announce a clear completion message (e.g., “Response ready” or “Response generated”) when the AI finishes generating the response.
• Ensure only meaningful status updates are announced and avoid frequent updates during streaming to prevent screen reader overload.
• Do not move keyboard focus during status updates; keep focus stable in the chat or input area.
• Replace previous status text on each update so every change is re-announced correctly.

For more information on implementing the live regions, visit https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Environment

MacBook Pro (16-inch, 2021)
macOS Tahoe 26.4
Operations - Windows11
Chrome - 148.0.7778.179 (Official Build) (64-bit)
Safari- Version 26.4
JAWS- Version 2026
NVDA- Version 2025.3.3
VoiceOver - Version Latest