fix(a11y): include latest hash and params for skip button

[OrbisK]

fixes #1437

ensures that we keep the query and params on skip link.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 12, 2026 8:03pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 12, 2026 8:03pm
npmx-lunaria	Ignored		Feb 12, 2026 8:03pm

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
app/app.vue	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

This change modifies the skip link in app/app.vue to navigate using a dynamic router object instead of a static route string. The :to binding now includes the hash '#main-content' along with the current route's query parameters and route params, preserving the existing route context during navigation. This addresses the issue where activating the skip link was previously clearing query parameters from the URL.

Possibly related PRs

• fix(a11y): add tabindex to main content #1385: Makes #main-content focusable via tabindex="-1", which complements this skip link navigation change by ensuring the target element can receive focus.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description directly addresses the linked issue #1437, describing the fix to preserve query and params on the skip link.
Linked Issues check	✅ Passed	The changes implement the required fix for issue #1437 by modifying the skip link to preserve query parameters and route parameters when navigating.
Out of Scope Changes check	✅ Passed	All changes in app.vue are directly related to fixing the skip link functionality and do not introduce unrelated modifications.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[OrbisK]

useRouteQuery has the same workaround: https://github.com/vueuse/vueuse/blob/7069eb4cc5ffd7d10ac07277db2d4b67967dfc3f/packages/router/useRouteQuery/index.ts#L93-L97

[knowler]

Nice, it works!

[ben-basten]

Thank you for the quick response to the issue! I just tried the deployment preview - it looks like this PR fixes the query param issue, but now focus no longer moves to the main content and stays on the skip link. So the actual "skip" never happens.

[danielroe]

merging as a hotfix but I think this is an issue with LinkBase

[alexdln]

It seems that "NuxtLink" and HTML "a" behave differently in the context of hash anchors...

[OrbisK]

@ben-basten Thank you! I have fixed this in #1460

[ben-basten]

@OrbisK That looks great, thank you!!