Visually, the table contains 7 columns; however, when navigating through the table using NVDA, the screen reader announces the total number of columns as 8: A11y_Table_Query Builder_Screen Reader

Storage Explorer Version

1.42.1

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

Windows

OS Version

No response

Bug Description

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

GitHub Tags:

#A11ySev3; #A11yTCS; #DesktopApp; #Win11; #FTP; #Azure Tools Storage Explorer; #E2E_Azure Tools Storage Explorer_Win32_April2026; #Win32; #WCAG1.3.1; #A11yMAS; #NVDA; #Element:Table;

Environment Details:

Application Name: Azure Tools Storage Explorer
Az copy Version: 10.31.0
Operating System: Windows 11 version 25H2

Resource Types

No response

Authentication Method

Sign in

Connection Type

Sign in (subscription)

Steps to Reproduce

1. Start NVDA.
2. Launch Storage Explorer
3. TAB till "Open Connect dialog" pane and Sign in to Azure.
4. TAB till "Manage Accounts" pane and Select the subscriptions you will use. Once selected, hit ENTER on "Apply" button.
5. TAB till "Tables" of the selected subscription, press SHIFT + F10 and hit enter on "Create Table" to Create a new table.
6. Once completed, hit ENTER on "Query" button.
7. TAB till table.
8. Observe the issue Visually, the table contains 7 columns; however, when navigating through the table using NVDA, the screen reader announces the total number of columns as 8

Actual Experience

Visually, the table contains 7 columns; however, when navigating through the table using NVDA, the screen reader announces the total number of columns as 8. This results in a mismatch between the visual presentation and the information conveyed through assistive technology.

Expected Experience

NVDA should announce the correct number of columns present in the table, which is 7, ensuring that the information conveyed to screen reader users accurately reflects the visual structure of the table.

Additional Context

User Impact:

Screen reader users may become confused due to the discrepancy between the announced and actual number of columns in the table. This inconsistency can make it difficult for users to understand the table layout, accurately navigate between columns, or interpret tabular data correctly. As a result, users relying on assistive technologies may face challenges in accessing and comprehending the information presented within the table, leading to an inefficient and inaccessible user experience.

Attachment:

https://github.com/user-attachments/assets/331286f7-7b62-45a1-8ede-0e1e76f982dd