Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility: Screen readers (Narrator, JAWS, NVDA) read aloud "DesktopChildSiteBridge" on XAML Windows #9352

Open
rmlaapl opened this issue Feb 22, 2024 · 1 comment
Labels
accessibility Narrator, keyboarding, UIA, etc team-CompInput Issue for IXP (Composition, Input) team team-Reach Issue for the Reach team

Comments

@rmlaapl
Copy link

rmlaapl commented Feb 22, 2024

TL;DR
Applications that speak out loud what is happening on the screen (for sight-impaired people) appear to use the window's text as the source of words that they speak whenever Automation/Accessibility properties are not set.

The following is a problem in at least version 1.4.2312190001 of Windows App SDK: an SDK-created window with the class name "Microsoft.UI.Content.ContentWindowSiteBridge" has its text set (i.e. WM_SETTEXT) to DesktopChildSiteBridge. This causes a screen reader to read the title of your top-level XAML window, and then immediately speak that string of words, which would be very disorienting as a person relying on accessibility features.

This is a screenshot from Accessibility Insights, highlighting the window in question:

Screenshot 2024-02-21 at 19 19 01

The fix for this is extremely simple: just don't set the window text on that ContentWindowSiteBridge, and all will be well :)

I noticed this was/is also an issue in MAUI

In our application, I fixed it with some old school Win32: EnumChildWindows looking for that class name, and if found, set its text to an empty string.

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Feb 22, 2024
@bpulliam
Copy link
Contributor

not a duplicate of #7853. that was fixed in 1.3. internal bug

@bpulliam bpulliam added accessibility Narrator, keyboarding, UIA, etc team-Reach Issue for the Reach team team-CompInput Issue for IXP (Composition, Input) team and removed needs-triage Issue needs to be triaged by the area owners labels Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Narrator, keyboarding, UIA, etc team-CompInput Issue for IXP (Composition, Input) team team-Reach Issue for the Reach team
Projects
None yet
Development

No branches or pull requests

2 participants