E-mail List Archives
Thread: Resources for Keyboard Interface Design
Number of posts in this thread: 3 (In chronological order)
From: Sam Cartsos
Date: Tue, Dec 08 2015 3:26AM
Subject: Resources for Keyboard Interface Design
No previous message | Next message →
Are there good resources anyone can recommend - online and/or people -
for designing efficient and friendly keyboard interfaces for an involved
web-based application?
Thanks,
Sam
--
*Sam Cartsos*
Co-Founder and Senior Partner @
Frameweld <https://frameweld.com> - Accelerating Innovation
SyncWords <https://syncwords.com> - Caption Automation that Works
mobile: 718.813.1195
office: 718.956.0299
email: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
skype: scartsos
twitter: @scartsos <https://twitter.com/scartsos>
==============
From: Birkir R. Gunnarsson
Date: Tue, Dec 08 2015 8:45PM
Subject: Re: Resources for Keyboard Interface Design
← Previous message | Next message →
The closest you have to keyboard operation recommendations is the ARIA
Authoring practices
http://www.w3.org/TR/wai-aria-practices/ (check out the section on
keyboard operation and the chapter on specific patterns that generally
includes keyboard accessibility recommendations).
If you decide to build your own keyboard shortcuts, you have to make
sure you expose tem to keyboard only user in an accessible way, you
can't leave them guessing how to operate your interface. You can use
access keys with some restrictions but, the problem with the accesskey
attribute is that it does not get exposed to a keyboard only user by
the browser.
Avoid single letter keys doing something specific, there are conflicts
with screen reader users, or at least tell the screen reader users
about these keys up front along with the recommendation that they turn
their virtual buffer off (this puts a lot of responsibility on you
though that you provide all the info necessary to navigate in a very
restricted manner, use this solution sparingly).
Finally, use native html elements whenever possible/appropriate, try
not to invent he wheel, the effort of making it round usually beats
the vision of making it turn faster.
On 12/8/15, Sam Cartsos < = EMAIL ADDRESS REMOVED = > wrote:
> Are there good resources anyone can recommend - online and/or people -
> for designing efficient and friendly keyboard interfaces for an involved
> web-based application?
>
> Thanks,
> Sam
>
> --
> *Sam Cartsos*
> Co-Founder and Senior Partner @
> Frameweld <https://frameweld.com> - Accelerating Innovation
> SyncWords <https://syncwords.com> - Caption Automation that Works
>
> mobile: 718.813.1195
> office: 718.956.0299
> email: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> skype: scartsos
> twitter: @scartsos <https://twitter.com/scartsos>
> ==============>
> > > > >
--
Work hard. Have fun. Make history.
From: Sam Cartsos
Date: Wed, Dec 09 2015 5:00AM
Subject: Re: Resources for Keyboard Interface Design
← Previous message | No next message
Thanks Birkir. I've seen the WebAIM guidelines on the JAWS and NVDA
shortcuts which is helpful. I am thinking about implementing my own
shortcuts and was looking to Github's implementation as a possible
model. They use quite a few single letter shortcuts and shortcuts that
use letter combinations in quick succession. Do you have any thoughts on
their specific implementation?
Thanks,
Sam
On 12/8/2015 10:45 PM, Birkir R. Gunnarsson wrote:
> The closest you have to keyboard operation recommendations is the ARIA
> Authoring practices
> http://www.w3.org/TR/wai-aria-practices/ (check out the section on
> keyboard operation and the chapter on specific patterns that generally
> includes keyboard accessibility recommendations).
> If you decide to build your own keyboard shortcuts, you have to make
> sure you expose tem to keyboard only user in an accessible way, you
> can't leave them guessing how to operate your interface. You can use
> access keys with some restrictions but, the problem with the accesskey
> attribute is that it does not get exposed to a keyboard only user by
> the browser.
> Avoid single letter keys doing something specific, there are conflicts
> with screen reader users, or at least tell the screen reader users
> about these keys up front along with the recommendation that they turn
> their virtual buffer off (this puts a lot of responsibility on you
> though that you provide all the info necessary to navigate in a very
> restricted manner, use this solution sparingly).
> Finally, use native html elements whenever possible/appropriate, try
> not to invent he wheel, the effort of making it round usually beats
> the vision of making it turn faster.
>
>
>
>
> On 12/8/15, Sam Cartsos < = EMAIL ADDRESS REMOVED = > wrote:
>> Are there good resources anyone can recommend - online and/or people -
>> for designing efficient and friendly keyboard interfaces for an involved
>> web-based application?
>>
>> Thanks,
>> Sam
>>
>> --
>> *Sam Cartsos*
>> Co-Founder and Senior Partner @
>> Frameweld <https://frameweld.com> - Accelerating Innovation
>> SyncWords <https://syncwords.com> - Caption Automation that Works
>>
>> mobile: 718.813.1195
>> office: 718.956.0299
>> email: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>> skype: scartsos
>> twitter: @scartsos <https://twitter.com/scartsos>
>> ==============>>
>> >> >> >> >>
>
--
*Sam Cartsos*
Co-Founder and Senior Partner @
Frameweld <https://frameweld.com> - Accelerating Innovation
SyncWords <https://syncwords.com> - Caption Automation that Works
Partner Lead for Technology @
IDEA Data Center <https://ideadata.org> - Building Capacity for
High-Quality IDEA Data
mobile: 718.813.1195
office: 718.956.0299
email: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
skype: scartsos
twitter: @scartsos <https://twitter.com/scartsos>
==============
*Check Out Our Products*
SyncWords <https://syncwords.com> - Captions Automated
Recapd <https://recapd.com> - Live Captions Delivered
Encourse <https://encour.se> - A Smart Learning Platform
Workshop <https://workshop.frameweld.com> - A Better Way to Present Video