In `@packages/nuxt/src/app/components/nuxt-announcer.ts`:
- Around line 17-20: The code passes props.politeness as a plain value to
useAnnouncer, so changes to the parent prop won't propagate; update setup to
pass a reactive reference instead (e.g., create a ref with toRef(props,
"politeness") or watch props.politeness and call set/update on the useAnnouncer
API) and ensure you import toRef (or watch) from 'vue' and use the reactive ref
when calling useAnnouncer or when updating its politeness option; target the
useAnnouncer call and the props.politeness usage to keep the composable in sync.
- Around line 35-37: The span currently hardcodes role="alert" while binding
aria-live to politeness.value, causing a conflict; change the role to be
computed from politeness.value (e.g. if politeness.value === 'assertive' use
'alert', otherwise use 'status' or omit role) and replace the literal 'role':
'alert' in the h('span', ...) props with that computed value (or remove role
when politeness is absent) so the role and aria-live are consistent; locate the
h('span', { 'role': 'alert', 'aria-live': politeness.value, ... }) occurrence in
nuxt-announcer.ts and update it to use the computedRole derived from
politeness.value.

In `@packages/nuxt/src/app/composables/announcer.ts`:
- Around line 25-28: The set function using shallowRef for message will not
re-trigger reactivity when the same primitive string is set twice; update the
set implementation (function set) to clear message.value briefly before
assigning the new message (e.g., set message.value = '' then await nextTick() or
use a zero-delay setTimeout) and then assign message.value = messageValue and
politeness.value = politenessSetting so identical consecutive messages are
re-announced by the aria-live region.

In `@test/nuxt/composables.test.ts`:
- Around line 922-926: The test description claims it verifies the default
politeness but calls useAnnouncer with an explicit { politeness: 'polite' };
change the test to call useAnnouncer() with no arguments so it exercises the
default behavior (replace useAnnouncer({ politeness: 'polite' }) with
useAnnouncer()), then assert announcer.politeness.value === 'polite' to validate
the default; keep the test name and expectations otherwise unchanged.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/nuxt/src/app/components/nuxt-announcer.ts`:
- Around line 37-39: The component currently sets role.value alongside
politeness.value, which makes role('status') conflict when politeness is 'off';
change the computed role (symbol: role or its getter in nuxt-announcer.ts, and
the AnnouncerPoliteness type usage) to explicitly handle the 'off' case by
returning undefined/null (or mapping to a neutral value like 'log') instead of
'status', and update the render call (the h('span', { 'role': role.value,
'aria-live': politeness.value })) to only add the role attribute when role is
defined so that aria-live="off" is not paired with role="status".

In `@packages/nuxt/src/app/components/nuxt-route-announcer.ts`:
- Line 20: The computed role mapping for nuxt-route-announcer.ts incorrectly
maps politeness.value === 'off' to 'status', conflicting with aria-live="off";
update the computed role (the role constant defined via computed(() =>
politeness.value === 'assertive' ? 'alert' : 'status')) to explicitly handle
'off' by returning undefined or an empty string when politeness.value === 'off',
mirroring the change made in nuxt-announcer.ts so aria-live and role stay
consistent (use politeness.value checks in the computed to return 'alert' for
'assertive', 'status' for 'polite', and undefined/'' for 'off').

---

Duplicate comments:
In `@packages/nuxt/src/app/components/nuxt-announcer.ts`:
- Around line 17-20: The setup currently passes props.politeness as a plain
value into useAnnouncer, so downstream state in useAnnouncer won’t update when
the parent changes politeness; update setup to pass a reactive reference (e.g.,
toRef(props, 'politeness') or a watched wrapper) into useAnnouncer or add a
watch on props.politeness that calls the composable’s setter (setPoliteness /
set or similar) so the composable (useAnnouncer) receives updates; locate the
setup function and the useAnnouncer call to implement the reactive prop passing
or watch.

---

Nitpick comments:
In `@packages/nuxt/src/app/components/nuxt-announcer.ts`:
- Around line 32-54: The outer wrapper span created in the render return (the
element with class "nuxt-announcer") should be made semantically inert to avoid
exposing it to assistive tech; update that element's props to include either
'aria-hidden': 'true' or role: 'presentation' (while keeping the inner sr-only
span with aria-live/aria-atomic intact), and ensure the render still uses
slots.default ? slots.default({ message: message.value }) : message.value for
the inner content so the announcer remains functional.

In `@test/nuxt/composables.test.ts`:
- Around line 957-959: The delete on nuxtApp._announcerDeps uses an unnecessary
and inconsistent cast; remove the `as any` and delete the property directly like
the `_announcer` cleanup. Locate the cleanup block around nuxtApp and replace
`delete (nuxtApp as any)._announcerDeps` with a plain `delete
nuxtApp._announcerDeps`, relying on the optional `_announcerDeps` declaration on
the _NuxtApp interface.