You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the window body, voiceover reads the title aloud twice in very close proximity to one another.
The areas include:
A <section> has aria-label that reads “Window: TITLE”, so the title is describing the window region of the page (file: src/components/Window.js)
The navigation nested directly below this section, <nav arial-label=“Window navigation”>, includes the title as an <h2> and gets read (file: src/components/WindowTopBarTitle.js)
Note: These come very close to one another, the only things that get read in between are “Window navigation" and "toggle sidebar button".
Work-shopping solutions
While technically not an accessibility issue, it’s certainly a usability concern to those using screen readers since it is likely cumbersome to constantly hear the title (especially long ones). Things to think about
Perhaps the section could be called something more generic, like “Item window”, though I can see how it's helpful to know the title right away when you have multiple images/workspaces open
Consider hiding one from being read, but make sure that the heading is still present in the rotor, as this is a common way people navigate through pages
It's actually quite confusing to navigate multiple workspaces using the rotor, there's not always a clear indication of what workspace you're interacting with
Would love to know what native users think, assuming it's along the lines of what @brittnylapierre has reported and that there's "not enough screen reader feedback"
The text was updated successfully, but these errors were encountered:
Description
In the window body, voiceover reads the title aloud twice in very close proximity to one another.
The areas include:
<section>
has aria-label that reads “Window: TITLE”, so the title is describing the window region of the page (file:src/components/Window.js
)<nav arial-label=“Window navigation”>
, includes the title as an<h2>
and gets read (file:src/components/WindowTopBarTitle.js
)Note: These come very close to one another, the only things that get read in between are “Window navigation" and "toggle sidebar button".
Work-shopping solutions
While technically not an accessibility issue, it’s certainly a usability concern to those using screen readers since it is likely cumbersome to constantly hear the title (especially long ones). Things to think about
The text was updated successfully, but these errors were encountered: