You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
GridSplitter accessibility issue reported by Accessibility Insights #3399
The GridSplitter uses a symbol for the handle icon ("\xE784" & "\xE76F") and this is exposed to the automation tools. However, this is not an accessible value and so fails basic accessibility testing.
Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
Controls should not fail basic accessibility tests
Screenshots
This is what the tool reports. Note that the icon (from 'Segoe MDL2 Assets') cannot be rendered by accessibility software.
Environment
NuGet Package(s): Microsoft.Toolkit.Uwp.UI.Controls
Package Version(s): 6.1.0
Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [x] May 2020 Update (19041)
- [ ] Insider Build (build number: )
App min and target version:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [x] May 2019 Update (18362)
- [x] May 2020 Update (19041)
- [ ] Insider Build (xxxxx)
Device form factor:
- [x] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT
Visual Studio
- [ ] 2017 (version: )
- [x] 2019 (version: 16.6.4)
- [ ] 2019 Preview (version: )
Additional context
The fix is to expose an appropriate automation name/description for this element.
There may be other controls with accessibility issues and I haven't looked at them (yet) but this was found while testing the accessibility of apps generated by Windows Template Studio (X-Ref: microsoft/TemplateStudio#3723)
Thanks @mrlacey, I'm planning on my stream tomorrow afternoon to attempt the initial refactor of the GridSplitter (based on my ContentSizer control), but I believe the content symbol will work similarly/the same; so I imagine it has the same issue?
Are we just missing an automation property name somewhere?
Activity
Kyaa-dost commentedon Jul 24, 2020
Thanks, @mrlacey for the find! Are you already working on a fix?
mrlacey commentedon Jul 24, 2020
can do ;)
michael-hawker commentedon Jul 27, 2020
Thanks @mrlacey, I'm planning on my stream tomorrow afternoon to attempt the initial refactor of the GridSplitter (based on my ContentSizer control), but I believe the content symbol will work similarly/the same; so I imagine it has the same issue?
Are we just missing an automation property name somewhere?
[-]GridSplitter[/-][+]GridSplitter accessibility issue reported by Accessibility Insights[/+]mrlacey commentedon Jul 28, 2020
what a dreadful original title - fixed. sorry.
Don't have the GridSplitterHandle show in UIA tree
GridSplitter accessibility issue fix (#3401)
2 remaining items
azchohfi commentedon Aug 12, 2020
Closing, as this is now shipped:
https://www.nuget.org/packages/Microsoft.Toolkit.Uwp.Notifications/6.1.1
michael-hawker commentedon Feb 12, 2021
@azchohfi I don't think this ever got merged back to main. Going to re-open so we can cherry-pick the commit.