"Method Signature" edit field incorrect role is given as document: A11y_WPF_Change signature_ScreenReader

GitHub Tags:
#A11ySev2; #A11yTCS; #WCAG4.1.2; #Win32; #DesktopApp; #Win11; #WPF; #BM_WPFRuntime_Win32_JUNE2025; #NameRoleValue; #a11ydb-widget-wrong-role;

Issue Subcategory:

Interactive element or widget has incorrect role

User Experience:

Assistive technology announces the wrong control type, confusing users about how to operate the element or what it does.

Repro Steps:

Turn on NVDA > Launch Visual Studio 2026> Open any project > Open any file > Provide the below code
"// Invoke change signature in Func2 to trigger change signature
int Func2(int a, int b, int c)"

Select Complete line "Func2" and Press "Ctrl + ." > Change signature list item > "Method Signature" edit field > Observe the issue: "Method Signature" edit field incorrect role is given as document

Actual:

When focus moves to the "Method Signature" edit field, screen readers announce it as a "document" instead of an edit field.

Expected:

When focus moves to the "Method Signature" field, screen readers should announce the correct role as "edit" (or appropriate text input role) so users can understand that the control accepts text input.

How to Fix

Assign the role that matches the control's actual behavior, or use the native element that conveys it (<button>, <a href>, <select>). Verify the role against the intended ARIA pattern.

Environment Details:

Application Name: WPF
Visual Studio 2026
18.9.0 Canary [11916.14.main]
Edition Windows 11 Enterprise Insider Preview
OS Version 25H2
OS build 26544.1000

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."
"Contact CAI Accessibility Support Channel for Accessibility queries on design, development, test, usability or any processes"

Attachment:

WpfApp9.zip

Reproduce the issue with NVDA in Visual Studio 2026 by opening a project, invoking Change Signature with Ctrl + ., and focusing the “Method Signature” field. The payload names no source file or test, so first identify which component owns this control; done means the field is exposed as an edit or appropriate text-input role rather than a document.