Fix focus reset after AJAX page navigation

[nonprofittechy]

Summary

• move post-navigation focus to the page title/question label instead of dropping focus
• make the non-link #dapagetitle span programmatically focusable with tabindex="-1"
• regenerate the shipped JS bundles and sourcemaps so the browser-served assets include the fix

Problem

After activating Continue and landing on a new page, the fallback focus logic could immediately blur the focused element or try to focus a non-focusable page title span. That left keyboard users in the middle of the page instead of at the top-most meaningful target.

Result

Keyboard and assistive-technology users now land on a stable, top-of-page focus target after AJAX page transitions, which keeps the tab order aligned with WCAG expectations.

[nonprofittechy]

Proposed fix for tab navigation issue that MATC pointed out to us; needs some testing.

[BryceStevenWilley]

I like the idea, but IMO it should target the Question title, not the page / interview title. Focusing to the page title doesn't really fix the number of tab presses it takes for a user to get to main content of the page, but starting focus on the question title would bring the user right there.