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
[Redesign] Focus search element immediately when landing on the front page #4458
Comments
We need to check about the accessibility guidance of this (/cc @MicrosoftSam), but I like the idea. |
If not on the homepage, it really should still happen on |
I think a better way to solve this is to provide a mechanism to bypass blocks, since you have content that's repeated on multiple pages (each page has a search box, each page has the menu, and each page has the content section). This is the "hidden menu" concept we've previously talked about. A menu when focused provides the user the ability to "Jump to Search", or "Jump to Content", or "Change language", etc. So I think focusing the search box should only be done on pages where that is the likely first intractable element for a user. MAS Standard in question here: WCAG 2.0 2.4.1 Bypass Blocks |
Any chance a "focus the element when user starts typing" could be added within those rules? |
^^ That's what github does. You'd want to make sure you'd on no activeElement in your handler, but that would work. |
Fixed and deployed to https://preview.nuget.org/. |
It would be nice for the search box to be focused immediately when visiting the new NuGet.org website, much like on NuGet.org vCurrent. This would mean people are able to just start typing, hit enter, find results. No need to move the mouse and click the search box.
The text was updated successfully, but these errors were encountered: