Links using Next/Link are bypassing the skip-link component that is used for accessibility for keyboard users.

If we use regular a tags, the first Tab hit on the keyboard will focus on the skip-link component but if we are using Next/Link, then it will not focus on that, instead, it will focus on the second element, which in most cases is the logo.

This bug appears when the page is cached. So if you open incognito mode, all links will usually work for the first time as expected but when visited again, they will fail to work.

So basically, this will skip the first element on the next page that loads when I hit Tab,

<Link href="/search">
  <a aria-label="Search Page" className="header__search">
    Search
  </a>
</Link>

but this will as expected:

<a href="/search" aria-label="Search Page" className="header__search">
  Search
</a>

Expected Behavior

Whenever we change the page, the first Tab click should trigger a skip-link if it is available there.

To Reproduce

• Go to https://vercel.com/home
• Click on Integrations on the navigation bar.
• Hit the Tab key on the keyboard.

Any help is appreciated.