Users can navigate through your app using sound when you add descriptive labels to UI elements. When using a screen reader and navigating with touch exploration, labels are read aloud when users touch UI elements on the screen. With that in mind, screen readers can be difficult to use when:
- Sound plays over a screen reader (ie. background music that autoplays) 
- Extra sounds are added to native elements

University of Illinois at Urbana-Champaign

Sound and motion can be incredibly helpful for users to help navigate through your page with or without a screen reader. However, accessibility for screen readers should still be considered when implementing these elements.

Sound and Motion

Material Design Documentation

Accessibility with Sound and Screen Readers

Motion can be helpful for guiding focus between screens. Surfaces can transform into focal points for the user to follow while unimportant elements are removed. To account for users with motion and visual sensitivities you should adhere to the following recommendations:
- Enable content that moves, scrolls, or blinks to automatically be paused, stopped, or hidden if it lasts more than fives seconds
- Limit flashing content to three times in one-second period to meet flash and red flash thresholds
- Avoid flashing large central regions of the screen

Motion Guidelines for Accessibility

Controls in an app can be set to disappear after a certain amount of time has passed. For example, five seconds after starting a video, playback controls can fade from the screen. However, controls that perform high-priority functions can be missed by users if timers cause them to disappear too quickly.  Keep this in mind when setting timed controls for different elements.

Learn Before

Related