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
Press tab key to reach the 'stable read the docs' control present in the bottom right corner of the page and activate it using Enter key.
Press tab key to navigate to search docs edit field. Search dialog will appear.
Verify with tab key/arrow keys, whether "Read the Docs' control present in the search dialog is keyboard accessible or not.
Expected Result
'Read documentation' control present in the search dialog in should be accessible with the keyboard.
EX: While navigating with the keyboard tab key, the keyboard focus should move to 'Read the Docs' control.
Actual Result
'Read the Docs' control present in the search dialog is not keyboard accessible.
Observation:
While navigating with the keyboard tab key, the keyboard focus is not moving to 'Read documentation' control.
'Read the Docs' control is accessible and operable with the mouse.
The text was updated successfully, but these errors were encountered:
humitos
transferred this issue from readthedocs/readthedocs.org
Apr 10, 2025
humitos
changed the title
'Read the Docs' Control in Search Dialog is Not Keyboard Accessible on Windows.
Search: not keyboard accessible (on windows)
Apr 10, 2025
Details
Repro steps:
Expected Result
'Read documentation' control present in the search dialog in should be accessible with the keyboard.
EX: While navigating with the keyboard tab key, the keyboard focus should move to 'Read the Docs' control.
Actual Result
'Read the Docs' control present in the search dialog is not keyboard accessible.
Observation:
While navigating with the keyboard tab key, the keyboard focus is not moving to 'Read documentation' control.
'Read the Docs' control is accessible and operable with the mouse.
Read.the.Docs.Control.in.Search.Dialog.is.Not.Keyboard.Accessible.on.Windows.2.mp4
The text was updated successfully, but these errors were encountered: