Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

NavigationViewItem tab control type supports invoke pattern with PaneDisplayMode="Top"

See original GitHub issue

Describe the bug

NavigationViewItems in a NavigationView with the PaneDisplayMode set to Top supports the invoke pattern, which is a violation of Section 508 502.3.10 (according to Accessibility Insights for Windows).

Steps to reproduce the bug

Steps to reproduce the behavior:

Create an app with a NavigationView control with PaneDisplayMode set to Top.
Add NavigationViewItems in NavigationView.MenuItems with any content value: (ex: “Menu Item 1”, “Menu Item 2”, “Menu Item 3”.
Run the app with Accessibility Insights.

Expected behavior

Expected: Invoke pattern is not supported.

Screenshots

Version Info

NuGet package version:

[Microsoft.UI.Xaml 2.4.2]

Windows 10 version	Saw the problem?
Insider Build (xxxxx)
November 2019 Update (18363)	Yes
May 2019 Update (18362)
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)

Device form factor	Saw the problem?
Desktop	Yes
Mobile
Xbox
Surface Hub
IoT

Additional context

Issue Analytics

State:
Created 3 years ago
Comments:10 (7 by maintainers)

Top GitHub Comments

2reactions

dbjorgecommented, Jul 1, 2020

Hi! I’m a developer on the Accessibility Insights team. I’ve left an answer to the internal StackOverflow post explaining why Accessibility Insights flags this as a violation and what the user impact of it might be.

1reaction

chingucodingcommented, Jul 2, 2020

Of course @YuliKl , would love to! I will look into this.