- From: <accessys@smart.net>
- Date: Mon, 8 Apr 2013 15:46:46 -0400 (EDT)
- To: Brian Cragun <cragun@us.ibm.com>
- cc: Bryan Garaventa <bryan.garaventa@whatsock.com>, Alastair Campbell <alastc@gmail.com>, WAI Interest Group <w3c-wai-ig@w3.org>
I would suspect that gesture/typing for visually impaired and others might depend on their age, older folks were taught to touch type when they were young and probably prefer the keyboard. Bob On Mon, 8 Apr 2013, Brian Cragun wrote: > Date: Mon, 8 Apr 2013 14:31:55 -0500 > From: Brian Cragun <cragun@us.ibm.com> > To: Bryan Garaventa <bryan.garaventa@whatsock.com> > Cc: Alastair Campbell <alastc@gmail.com>, > WAI Interest Group <w3c-wai-ig@w3.org> > Subject: Re: Voiceover detection in JavaScript > Resent-Date: Mon, 08 Apr 2013 19:32:35 +0000 > Resent-From: w3c-wai-ig@w3.org > > 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, 8 April 2013 19:47:30 UTC