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

Improve the tutorial table of contents accessibility #4673

Closed
jpaquim opened this issue Apr 14, 2020 · 3 comments
Closed

Improve the tutorial table of contents accessibility #4673

jpaquim opened this issue Apr 14, 2020 · 3 comments

Comments

@jpaquim
Copy link

jpaquim commented Apr 14, 2020

Is your feature request related to a problem? Please describe.
I feel a bit frustrated sometimes when trying o open another section of the tutorial in another tab, and invariably fail due to the table of contents being a <select>.

Describe the solution you'd like
It would be more intuitive and useful if it was possible to open a new section in a new tab from the right click menu, or by Cmd+clicking (so I guess just behaving like a regular <a> element).

How about replacing the single selection table of contents with a more accessible one with anchor elements?

Describe alternatives you've considered
It seems that this section is responsible for defining the DOM for this part of the page. https://github.com/sveltejs/svelte/blob/master/site/src/routes/tutorial/%5Bslug%5D/_TableOfContents.svelte#L80

I imagine that the solution would be along the lines of replacing it with the usual <nav>, <ol>, <li>, and <a> elements. Or maybe just add wrapper <a> elements in the TOC entries themselves.

How important is this feature to you?
It's a nice to have, but it doesn't really impact my daily work significantly.

I wouldn't mind tackling this issue, but I wanted to check if I was the only one slightly frustrated by this behavior.

@pushkine
Copy link
Contributor

I remember I didn't find it great when I did it months ago
the workaround is to go to the page anyway then cmd click the history.back button instead

@stale
Copy link

stale bot commented Dec 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-bot label Dec 24, 2021
@dummdidumm
Copy link
Member

Closing as outdated, we have a new omnisite in a different repo now, and there's work planned to make it more navigateable

@dummdidumm dummdidumm closed this as not planned Won't fix, can't repro, duplicate, stale Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants