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

bug: submenu links are not accessible from keyboard #139

Closed
2 of 5 tasks
PaulineNemchak opened this issue Apr 30, 2024 · 3 comments
Closed
2 of 5 tasks

bug: submenu links are not accessible from keyboard #139

PaulineNemchak opened this issue Apr 30, 2024 · 3 comments

Comments

@PaulineNemchak
Copy link
Contributor

Bug Report

Describe the bug

Submenu links are not accessible from keyboard and misses aria attributes

To Reproduce

Steps to reproduce the behavior:

  1. Go to the website
  2. Navigate with your keyboard using tab key
  3. Focus on the menu item and try to open the submenu

Expected behavior

It should be possible to open the submenu with your keyboard e.g. using the arrow down key
w3 tutorial:
another w3 tutorial

Screenshots

Screenshot 2024-04-30 at 15 13 02

Desktop (please complete the following information):

  • OS: macOS
  • Browser tested in chrome, suppose any
  • Version 124

Reproducibility

  • The bug is reproducible consistently.
  • The bug is sporadic or occurs randomly.

Impact

  • The bug affects critical functionality.
  • The bug affects minor functionality.
  • The bug is a cosmetic issue.

Additional context

Add any other context about the problem here.

Related Issues/PRs

If you know of any related issues or pull requests, link them here.

Proposed Solution (optional)

If you have any ideas on how to fix the bug or potential areas to investigate, suggest them here.

Your Contribution (optional)

If you're able and willing to contribute a fix, mention it here.

@lilyndk
Copy link
Collaborator

lilyndk commented May 1, 2024

Closing this as a duplicate of #115

@lilyndk lilyndk closed this as completed May 1, 2024
@PaulineNemchak
Copy link
Contributor Author

Sorry @lilyndk I've missed that

@lilyndk
Copy link
Collaborator

lilyndk commented May 2, 2024

No worries @PaulineNemchak :) It was also confusing how it was moved under a different ticket and now re-opened again...

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