Skip to content

Success message is not announced by screen reader after activating "Create Index" button:A11y_DocumentDB for VS Code Extension_Creating index_ScreenReader #772

Description

@kapilvaishna

GitHub Tags

#A11yTCS; #E2E_DocumentDB_Win32_JUNE2026; #DocumentDB for VS Code Extension; #DesktopApp; #FTP; #Win32; #A11ySev2; #A11yMAS; #WCAG4.1.3; #StatusMessage;  #ScreenReader; #NVDA;

Issue Subcategory

Success/error message not announced

User Experience

Screen reader users are not informed of form submission success, validation errors, or important status changes. They must manually search the page to discover what happened.

Repro Steps

Open VS code > Install the DocumentDB for VS Code Extension and open it > Add new Connections > Expand one of the databases > Expand a collection within that database > Double-click the Documents item > Run query { Reviews : 10 } > Query Insights tab > Get AI Performance Insights button > Create Index button > Observe the issue: Success message is not announced by screen reader after activating "Create Index" button.

Actual Result

fter activating the"Create Index" button, a success message ("Index 'rating_1' created successfully") is displayed on the screen. However, the success message is not announced by screen readers, and users are not informed that the index creation operation completed successfully.

Expected Result

When the success message appears, it should be programmatically exposed as a status message so screen readers automatically announce the newly displayed confirmation without requiring users to move focus to the message.

How to Fix

Use ARIA live regions: role="status" with aria-live="polite" for non-urgent messages, or role="alert" (implicitly aria-live="assertive") for urgent errors. Ensure the live region exists in the DOM before content is injected

Environment details

Application Name: VS Code
Extension: DocumentDB for VS Code
Extension Version: 0.9.1
Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8390

Note

  • Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.
  • "Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

Attachment

772_NVDA.mp4

Metadata

Metadata

Assignees

No one assigned

    Labels

    a11yAccessibility Issues

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions