[ ] monitor changes in 'location' with client side router
[ ] update document.pageTitle
[ ] ensure application resets focus on "virtual page load"
[ ] ensure screenreader announces page title relevant to content
Other Notes
When you navigate on a server rendered page, the page is torn down by the browser and focus is reset to the top of the window. Once at the top of the window, a screenreader will read the new page
(and URL sometimes) to give the user a frame of reference of where they are and confirmation they got to where they were going. Then the user begins tabbing through content, hopefully assisted by some helpful skip navigation links.
we have already implemented 2 out of 3 requirements to improve a11y on our "virtual pages"
focus is reset to the top of the window.
user begins tabbing through content, hopefully assisted by some helpful skip navigation links.
we can explore adding this additional functionality to complete the a11y improvements and better align our embedded apps with similar server rendered experiences
***NOTE: search engines will not have access to or crawl to index these title changes
User / Persona
individual using screen reader(s)
Reason / Justification
for improved accessibility and experience
Acceptance Criteria (AC)
with client side router
<title\>
as live regionpolite
Other Notes
When you navigate on a server rendered page, the page is torn down by the browser and focus is reset to the top of the window. Once at the top of the window, a screenreader will read the new page
we have already implemented 2 out of 3 requirements to improve a11y on our "virtual pages"
we can explore adding this additional functionality to complete the a11y improvements and better align our embedded apps with similar server rendered experiences
***NOTE: search engines will not have access to or crawl to index these title changes