TL,DR;
Inviting discussion: I recommend using the page title as the default navigation announcement text.
Description
I've been using ember-a11y-refocus in some of my public-facing apps for about a year. During that time, I have been lucky enough to put those apps through accessibility-focused user testing multiple times. However, there's been a problem with the navigation announcement. I'm curious if anyone else has had this experience when testing apps that user ember-a11y-refocus with screen reader users.
At least two screen reader users (albeit ones with lots of web dev a11y knowledge) have commented that the <NavigationNarrator> text is confusing and not what they expect when navigating pages. I received two main pieces of feedback:
- The user expected to hear the title of the page, not whatever text is in the narrator (for me, it's "Page loaded").
- The user was confused that the text is persistent on the page.
For the first issue, I think it may be less confusing if the narrator announces the new page title. I'm not sure what to do about the second issue.
I welcome any insight others may have!
TL,DR;
Inviting discussion: I recommend using the page title as the default navigation announcement text.
Description
I've been using
ember-a11y-refocusin some of my public-facing apps for about a year. During that time, I have been lucky enough to put those apps through accessibility-focused user testing multiple times. However, there's been a problem with the navigation announcement. I'm curious if anyone else has had this experience when testing apps that userember-a11y-refocuswith screen reader users.At least two screen reader users (albeit ones with lots of web dev a11y knowledge) have commented that the
<NavigationNarrator>text is confusing and not what they expect when navigating pages. I received two main pieces of feedback:For the first issue, I think it may be less confusing if the narrator announces the new page title. I'm not sure what to do about the second issue.
I welcome any insight others may have!