NuxtLink aria-current on dynamic routes: which link should announce the current page?

Short answer

For a mixed nav in Nuxt 3, the static link (/) and external link behave predictably, and the dynamic links are the only real risk area — but probably not for the reason you suspect. <NuxtLink> delegates its active state to Vue Router's RouterLink, which distinguishes between active (same route record) and exact active (same record and same location, including params). aria-current="page" is applied on the exact match, so moving from /post/123 to /post/456 should move the attribute to the correct link — params are part of the comparison.

That said, this behavior has shifted across Nuxt 3 point releases, and I have not verified it against your exact version. Treat the above as the expected behavior and confirm it with the check below before shipping.

Confirmed vs. likely

• Confirmed: external URLs passed to <NuxtLink to="https://…"> are rendered as plain anchors outside the router's matching, so they never receive aria-current. That is correct behavior — an external link is never "the current page."
• Confirmed: there is no documented prop on <NuxtLink> to change the aria-current value (e.g. page vs location) or to opt out per link. Overriding requires your own wrapper.
• Likely, verify: exact-active matching includes params, so two /post/:id links should not both announce. If your nav only ever contains one link per dynamic pattern (the typical case — a nav links to a section, not to a specific post), the ambiguity you're worried about cannot occur at all.

Verify in two minutes

// pages or a test nav with two dynamic links
<NuxtLink to="/post/123">Post 123</NuxtLink>
<NuxtLink to="/post/456">Post 456</NuxtLink>

Navigate between the two routes and inspect the rendered anchors in DevTools. Only the link whose to matches the current full path should carry aria-current="page". If both do, your Nuxt version's matching is pattern-only and you need the wrapper below.

Escape hatch: a small wrapper

Where the default is ambiguous — or where you want aria-current="location" for a sub-section — wrap the link and control the attribute yourself:

<script setup lang="ts">
const props = defineProps<{ to: string; currentValue?: string }>()
const route = useRoute()
const isCurrent = computed(() => route.fullPath === props.to)
</script>

<template>
  <NuxtLink :to="to" :aria-current="isCurrent ? (currentValue ?? 'page') : undefined">
    <slot />
  </NuxtLink>
</template>

Comparing route.fullPath to the target gives you exact, param-aware matching regardless of what the built-in behavior does in your version.

Recommended pattern for your nav

1. Keep plain <NuxtLink> for static and section-level links — one link per route pattern, so matching is unambiguous.
2. Leave external links as-is; no aria-current is correct there.
3. If a nav ever links to a specific dynamic instance (e.g. "current post"), use the wrapper so you control the comparison explicitly.
4. Do a screen-reader pass (NVDA or VoiceOver) before release — attribute presence is easy to verify in the DOM, but announcement order and wording are not.

One detail that would change this advice: your exact Nuxt version. If the DevTools check shows pattern-only matching, pin the wrapper approach everywhere rather than relying on defaults.