Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redundant title read by screen reader #3904

Open
mferrarini opened this issue Apr 30, 2024 · 0 comments
Open

Redundant title read by screen reader #3904

mferrarini opened this issue Apr 30, 2024 · 0 comments

Comments

@mferrarini
Copy link

Description

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"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Design Backlog
Development

No branches or pull requests

1 participant