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

[Screen Reader - Windows Powershell]: In scan mode user is not able to activate dropdown as combined focus is navigating to 'New tab' split button. #8478

Closed
Chandresh1007 opened this issue Dec 3, 2020 · 4 comments
Assignees
Labels
A11yCO Accessibility tracking A11ySev2 Accessibility tracking A11yWCAG Accessibility tracking Area-Accessibility Issues related to accessibility HCL-E+D Accessibility tracking HCL-WindowsTerminal Accessibility tracking Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-2 A description (P2) Product-Terminal The new Windows Terminal.

Comments

@Chandresh1007
Copy link

User Experience:
If any application does not expose information and mechanisms necessary to track focus, text insertion point, and selection attributes (e.g. whether text has been selected for copy/paste) of user interface components, it would be difficult for the platforms that provide Accessibility APIs, and would in turn affect the screen reader dependent users to determine the focus

Test Environment:
OS: Win 10 2004 Build (20262.1010)
App: Windows Terminal
App version: 1.4.3243.0

Repro Steps:

  1. Open Windows terminal app.
  2. Launch Narrator.
  3. Turn on the scan mode of the narrator using "Caps+Space".
  4. Now navigate using Up/Down arrow key to New tab split button.
  5. Now try to open the flyout/dropdown using keyboard "Alt down" key.
  6. Observe the issue.

Actual Result:
In scan mode user is not able to activate dropdown as combined focus is navigating to 'New tab' split button.

Expected Result:
In scan mode user should be able to activate dropdown by any keyboard key defined which should be announced by the narrator.
Or, Separate focus should navigate to 'New tab' button and dropdown button.

Note: NVDA browse mode is not working.

MAS Reference:
MAS4.2.10
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7Bb24201d1-2276-4471-8183-e1e5353031ad%7D&cid=83352b15-6eaa-4fc1-bd5a-2d857a532986

UI of new tab Split button

MAS4.2.10_Split button_focus navigates one time_not able to open flyout.zip

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 3, 2020
@Chandresh1007 Chandresh1007 added HCL-E+D Accessibility tracking Product-Terminal The new Windows Terminal. labels Dec 3, 2020
@zadjii-msft
Copy link
Member

I could have sworn we already had this bug filed on us, and it got move upstream to the WinUI repo...

@zadjii-msft zadjii-msft added the Area-Accessibility Issues related to accessibility label Dec 3, 2020
@carlos-zamora
Copy link
Member

A few things:

  1. SplitButton's "More Options" button is not keyboard accessible microsoft-ui-xaml#1238 was filed on XAML. They're considering how to get around this.
  2. I'll copy this comment since it has some good info:
    • Alt+Down opens the split options, consistent with the Office control set. With narrator, the secondary action should open the overflow.
  3. We have an openNewTabDropdown action.
    • use Ctrl+Shift+Space to open the dropdown (only works when focused on shell)
    • the user can introduce their own keybinding for openNewTabDropdown to open it with their custom keybinding

@Chandresh1007 Is this sufficient to close this issue?

@cinnamon-msft cinnamon-msft added the Priority-2 A description (P2) label Dec 3, 2020
@DHowett DHowett added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Dec 4, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Dec 4, 2020
@Chandresh1007 Chandresh1007 added A11yWCAG Accessibility tracking HCL-WindowsConsole Accessibility tracking HCL-WindowsTerminal Accessibility tracking labels Dec 7, 2020
@Chandresh1007
Copy link
Author

@carlos-zamora Pressing 'Alt+Down' to open the flyout of the split button the focus is navigating to the tab and then by pressing 'Alt+Down' once more, the flyout is getting open. Here, the flyout should get open by pressing 'Alt+Down' key once.
Also it would be good, if narrator announces the information that press 'Alt+down' to open the flyout.
Refer attachment
Terminal_Split button_scan mode_flyout getting open in 2nd time.zip

@Chandresh1007
Copy link
Author

Closing the bug as it is External to XAML team:
WinUI 2 team has accepted this as a XAML bug.
plitButton's "More Options" button is not keyboard accessible · Issue #1238 · microsoft/microsoft-ui-xaml (github.com)

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Feb 23, 2021
@awalia13 awalia13 added the A11yCO Accessibility tracking label Mar 10, 2021
@Priyanka-Chauhan123 Priyanka-Chauhan123 added the A11ySev2 Accessibility tracking label Jun 10, 2021
@Priyanka-Chauhan123 Priyanka-Chauhan123 removed the HCL-WindowsConsole Accessibility tracking label Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11yCO Accessibility tracking A11ySev2 Accessibility tracking A11yWCAG Accessibility tracking Area-Accessibility Issues related to accessibility HCL-E+D Accessibility tracking HCL-WindowsTerminal Accessibility tracking Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-2 A description (P2) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

7 participants