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

Narrator fails to read the name for all the editable number boxes in "Number Box" page. #3505

Closed
YuliKl opened this issue Oct 28, 2020 · 4 comments · Fixed by #3775
Closed
Labels
A11yMAS A11ySev3 accessibility Narrator, keyboarding, UIA, etc area-NumberBox NumberBox Control help wanted Issue ideal for external contributors team-Controls Issue for the Controls team

Comments

@YuliKl
Copy link

YuliKl commented Oct 28, 2020

Steps to reproduce the bug

Pre-requisite:

  • Turn on Narrator.

Steps to reproduce the behavior:

  1. Launch XAML Controls Gallery.
  2. Activate "number box" from home page.
  3. Navigate to all the editable number boxes in the page.
  4. Observe narrator's description for the same.

Expected behavior

Narrator should read unique name, role for the all the respective number boxes.

Screenshots

image

image

Version Info

Xaml Controls Gallery version: 1.2.13.0

Additional context

Copied from internal bug

@YuliKl YuliKl added accessibility Narrator, keyboarding, UIA, etc area-NumberBox NumberBox Control team-Controls Issue for the Controls team A11yMAS labels Oct 28, 2020
@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Oct 28, 2020
@YuliKl
Copy link
Author

YuliKl commented Oct 28, 2020

@SavoySchuler , there was a question for you in the original issue:
What is the expected behavior here ? When Narrator lands on the NumberBox it does not read anything. However, there are two more stops, one for the header and another for the TextBox where the expression is present and they are read out. Should NumberBox have a default automation name if one is not provided ? I think providing an automation name for NumberBox will fix the issue.

@robloo
Copy link
Contributor

robloo commented Oct 28, 2020

Another duplicate of #2951 I believe.

@marcelwgn
Copy link
Contributor

This is not exactly the same as #2951 as textbox controls also provide a UIA name even if AutomationProperties.Nam is not set (e.g. by taking the header into account). This might be related to or a duplicate of #1853 .

@StephenLPeters StephenLPeters added help wanted Issue ideal for external contributors and removed needs-triage Issue needs to be triaged by the area owners labels Oct 28, 2020
@marcelwgn
Copy link
Contributor

I would like to look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11yMAS A11ySev3 accessibility Narrator, keyboarding, UIA, etc area-NumberBox NumberBox Control help wanted Issue ideal for external contributors team-Controls Issue for the Controls team
Projects
None yet
5 participants