Provide permalinks for headings

[mcking65]

would be nice if we provide anchor links in the headers, There's no longer # in headers which I can click and get the link of the section.

For example in this page
https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface
There is no way to link to the roving tabindex pattern directly.

Fun fact: although attaching the old hash does work /#kbd_roving_tabindex

Originally posted by @anuraghazra in w3c/aria-practices#2362 (comment)

[mcking65]

The TR Note offered permalinks for all headings, so the fact that we no longer have them is a functional regression.

@shawna-slh, would you prefer this be addressed by a template feature? Or, would you prefer that we make it an APG feature?

[shawna-slh]

Users can get links to a specific section by clicking in the Page Contents list and copying the URI. That's not as easy as a permalink UI, though.

I would prefer this be addressed site-wide -- WAI-site-wide, if not W3C-site-wide.

I'm pretty sure that @yatil developed UI for permalinks on WAI website a few years ago; however I can't find it. (I think was on the old tutorials.)

If you can't find that, please use W3C site implementation.

[mcking65]

@shawna-slh wrote:

Users can get links to a specific section by clicking in the Page Contents list and copying the URI.

That only works for level 2. We have several sections where it is valuable to link to level 3 or 4 headings.

I'm pretty sure that @yatil developed UI for permalinks on WAI website a few years ago; however I can't find it. (I think was on the old tutorials.)

If you can't find that, please use W3C site implementation.

So, there is a w3c site implementation we can re-use now? How do we do that?

[yatil]

I don't think the 2014-ish implementation of the tutorial one would stand muster in 2022.

There has been no re-implementation for the redesign as there were other priorities.

There is probably a good way to use the Web Share API: https://developer.mozilla.org/en-US/docs/Web/API/Web_Share_API

[shawna-slh]

Thanks very much for the reply, @yatil !

There has been no re-implementation for the redesign as there were other priorities.

Agree.

[shawna-slh]

@mcking65 said:

That only works for level 2. We have several sections where it is valuable to link to level 3 or 4 headings.

It's easy to include additional heading levels in the Page Contents List if we want.

Without looking at it, I'm guessing that we don't additional levels because the Page Contents would be too long.

However, if others think it is best, I would support that. For example, if you think users will often want to jump down to an H3 or H4.

[shawna-slh]

@mcking65 said:

So, there is a w3c site implementation we can re-use now? How do we do that?

Please ask the W3C Systems Team via e-mail to [email protected]
Please also CC: [email protected]

We might also need to get Steve's help at some point for the WAI site integration.