You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
notice: The previous and next buttons on a given docs page have keyboard shortcuts of Alt-P and Alt-N, but this information is only communicated programmatically (e.g., to screenreader user).
Expected behavior
Would be good to let sighted keyboard user know this is available also, in plain text on the page / visible labels in the buttons. Note that these shortcuts seem to be fine in and of themselves, can’t find a common function that uses these shortcuts already in a given OS/browser.
Desktop:
This issue is not OS or browser specific, but for tracking purposes, testing was done on Win11, in Edge Version 114.0.1823.58 (Official build) (64-bit), and the screenreader in use was the common 3rd party screenreader NVDA (http://www.nvaccess.org).
Smartphone:
This issue is not device, OS, or browser specific.
Additional context
This is an accessibility issue, please annotate this bug with the 'accessibility' label.
The text was updated successfully, but these errors were encountered:
Describe the bug
Keyboard shortcuts are communicated to screenreader user but not sighted user
To Reproduce
Steps to reproduce the behavior:
notice: The previous and next buttons on a given docs page have keyboard shortcuts of Alt-P and Alt-N, but this information is only communicated programmatically (e.g., to screenreader user).
Expected behavior
Would be good to let sighted keyboard user know this is available also, in plain text on the page / visible labels in the buttons. Note that these shortcuts seem to be fine in and of themselves, can’t find a common function that uses these shortcuts already in a given OS/browser.
Desktop:
This issue is not OS or browser specific, but for tracking purposes, testing was done on Win11, in Edge Version 114.0.1823.58 (Official build) (64-bit), and the screenreader in use was the common 3rd party screenreader NVDA (http://www.nvaccess.org).
Smartphone:
This issue is not device, OS, or browser specific.
Additional context
This is an accessibility issue, please annotate this bug with the 'accessibility' label.
The text was updated successfully, but these errors were encountered: