microsoft / microsoft/WPF-Samples
Tooltip associated with "Add declaration to file" control cannot be dismissed: A11y_WPF_Move to file_Content on Hover or Focus
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.7k
- Forks
- 3.3k
- Avg merge
- 12d 8h
- Merged PRs (30d)
- 2
Description
GitHub Tags:
#A11ySev2; #A11yTCS; #WCAG1.4.13; #Win32; #DesktopApp; #Win11; #WPF; #BM_WPFRuntime_Win32_JUNE2025; #ContentonHoverorFocus; #a11ydb-hover-nondismissible;
Issue Subcategory:
Content on hover/focus not dismissible
User Experience:
Users who primarily use keyboard to navigate and low vision users may be unable to dismiss overlapping content while keeping focus or pointer on the trigger, which can block nearby content or controls.
Repro Steps:
Launch Visual Studio 2026> Open any project > Open any file > Provide the below code
"// Go to Tools -> Options -> Preview Features and enable Move to File Refactoring // Select the whole line, Ctrl + . -> Move to File
int a = 0;"
Select Complete line "int a = 0;" and Press "Ctrl + ." > Move to file list item > "Add declaration to file" radio button> Observe the issue: Tooltip associated with "Add declaration to file" control cannot be dismissed.
Actual:
When the tooltip associated with the "Add declaration to file" control is displayed, pressing the Escape key dismisses the entire popup/dialog instead of dismissing only the tooltip
Expected:
The tooltip should be dismissible independently using the keyboard. When the Escape key is pressed while the tooltip is displayed, only the tooltip should be dismissed
How To Fix:
Prefer an accessible tooltip or popover component from a trusted component library that supports dismissal (e.g., Escape) without moving hover or focus, and check the library's accessibility documentation to confirm a dismiss mechanism is enabled. If a library component does not fit, provide a dismissal mechanism such as Escape and/or a close control that works without requiring users to move pointer hover or keyboard focus away from the trigger
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:
https://github.com/user-attachments/assets/521847b2-ce12-43a6-8707-15ef58a95ca6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the WPF scenario described: open a project and file in Visual Studio 2026, invoke Move to File, and focus “Add declaration to file.” Trace the tooltip and popup behavior when Escape is pressed. Done means Escape dismisses only the tooltip while preserving the surrounding dialog, with the expected keyboard behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- accessibility, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100