-
Notifications
You must be signed in to change notification settings - Fork 343
Prototype a "skip to content" hidden button #1285
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
Comments
Hi @anshukaira, just wondering if you are still interested in this? If not, that's completely okay :)) If I don't hear back soon I will ask someone else if they would like to take this on. |
@anshukaira I'm going to reassign this, if you still want to contribute could you ask again over in #1245 and I'll find another issue for you :)) ? @divya144 would you like to have a go with this? Please let me know by commenting below, thanks. |
Hey @patricoferris |
Hi @anshukaira Very sorry to hear that, I hope everything is okay. I'll bump you up on my long stack of things to do and hopefully will create an issue for you some time today or tomorrow. @divya144 how is everything going, do you need any help? No pressure, just want want to make sure you're not blocked on anything :)) |
thanks a lot!!! @patricoferris ^_^ |
@patricoferris I am trying to incorporate the code into the template page. I have not faced any issues till now. Thanks |
@divya144, how is it going? :) Are you still working in this? |
Hi @divya144. Are you still working on this? If not, I would like to take this issue. :) |
When navigating content heavy pages with a keyboard, it would be nice if there was a hidden "skip to content" button that by-passed things like the navbar. This would hopefully improve the user experience for keyboard users.
There is already a lot of guidance online about this:
A good first page to look at is the "up and running" page. Tabbing through this page to get to the main content takes many clicks. The visibility of the focus is being worked on in #1282 so that doesn't need to be addressed here.
This is quite an involved issue since it may require modifying the
templates
of pages. I would suggest:ocaml.org
for a particular page to get the correct functionality.@anshukaira would you like to tackle this issue as part of #1245? Let me know either way below :))
The text was updated successfully, but these errors were encountered: