WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard navigation

for

From: Birkir R. Gunnarsson
Date: Jan 24, 2014 10:18AM

Sara

What happens when user needs to use the n key when typing into a form
field on the page.
Basically, a keyboar navigation interface needs to allow for the
concept of interactive typing and filling in forms, similar to the
forms mode in screen readers.
I absolutely agree that browsers should offer up a more robust support
for keyboard only behavior.
I think that would be a fantastic addition for a lot of people, not
just with disabilities but frequent/power users of websites.
I know the traders at the investment bank I used to work for always
used a console mode app for trading stocks because using the keyboard
they could pull of trades much more quickly.



On 1/24/14, <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:
> Hi Sailesh,
> Nice to know about opera support. I'll try that out. Thank you for sharing.
>
>
> Best regards,
>
> Srinivasu Chakravarthula
> Mobile: +91 990 081 0881
> Website: http://www.srinivasu.org |http://sgaccessibility.com
> Follow me on Twitter:http://twitter.com/CSrinivasu
>
> Sr. Accessibility Lead at PayPal
> Founder at Sai Gagan Accessibility Solutions
> Hon. Joint Secretary at The National Association for the Blind, Karnataka
> Branch
> http://about.me/srinivasuc
>
> Sent from my iPhone 4S
>
>> On 24-Jan-2014, at 19:30, Sailesh Panchang < <EMAIL REMOVED> >
>> wrote:
>>
>> Hello Srinivasu,
>> At least one browser (Opera) did permit heading navigation from the
>> keyboard ... I suppose that is more robust now ... no personal
>> experience there.
>> My responses are in the context of the thought in the first email.
>> And in that context I said that SRs do allow one to work with speech
>> off.
>> Sure one can have a user agent that allows keyboard navigation in a
>> manner that is as robust as SRs allow with no speech funtctionality at
>> all.
>> Sailesh
>>
>>
>>> On 1/24/14, <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:
>>> Sailesh,
>>> While I agree that's a solution, I'm unsure if a general keyboard only
>>> user
>>> would aware of this. In fact why would they even think of a screen
>>> reader?
>>> Since we are all in the accessibility industry, we could think of cross
>>> disability and aware of AT features across.
>>>
>>> Also, I'm not sure if screen reader vendors ever document with keywords
>>> of
>>> other disabilities.
>>>
>>> Further, all they would need is a quick navigation feature and why would
>>> they need to install a screen reader that require investment of more
>>> space.
>>>
>>>
>>> Can we think of a plugin that could just turn on quick navigation feature
>>> by
>>> pressing an access key?
>>>
>>> Am I missing something?
>>>
>>> Regards,
>>> Srinivasu Chakravarthula | PayPal | @csrinivasu
>>> Sent from my iPhone 5C
>>>
>>>> On 24-Jan-2014, at 16:33, Sailesh Panchang < <EMAIL REMOVED> >
>>>> wrote:
>>>>
>>>> Speech off has been built into SRs for the same reason for a long time
>>>> now.
>>>> For some aspects, if visual cursor tracking does not work as intended,
>>>> that's a bug to be fixed.
>>>> But overall it is the solution you were hoping for as per your first
>>>> email.
>>>> Thanks and regards,
>>>> Sailesh
>>>>
>>>>> On 1/23/14, Don Mauck < <EMAIL REMOVED> > wrote:
>>>>> I understand that as screen reader myself, however, I'm not convinced
>>>>> that
>>>>> with speech off, the visual cursor would track correctly. I'll half
>>>>> to
>>>>> ask
>>>>> some of my visual friends.
>>>>>