question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Status content discoverable by mobile screen reader swipe gestures

See original GitHub issue

Description

Mobile screen reader users will run into the status content when using swipe gestures. This may cause confusion as to the position or purpose of this seemingly duplicate content.

Adding aria-hidden to the container will avoid this issue as this cause screen readers to bypass the container altogether:

// status-announcer.ts:81
statusElement.setAttribute('aria-hidden', 'true');

Screenshot_20190325-111102

Live Demo

  1. Go to <model-viewer> with Chrome for Android
  2. Load up TalkBack screen reader
  3. Swipe right with one finger until the status content is found

Browser Affected

  • Chrome
  • Edge
  • Firefox
  • Helios
  • IE
  • Safari

OS

  • Android
  • iOS
  • Linux
  • MacOS
  • Windows

Versions

  • model-viewer: v0.1.1

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
svinklecommented, Mar 25, 2019

the status element is read two times (once when the text content changes, and once again as you cycle through elements while swiping)?

Yes, exactly this.

If we added aria-hidden to the element, would changes to its text content still be announced correctly?

Yes, announcements still occur as expected.

There would be no change other than the visually hidden text node is bypassed while using swipe navigation.

0reactions
elalishcommented, Aug 1, 2022

I think this was fixed as part of our other a11y work.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Mobile Screen Reader Testing - Scott Vinkle
Swipe : Use a single finger and swipe right, anywhere on the screen. This allows the screen reader to locate and announce content...
Read more >
How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile
For example, a swipe in from the left side of the screen gesture to open a menu is not discoverable without an indicator...
Read more >
Screen Readers on Touchscreen Devices
Screen Readers and Gestures on Touchscreen Devices ; Drag one finger over the screen to explore the interface and hear the screen reader...
Read more >
Browsing with a mobile screen reader - TetraLogical
The most common approach to navigating with a mobile screen reader is to swipe through content sequentially. ... In addition, mobile screen ...
Read more >
Principles for improving app accessibility - Android Developers
TalkBack: helps people who have low vision or are blind. It announces content through a synthesized voice and performs actions on an app...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found