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][a11y]: Opening the preference modal using keyboard navigation gives no feedback #688

Open
mrleblanc101 opened this issue May 31, 2024 · 2 comments
Labels
bug Something isn't working triage yet to be reviewed

Comments

@mrleblanc101
Copy link

Expected Behavior

When you open the preference modal, the focus should be transfered to the modal so that the screen reader actually says something.

Current Behavior

The focus stays on the button and nothing is said by the screen reader.

Steps to reproduce

  1. Activate VoiceOver,
  2. Tab inside the popup until you focus the "Manage preference" button
  3. Press enter to open the preference modal

Proposed fix or additional info.

No response

Version

3.0.1

On which browser do you see the issue?

Firefox, Chrome, Safari, Microsoft Edge

@mrleblanc101 mrleblanc101 added the bug Something isn't working label May 31, 2024
@github-actions github-actions bot added the triage yet to be reviewed label May 31, 2024
@mrleblanc101 mrleblanc101 changed the title [Bug]: Opening the preference modal using keyboard with VoiceOver gives no feedback [Bug][a11y]: Opening the preference modal using keyboard navigation gives no feedback May 31, 2024
@wittjeff
Copy link

The dialog won't be announced unless focus is moved to it or into it. The most common convention is to put focus on the first focusable item, which is generally the Close button.

When the dialog is closed, focus should return to the triggering element. Currently that happens when you press Esc to dismiss the dialog, but not when you click on the X/close button. I mention this requirement here because you'll need to save the item that has focus (document.activeElement) before setting the focus to the Close button when the Preferences dialog appears.

@mrleblanc101
Copy link
Author

Focusing the first element (the close button) is not a11y compliment. The user will have no way of understanding what is happening as the screen reader will simply read "Close modal" or something similar. The focus should be on the whole banner so that screen reader start ready the content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage yet to be reviewed
Projects
None yet
Development

No branches or pull requests

2 participants