-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Adding a "Skip to Content" Link #7220
Comments
Hey @canerakdas , I would like to work on this issue, could you please guide regarding this issue that what Also, this button would be like creating a button to be clicked by the user (using mouse) or it is like if the user presses (let's say) |
I think it would skip to content.
No, it's not aimed to users using a mouse, it should not be visible unless it has focus. You can read about in the linked spec, or you can get inspiration from an existing implementation (e.g. the GitHub one is arguably easy to grasp) |
Thanks @aduh95 , got it now 👍 |
Like on GitHub web UI, it should not be visible by default, and, on focus, it should appear on the extreme top-left – as you can see on the spec, it's not the only possible implementation, but in my experience it's the most usual one. It should not disturb anything on the page, in fact if it's correctly implemented users using a mouse should not be able to tell there's a new button, it's aimed for screen-readers and/or keyboard users. |
Yes, got it 👍 I'll keep it on the top-left of the page and by default it'll be hidden, unless the user presses - |
Hey @canerakdas , I've created a PR for this issue, could you please have a look at it? |
Enter your suggestions in details:
For users navigating only with a keyboard or using screen readers, reaching the main content on pages like the "Learn" section can be challenging. Currently, they need to bypass links in the navigation and progression sidebars before accessing the main page content, which creates a barrier to efficient navigation
To enhance accessibility, we could add a "Skip to Content" link, enabling users to jump directly to the primary content area.
Example Implementation: Carbon Design System, GitHub
WCAG Reference: WCAG 2.0 Technique G1
The text was updated successfully, but these errors were encountered: