"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility or the Divisional Driver."
GitHub Tags:
#A11ySev2; #A11yTCS; #WCAG4.1.2; #Win32; #DesktopApp; #Win11; #WinForms .NET Runtime; #BM_WinForms.NETRuntime_Win32_June2025; #NameRoleValue; #A11yMAS; #NVDA;
Environment Details:
Microsoft Windows 11 Enterprise (24H2) Build on 26100.4061
Repro Steps:
- Open Visual Studio 2022.
- TAB to Project menu dropdown and select it (Alt + P).
- TAB to the 'SSIS Import and Export Wizard' and select it.
- TAB to Next button present in 'SQL Server Import and Export Wizard' window and hit ENTER key.
- TAB to "Categorized" button present in 'Choose a Data Source' Screen.
- Observe that the screen reader does not announce the selected state of the button.
Actual Result:
The screen reader does not announce the selected state of the button when it is selected. The state change is not programmatically conveyed to assistive technologies.
Same issue exists for the links in the pane.
Expected Result:
The screen reader should announce the button as "Selected" or "not selected," depending on the current state. This ensures that the state change is programmatically exposed and accessible to users relying on assistive technologies.
User Impact:
Screen reader users cannot determine the current state of the “Categorized” buttons, leading to confusion and uncertainty while interacting with toggle functionality and reducing independent usability.
Attachment:
Similar issue:

"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility or the Divisional Driver."
GitHub Tags:
#A11ySev2; #A11yTCS; #WCAG4.1.2; #Win32; #DesktopApp; #Win11; #WinForms .NET Runtime; #BM_WinForms.NETRuntime_Win32_June2025; #NameRoleValue; #A11yMAS; #NVDA;
Environment Details:
Microsoft Windows 11 Enterprise (24H2) Build on 26100.4061
Repro Steps:
Actual Result:
The screen reader does not announce the selected state of the button when it is selected. The state change is not programmatically conveyed to assistive technologies.
Same issue exists for the links in the pane.
Expected Result:
The screen reader should announce the button as "Selected" or "not selected," depending on the current state. This ensures that the state change is programmatically exposed and accessible to users relying on assistive technologies.
User Impact:
Screen reader users cannot determine the current state of the “Categorized” buttons, leading to confusion and uncertainty while interacting with toggle functionality and reducing independent usability.
Attachment:
Similar issue: