W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

Re: Voiceover detection in JavaScript

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Tue, 02 Apr 2013 18:47:42 +0100
Message-ID: <515B19BE.8050106@splintered.co.uk>
To: w3c-wai-ig@w3.org
Just a few observations here:

On 02/04/2013 18:34, Bryan Garaventa wrote:
> Scrollable Divs are present all over the web, however they are extremely
> difficult to use with Voiceover running. The simplest solution for this
> is to provide two buttons, Scroll Up and Scroll Down, so that Voiceover
> users can simply tap them to scroll the content. However this is highly
> undesirable for visual UI designers and will never be included.

This is also a problem for keyboard users, so not specific to VoiceOver 

> Carousels with dynamically rotating content are also present everywhere,
> but can be very confusing for Voiceover users, when the content keeps
> changing as you try to read it.

And this can also affect users with cognitive disabilities, or those 
using screen magnifiers.

> Videos that play automatically when a page loads are another issue,
> which is fine for sighted users, but is very difficult for Voiceover
> users who can't hear Voiceover reliably when trying to read the content
> of the page to find the player controls when the video keeps playing.

Again, these can be a problem for lots of other users.

Patrick H. Lauke
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]

www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 2 April 2013 17:48:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:44 UTC