Skip to content
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

GridSplitter accessibility issue reported by Accessibility Insights #3399

Description

@mrlacey

Describe the bug

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:

Steps to Reproduce

Steps to reproduce the behavior:

  1. Add a GridSplittter to a page and run the app
  2. Analyze with Accessibility Insights for Windows
  3. See error

Expected behavior

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.

partial screenshot showing error report

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)

Activity

  1. added
    bug 🐛An unexpected issue that highlights incorrect behavior
    on Jul 24, 2020
  2. Kyaa-dost commented on Jul 24, 2020

    @Kyaa-dost
    Contributor

    Thanks, @mrlacey for the find! Are you already working on a fix?

  3. mrlacey commented on Jul 24, 2020

    @mrlacey
    ContributorAuthor

    Thanks, @mrlacey for the find! Are you already working on a fix?

    can do ;)

  4. michael-hawker commented on Jul 27, 2020

    @michael-hawker
    Member

    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?

  5. added this to the 7.0 milestone on Jul 27, 2020
  6. changed the title [-]GridSplitter[/-] [+]GridSplitter accessibility issue reported by Accessibility Insights[/+] on Jul 28, 2020
  7. mrlacey commented on Jul 28, 2020

    @mrlacey
    ContributorAuthor

    what a dreadful original title - fixed. sorry.

  8. ghost added a commit that references this issue on Aug 11, 2020
    2d41859
  9. 2 remaining items

  10. azchohfi commented on Aug 12, 2020

    @azchohfi
    Contributor
  11. ghost locked as resolved and limited conversation to collaborators on Oct 12, 2020
  12. michael-hawker commented on Feb 12, 2021

    @michael-hawker
    Member

    @azchohfi I don't think this ever got merged back to main. Going to re-open so we can cherry-pick the commit.

  13. removed their assignment
    on Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions