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

A11y_.NETWPF_ExpenseItIntro_ExpenseReportFor_AI4D: The Name property of a focusable element must not be null. #5045

Closed
Blessymanna opened this issue Aug 9, 2021 · 1 comment
Assignees

Comments

@Blessymanna
Copy link

Blessymanna commented Aug 9, 2021

The following accessibility issue needs investigation.
GitHubTags:#A11yMAS;#A11ySev2;#A11yTCS;#A11yWCAG;#DesktopApp;#WCAG4.1.2;#DesktopApp;#Win10;#BM-.NetCore(WPF)-Win32-July2021;#.NET Core;#Benchmark;#A11yAuto;
App: ExpenseIt9

Environment Details:
Application Name: .NET Core WPF
Microsoft .NET Core SDK Version 6.0.100-rc.1.21380.2
Windows Version: Windows10

Repro Steps:

  1. Launch VS 2019 Int Preview
  2. Navigate to Getting started and right click on the Expense it intro and navigate to build
  3. Then right click on Expense it Intro then Click on Debug-->Start New Instance.
  4. Navigate to Names list and select any name and navigate to View.
  5. Verify all the elements of 'Expense Report for' screen are accessible and MAS Compliant

Element path: menu ''

Issue Details: The Name property of a focusable element must not be null.

How To Fix: Provide a UI Automation Name property that concisely identifies the element.

This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights.

@Blessymanna Blessymanna changed the title A11y_ExpenseItIntro_ExpenseReportFor_AI4D: The Name property of a focusable element must not be null. A11y_.NETWPF_ExpenseItIntro_ExpenseReportFor_AI4D: The Name property of a focusable element must not be null. Aug 9, 2021
@anjali-wpf anjali-wpf self-assigned this Aug 16, 2021
@ryalanms
Copy link
Member

This is by design. The control is not owned by WPF and does not set AutomationName.

@ghost ghost locked as resolved and limited conversation to collaborators Apr 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants