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
OnkarRuikar opened this issue
Mar 17, 2022
· 1 comment
· May be fixed by #11233
Labels
♿ a11yAn MDN Web Docs accessible by everyone🐛 bugSomething isn't working, or isn't working as expectedhas PRIssues that already have a PRidlep4Not urgent, only if time allows🔎 searchSearch featureuxmake the user experience awesome
The Search box is not easy to use using only keyboard and without mouse.
Consider a scenario where a user is on MDN home page and trying to search Request interface using "request" word.
After, typing search text and hitting Enter key, the first suggestion is forced on to the user. Have to hit down arrow key 5 times to get to the option which performs full search. In case of GitHub and Google searches, they give priority to the user entered text.
On home page, some search suggestions go out of the viewport. Even after hitting down arrow key they don't come into view.
Without scrolling down(i.e. involving mouse) we can't see the last full-search option. This makes above point 1) more painful.
Suggestions do not get cycled on pressing Tab key like they do on google search.
On blur, by clicking outside, suggestions are not hidden.
Suggestions are sorted by "popularity". While actual search results are sorted by "best". User may get confused by seeing different outcomes. On home page:
Results page:
On home page there are two search boxes. One in top right corner and a giant one in the center of the page.
Type "request" in the search box that is at the center.
Hit Enter key. It opens page for '400 Bad Request' and not search results page.
Issue 2:
Set browser zoom to 0.
On MDN home page type "request" in center search box.
Six suggestions are listed below the search box.
If your monitor resolution is not high(mine is 1366x768) some suggestions will go off the viewport.
Without using mouse, to scroll down, try to select option "Site search for request".
There is no way to know which option we are on.
Issue 3:
On MDN home page in center search box type "request".
Try to cycle through suggestions using Tab key, like we can do on google search.
Issue 4:
Type "request" in search box.
Click outside the search box. The suggestions are not hidden.
Issue 5:
On home page search for text "request".
And choose "Site search" suggestion.
Notice the difference between suggestions and results sort order.
Expected behavior
1. Should be able to type search text and hit Enter/Return key in order to see full search results.
2. When the input box gets focused by tab or click, one of the following needs to happen:
- make it touch top border of the viewport. We can use scrollIntoView() for this.
- Or make highlighted option text appear in the input box like Google.com does.
3. By pressing tab cycle through suggestions till user hits enter or escape keys. This will bring options into view automatically. And will solve the issue 2).
4. On blur, by clicking outside the suggestion box, hide it.
5. Unless this has been done intentionally, make search results sort by "popularity" by default.
6. Get rid of or hide top right search box on the home page.
schalkneethling
added
♿ a11y
An MDN Web Docs accessible by everyone
and removed
needs triage
Triage needed by staff and/or partners. Automatically applied when an issue is opened.
labels
Mar 17, 2022
caugner
added
p4
Not urgent, only if time allows
ux
make the user experience awesome
accepting PR
We invite you to open a PR to resolve this issue.
labels
Nov 15, 2022
♿ a11yAn MDN Web Docs accessible by everyone🐛 bugSomething isn't working, or isn't working as expectedhas PRIssues that already have a PRidlep4Not urgent, only if time allows🔎 searchSearch featureuxmake the user experience awesome
Summary
The Search box is not easy to use using only keyboard and without mouse.
Consider a scenario where a user is on MDN home page and trying to search Request interface using "request" word.
After, typing search text and hitting
Enter
key, the first suggestion is forced on to the user. Have to hitdown arrow
key 5 times to get to the option which performs full search. In case of GitHub and Google searches, they give priority to the user entered text.On home page, some search suggestions go out of the viewport. Even after hitting down arrow key they don't come into view.
Without scrolling down(i.e. involving mouse) we can't see the last full-search option. This makes above point 1) more painful.
Suggestions do not get cycled on pressing
Tab
key like they do on google search.On blur, by clicking outside, suggestions are not hidden.
Suggestions are sorted by "popularity". While actual search results are sorted by "best". User may get confused by seeing different outcomes.
On home page:
Results page:
URL
https://developer.mozilla.org/en-US/
Reproduction steps
Issue 1:
Enter
key. It opens page for '400 Bad Request' and not search results page.Issue 2:
Issue 3:
Tab
key, like we can do on google search.Issue 4:
Issue 5:
Expected behavior
- make it touch top border of the viewport. We can use scrollIntoView() for this.
- Or make highlighted option text appear in the input box like Google.com does.
enter
orescape
keys. This will bring options into view automatically. And will solve the issue 2).Actual behavior
As mentioned in summary section.
Device
Desktop
Browser
Chrome
Browser version
Stable
Operating system
Windows
Screenshot
No response
Anything else?
No response
Validations
The text was updated successfully, but these errors were encountered: