headerTitleAccessibilityProps vs custom header title: which ensures dynamic accessibility updates?

Goal: Ensure that screen readers announce the current screen’s header title immediately after a navigation change, satisfying WCAG 2.1 Success Criterion 2.4.2.

Constraint: React Navigation provides two documented ways to expose accessibility information for the header title – the built‑in headerTitleAccessibilityProps prop, which updates automatically when the navigation title changes, and a custom <Text> header title where developers must manually forward the title prop and apply accessibility attributes.

Uncertainty: It is unclear which method reliably keeps the accessibility label in sync during rapid or nested navigation events without introducing extra boilerplate or risking missed announcements.

Questions:

• Does headerTitleAccessibilityProps consistently reflect title changes when using nested stack or tab navigators?
• When overriding the header with a custom <Text> component, what is the minimal pattern for passing the title prop to keep the accessibility label up to date?
• Which approach reduces the likelihood of announcements being skipped or delayed during fast screen transitions?