Recently, someone posted on LinkedIn that skip links are often broken because their target elements are missing a `tabindex` attribute. I was really surprised to see that because I thought that was an issue of the past. That's why I decided to test it.

https://matuzo.at/blog/2026/skip-links-tabindex?d=0503

Update: Thanks for the feedback. I've added more tests and updated the title.

Your skip link targets may not need tabindex=-1 to work properly - Manuel Matuzovic

I'm a frontend developer in Graz, specialized in HTML, accessibility, and CSS layout and architecture.

Manuel Matuzovic

@matuzo Is that what they are called today, "skip links"? Whatever happened to "document fragment"?

Guess I've learned something new today.

@dreddie "skip links" are a specific use of document fragment links, to allow keyboard or screen reader users to skip over large navigation menus & get straight to the content without having to tab-tab-tab through every other link. But they only work for that purpose if the keyboard focus (not just the scroll position) actually moves to the target!

@matuzo

@AmeliaBR @matuzo It sounds to me that it is a band-aid / workaround for something more fundamental to the page. If you page is designed in such a way that large sections can be skipped without affecting the content, then why are these sections on the page in the first place? Just remove them instead. And I sincerly hope that by using the <main> element any assistive technologies have standard hotkeys to jump to that content.

A better way imo would be to provide for example alternate display modes on the page. Many browsers have a Reader Mode built in. The page or site should also contain things like RSS feeds.

@dreddie @AmeliaBR @matuzo Hi! Thanks for bringing this up. Accessibility people have never thought about this. /s

Sorry. This is for skipping the navigation when someone uses the keyboard but no assistive technologies. Yes, browsers could add that functionality natively, but they give a fuck. Thanks for coming to my TED talk on “why sometimes accessibility accommodations need to be made while they could solved otherwise, but that is just not done due to ableism in the web technology space”.

@yatil If your page navigation is in the way of keyboard users, you sould redesign the page so the navigation is NOT in the way of keyboard users.

If there is a large 'table of contents' before the main content, maybe move the TOC to the side of the page. Instead of band-aid solutions like a skip-link.

@dreddie Good idea to have keyboard users navigate through all of the content to get to the table of contents. Oh, what is that? They need a skip link for the content then? Yeah.

(Also a table of contents is also skip links. 🤷‍♂️)

It’s okay to not know or not fully understand, but it’s a bit insulting to give advice to people, who work on these problems for decades. We have thought long and hard about this, skip links are practical, flexible, and easy to implement.