Custom JavaScript focus management blocked by page transition router — accessibility issue

i have a page that includes a contact-me form and a separate nav link to the form. when visitors click the contact link, their browsers go to the form but their screen readers read from the top of the page rather than from the contact form. i'd love to find a way to fix this so that it's clear for visually impaired visitors.

here's the technical version of what i've tried:

i'm trying to implement a standard screen reader accessibility fix on a site built with hostinger website builder (manual mode). when a user clicks a navigation link that transitions to another page, i need to programmatically move keyboard focus to a target element on the destination page.

i've tried:

• document-level click listeners
• direct listeners on the nav links in both bubble and capture phase
• polling for aria-busy to clear on the main landmark before calling .focus()

none of these work on the live published site, though the same code works when pasted into the browser console after load. hostinger ai support confirmed there is no documented navigation lifecycle event for the router.

has anyone found a hook or event that fires reliably after a hostinger page transition completes? or any other workaround for focus management in custom code?