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

Re: Voiceover detection in JavaScript

From: Brian Cragun <cragun@us.ibm.com>
Date: Mon, 15 Apr 2013 13:04:08 -0500
To: David Hilbert Poehlman <poehlman1@comcast.net>
Cc: Alastair Campbell <alastc@gmail.com>, Bryan Garaventa <bryan.garaventa@whatsock.com>, WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <OF9BC6D49D.84AE18DD-ON86257B4E.00621244-86257B4E.0063414E@us.ibm.com>
Hi David, 

I did a little more checking and I don't actually find hardware keyboard 
and Assistive touch are mutually exclusive.  When I have Assistive Touch 
enabled, and then add the keyboard (via Bluetooth pairing) and then 
activate Voiceover, the Assitive Touch remains active.  It responds to 
button presses via touch gesture.   When the Assistive Touch menu is 
displayed, I can navigate using the keyboard and select any action.

The only thing I can't do is get focus to the Assistive Touch  icon.  The 
keyboard navigation ring just skips over it.  But if I tap it once to give 
it focus, I can use the keyboard commands to open it and use the 
subsequent menus.

Brian Cragun
IBM AbilityLab Consultant
Human Ability & Accessibility Center
www.ibm.com/able





From:   David Hilbert Poehlman <poehlman1@comcast.net>
To:     Bryan Garaventa <bryan.garaventa@whatsock.com>, 
Cc:     Brian Cragun/Rochester/IBM@IBMUS, Alastair Campbell 
<alastc@gmail.com>, WAI Interest Group <w3c-wai-ig@w3.org>
Date:   04/08/2013 03:22 PM
Subject:        Re: Voiceover detection in JavaScript



Assistive touch and hardware keyboard are mutually exclusive.  sadly, 
assistive touch is not toggled on by the removal of the keyboard, but is 
removed by its addition.
-- 
Jonnie Appleseed
With His
Hands-On Technolog(eye)s
touching the internet
Reducing Technology's disabilities
One Byte At a time

On Apr 8, 2013, at 4:04 PM, "Bryan Garaventa" <
bryan.garaventa@whatsock.com> wrote:

Unfortunately I'm not aware of the keyboard accessibility of the assistive 
touch feature, but I can't find any documentation on the web that suggests 
it is keyboard accessible. Hopefully others here can share more info on 
it.
 
 
 
 
----- Original Message ----- 
From: Brian Cragun 
To: Bryan Garaventa 
Cc: Alastair Campbell ; WAI Interest Group 
Sent: Monday, April 08, 2013 12:31 PM
Subject: Re: Voiceover detection in JavaScript

Hi Bryan, 

I think it was user error on my part.  :-)  A little more testing showed 
that the "bounce back" occurs on the time slider when the  horizontal 
slider has engaged more than 20%.  In that case, the time slide button is 
not visible, and for some reason this causes it to not retain focus.  When 
I set the horizontal slider to 0%, the time slider works with the gesture, 
or with the keyboard after selecting the link. 

Wireless keyboards.   We're requiring teams that develop mobile apps to 
test both gesture access and keyboard access using a paired wireless 
keyboard.  This is to meet the standards criteria, which still require 
keyboard access, and we think the Soft keyboard on iOS not sufficient for 
the standard, as we understand it.   Keyboards could benefit navigation by 
the blind (although most blind people I know prefer gestures) but also 
those with mobility impairment.  I don't have a switch to test with, but 
paired keyboard access would be a good indicator of  access without 
gesture. 

BTW.  The only iOS native element I have not been able to access with the 
keyboard, so far, is the assistive touch icon.  Any ideas? 

Brian Cragun 
IBM AbilityLab Consultant
Human Ability & Accessibility Center





From:        "Bryan Garaventa" <bryan.garaventa@whatsock.com> 
To:        Brian Cragun/Rochester/IBM@IBMUS, 
Cc:        "Alastair Campbell" <alastc@gmail.com>, "WAI Interest Group" <
w3c-wai-ig@w3.org> 
Date:        04/08/2013 01:57 PM 
Subject:        Re: Voiceover detection in JavaScript 



A wireless bluetooth combination, I hadn't thought of that. The hidden 
link is provided as a fallback for users with screen readers that don't 
support the use of ARIA, but if a keyboard is being used, it should be 
possible to set focus to the slider itself, since it is already programmed 
to be keyboard accessible, then the arrow keys would move the slider? Then 
again, I seem to remember that the arrow keys on Voiceover move focus 
instead of passing this through to the control. 
  
I'm not sure why the time slider would bounce focus. It literally uses the 
same setup script as the first slider, the only difference is the CSS 
which makes it a vertical slider instead of a horizontal one, and 
aria-orientation="vertical" is set on the slider. 
  
I tried this using the gestures and didn't have a bounce effect. Which 
mode of navigation does this happen on? Also, it's important to move the 
first slider to 0% before trying the Time slider, because the image that 
opens will obscure the second slider. 
  
The Time slider also has a hidden link fallback that opens a standard 
select as well, which is intrinsically bound to the slider. 
 
 
 
 
----- Original Message ----- 
From: Brian Cragun 
To: Bryan Garaventa 
Cc: Alastair Campbell ; WAI Interest Group 
Sent: Monday, April 08, 2013 11:01 AM 
Subject: Re: Voiceover detection in JavaScript 

Bryan, that is a fantastic gesture to learn!  Works great for gesture 
interaction.  Is there a corresponding bluetooth wireless keyboard key 
combination to interact with the slider? 
The only thing I can find is to "select" the slider bar brings up a popup 
button to set the value. 

Also, any idea why on this demo when I navigate to the "time" slider, the 
page resets and the focus goes to the top of page? 

Brian Cragun 
IBM AbilityLab Consultant




From:        "Bryan Garaventa" <bryan.garaventa@whatsock.com> 
To:        "Alastair Campbell" <alastc@gmail.com>, 
Cc:        "WAI Interest Group" <w3c-wai-ig@w3.org> 
Date:        04/08/2013 11:31 AM 
Subject:        Re: Voiceover detection in JavaScript 



This would be the page at 
http://whatsock.com/modules/aria_slider_module/demo.htm 
 
Voiceover incorrectly says that you should swipe up and down with one 
finger to adjust the slider, but David gave the correct sequence earlier, 
which is to double tap and hold with one finger, wait for the pass-through 
sound, then slide your finger in the direction you want to drag the 
slider. 
 
----- Original Message ----- 
From: Alastair Campbell 
To: Bryan Garaventa 
Cc: WAI Interest Group 
Sent: Monday, April 08, 2013 1:42 AM 
Subject: Re: Voiceover detection in JavaScript 

I couldn't get anything to 'slide' in iOS, with or without VoiceOver, I 
just used the buttons. 

Perhaps we're talking at cross-purposes, which page do you mean? 


On Sun, Apr 7, 2013 at 8:45 PM, Bryan Garaventa <
bryan.garaventa@whatsock.com> wrote: 
The issue is that I can't get Voiceover to grab the slide, then move it. 
If there is a gesture sequence for this though, I definitely want to learn 
it. 
 
The carousels are fine in Voiceover, I worked on these a while ago. For 
some reason Voiceover on iOS isn't paying attention to aria-hidden="true" 
when included within a button element. That's a bout it though. 
 
 
----- Original Message ----- 
From: Alastair Campbell 
To: Bryan Garaventa 
Cc: WAI Interest Group 
Sent: Sunday, April 07, 2013 5:16 AM 
Subject: Re: Voiceover detection in JavaScript 

> Now, if only I could fix the ARIA Sliders that easily. 

What was the issue there? I tried the carousel and slidershow, they seemed 
ok. Could adjust the ordering a little to make it easier to understand 
(and don't rely on having an esc key), but it seemed ok. 

-Alastair 
Received on Monday, 15 April 2013 18:04:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC