Accessibility: Screen readers (Narrator, JAWS, NVDA) read aloud "DesktopChildSiteBridge" on XAML Windows #9352
Labels
accessibility
Narrator, keyboarding, UIA, etc
team-CompInput
Issue for IXP (Composition, Input) team
team-Reach
Issue for the Reach team
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) toDesktopChildSiteBridge
. 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:
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.The text was updated successfully, but these errors were encountered: