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

When we press "Esc" key to close the dropdown the keyboard focus is moving back to "visible" instead of dropdown.: A11y_.NET CoreWinforms_Remaining_Controls_Testing_Keyboard #12222

Closed
kupatkar99 opened this issue Sep 25, 2024 · 1 comment

Comments

@kupatkar99
Copy link

.NET version

dotnet-sdk-9.0.100-rc.1.24422.10-win-x64

Did it work in .NET Framework?

Yes

Did it work in any of the earlier releases of .NET Core or .NET 5+?

No response

Issue description

GitHub Tags:

#A11yMAS; #A11yTCS; #A11ySev3; #BM_.NET Core[Winforms]_Win32_May2024; #.NETCore; #WCAG2.4.7; #DesktopApp; #Win11; #FTP; #Keyboard;

Environment Details:

App name: .NET Core Winforms
Window Version: Win 11 Enterprise
OS Build: 22631.4169

Steps to reproduce

  1. Launch the "Accessibility core app".
  2. Main Form screen would appear.
  3. TAB to "Remaining_Controls_Testing" and hit ENTER key.
  4. Remaining Controls window will get open. TAB till "Category" button and press enter.
  5. Tab till dropdown button and select any option from the list.
  6. Observe that When we press "Esc" key to close the dropdown the keyboard focus is moving back to "parent dropdown control" or not.

Actual Result:

When we press "Esc" key to close the dropdown the keyboard focus is moving back to "visible" instead it should remain on dropdown it self.

Expected Result:

When we press "Esc" key to close the dropdown the keyboard focus should return to it's parent control i.e. "dropdown".

User Impact:

Keyboard users will face difficulties to navigate to the parent control once the pop-up is collapsed as keyboard focus is not returning automatically to it's parent control.

Attachment:

winform.mp4
@kupatkar99 kupatkar99 added the untriaged The team needs to look at this issue in the next triage label Sep 25, 2024
@JeremyKuhne
Copy link
Member

Sev3.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged The team needs to look at this issue in the next triage label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants