Skip to content
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

Open
canerakdas opened this issue Nov 12, 2024 · 6 comments · May be fixed by #7390
Open

Adding a "Skip to Content" Link #7220

canerakdas opened this issue Nov 12, 2024 · 6 comments · May be fixed by #7390
Labels
accessibility Issues concerning accessibility good first issue Issues for newcomers

Comments

@canerakdas
Copy link
Member

canerakdas commented Nov 12, 2024

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

@canerakdas canerakdas added accessibility Issues concerning accessibility good first issue Issues for newcomers labels Nov 12, 2024
@yaten2302
Copy link

Hey @canerakdas , I would like to work on this issue, could you please guide regarding this issue that what Skip to Content button would exactly do? Like, here on the content page

Image

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) Tab (on windows), then the user would be redirected to the main content page?

@aduh95
Copy link
Contributor

aduh95 commented Jan 6, 2025

what Skip to Content button would exactly do?

I think it would skip to content.

this button would be like creating a button to be clicked by the user (using mouse)

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)

@yaten2302
Copy link

Thanks @aduh95 , got it now 👍
Just wanted to ask that should this button be present on the extreme right-bottom side of the page?(since, it'll not disturb other buttons or elements present on the page), WDYT?

@aduh95
Copy link
Contributor

aduh95 commented Jan 6, 2025

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.

@yaten2302
Copy link

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 - tab (for windows)

@yaten2302 yaten2302 linked a pull request Jan 7, 2025 that will close this issue
5 tasks
@yaten2302
Copy link

Hey @canerakdas , I've created a PR for this issue, could you please have a look at it?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues concerning accessibility good first issue Issues for newcomers
Projects
None yet
3 participants