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

[Accessibility] Narrator does not read the status message as row added after click on Add New button of BindingNavigator #3596

Closed
Amy-Li03 opened this issue Jul 17, 2020 · 4 comments
Assignees
Labels
a11yMAS High Priority - Accessibility violation of Microsoft Accessibility Standards tenet-accessibility MAS violation, UIA issue; problems with accessibility standards won't fix: by design Behaviour is by design

Comments

@Amy-Li03
Copy link
Contributor

Amy-Li03 commented Jul 17, 2020

  • .NET Core Version:
    .NET SDK 5.0.100-preview.8.20363.2

  • Have you experienced this same bug with .NET Framework?:
    Yes

More info:
NVDA tool also can reproduce this issue.

Minimal repro:

  1. Extract the test app, then build and run it.
    CoreApp.zip
  2. Open Narrator tool, navigate to the Add New button of BindingNavigator.
  3. Click on Add New button (click by mouse or through keyboard), then a row will be added.
    repro

Actual behavior:

  1. Narrator does not provide instruction that Add New button refers to what control to be added.

  2. While clicking on Add New button through Caps + Enter key, Narrator will not focus on the new added row, so Narrator does not read the status message as row added.
    Narrator1

  3. While clicking on Add New button by mouse, Narrator will focus on the new added row, so Narrator will read the status message as row added.
    Narrator2

Expected behavior:

  1. Narrator should provide information that Add new button refers to what control should be added.
  2. While clicking on Add New button through Caps + Enter key, Narrator should read the status message as row added after click on "Add New" button.
@Amy-Li03 Amy-Li03 added the tenet-accessibility MAS violation, UIA issue; problems with accessibility standards label Jul 17, 2020
@merriemcgaw merriemcgaw added the a11yMAS High Priority - Accessibility violation of Microsoft Accessibility Standards label Jul 17, 2020
@merriemcgaw merriemcgaw added this to the 5.0 milestone Jul 17, 2020
@merriemcgaw
Copy link
Member

You may be able to do this directly in the sample app, though if we can get it into the DGV it would be pretty cool.

@SergeySmirnov-Akvelon
Copy link
Contributor

Hi @Amy-Li03. I have investigated this issue and found that this is behavior by design. After clicking on ToolStripButton, ToolStrip return focus to previous control that had focus. If user uses keyboard navigation then focus will return on ToolStrip control. As workaround i suggest to add handler with dataGridView.Focus() code on "Click" event of "Add new" button:

bindingNavigatorAddNewItem.Click += (s, e) =>
{
    dataGridView1.Focus();
};

This code returns focus to dataGridView.

In score of #3560 we fixed issue with supporting of AccessibleName for ToolStrip items. As result user can use AccessibleName or ToolStripText properties for providing required information to Narrator (for example: what control should be added)

@Amy-Li03
Copy link
Contributor Author

@SergeySmirnov-Akvelon tried this workaround mentioned above, Narrator can read the status message as row added when clicking on Add New button through Caps + Enter key.

@SergeySmirnov-Akvelon
Copy link
Contributor

This behavior is by design and the suggested workaround works for @Amy-Li03. Thus it closed as solved.

@SergeySmirnov-Akvelon SergeySmirnov-Akvelon added the won't fix: by design Behaviour is by design label Sep 17, 2020
@RussKie RussKie removed this from the 6.0 Preview1 milestone Sep 24, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a11yMAS High Priority - Accessibility violation of Microsoft Accessibility Standards tenet-accessibility MAS violation, UIA issue; problems with accessibility standards won't fix: by design Behaviour is by design
Projects
None yet
Development

No branches or pull requests

5 participants