Re: Mobile A11y Task Force Agenda Thursday, March 19

All,


Thanks Henny. 


That has always been something we have been trying to convey. Not sure how it was not clearer.


Regards,


Alan






Sent from Windows Mail on a tablet





From: Henny Swan
Sent: ‎Thursday‎, ‎26‎ ‎March‎, ‎2015 ‎8‎:‎27‎ ‎AM
To: Mike Shebanek
Cc: Mobile Accessibility Task Force, Andrew Kirkpatrick, Joshue O Connor, jimallan@tsbvi.edu, Kim Patch




Hi All,



I noticed a comment via Patrick Lauke on Github in response to the proposed new text below [1]. It might be worth adding this to the list of discussions.




Henny






[1] https://github.com/w3c/Mobile-A11y-TF-Note/issues/4#issuecomment-83766206





—

Henny Swan

User Experience and Design Lead

The Paciello Group

Twitter: iheni

Skype: ihenix



”






On 18 Mar 2015, at 15:08, Mike Shebanek <shebanek@yahoo-inc.com> wrote:







Hi All:




>devices. (Mobile Accessibility Task Force)
>http://www.w3.org/WAI/GL/mobile-a11y-tf/track/actions/24

>On: Mike Shebanek
>Due: 2015-03-19








Related to my Action item (#24) above, I'm proposing an additional bullet to 3.1 Keyboard Control for Touchscreen Devices to indicate supporting keyboards also benefits people who require alternate input devices that mimic keyboards:




•   Those who require alternative input devices such as switch controls that mimic keyboard input








I've also included a proposed revision to the main text for your review. The suggested new text is below followed by the original text.




-- Mike Shebanek








=======================




Proposed Text

 

3.1 Keyboard Control for Touchscreen Devices


Many mobile devices do not include a physical keyboard but instead require a user to interact with an on-screen keyboard that appears only when an interface control that accepts text or numeric input (e.g. a text box or edit field) is selected.


 

Even though an on-screen keyboard may be provided, many people with disabilities require an alternative software or hardware keyboard solution in order to effectively use one of these mobile devices.






Mobile Touchscreen devices and apps should be operable using a physical keyboard or alternative external input device and provide or support alternative on-screen keyboard layouts. When being operated using a physical keyboard, a mobile device should also provide an easily identified and highly visible keyboard cursor indicator. 

 

Most mobile operating systems include keyboard interfaces but these may require specific coding support. These interfaces enable mobile devices to be operated using external devices such as a wired or wireless physical keyboard, switch device, or an alternative on-screen keyboard such as a scanning keyboard or keyboard layout with fewer, larger or higher-contrast keys. 

 


Supporting these keyboard interfaces benefits people with a variety of disabilities including:

 

•   Those with visual disabilities who benefit from the characteristics of physical keyboards clearly separated keys, such as tactile feedback, key nibs and predictable key layouts.

•   Those with dexterity or mobility disabilities who benefit who require keyboards that minimize inadvertent presses (e.g. differently shaped, spaced and guarded keys)

•   Those who require alternative input devices such as switch controls that mimic keyboard input


•   Those who can be confused by the dynamic nature of onscreen keyboards and who benefit from the consistency of a physical keyboard.







=======================



Original Text




3.1 Keyboard Control for Touchscreen Devices

Mobile device design has evolved away from built-in physical keyboards (e.g. fixed, slide-out) towards devices that maximize touchscreen area and display an on-screen keyboard only when the user has selected a user interface control that accepts text input (e.g. a textbox). 




However, keyboard accessibility remains as important as ever and most major mobile operating systems do include keyboard interfaces, allowing mobile devices to be operated by external physical keyboards (e.g. keyboards connected via Bluetooth, USB On-The-Go) or alternative on-screen keyboards (e.g. scanning on-screen keyboards). 




Supporting these keyboard interfaces benefits several groups with disabilities: 
People with visual disabilities who can benefit from some characteristics of physical keyboards over touchscreen keyboards (e.g. clearly separated keys, key nibs and more predictable key layouts). 
People with dexterity or mobility disabilities, who can benefit from keyboards optimized to minimize inadvertent presses (e.g. differently shaped, spaced and guarded keys) or from specialized input methods that emulate keyboard input. 
People who can be confused by the dynamic nature of onscreen keyboards and who can benefit from the consistency of a physical keyboard.

















On Tuesday, March 17, 2015 9:44 AM, Kim Patch <kim@redstartsystems.com> wrote:







Greetings! 

The next Mobile A11y Taskforce meeting will be this Thursday, March 19 at 11 AM Eastern  (Length: 1 hour).  For your local time, please use World Clock: http://tinyurl.com/pwgf6wc. 

Teleconference bridge:
·          +1.617.761.6200

·          Instructions for VoIP "Zakim-SIP"

·          Code: 6283

IRC:

·          Channel: #mobile-a11y

·          Server: irc.w3.org

·          Port: 6665

Agenda:

1. Comments on note (changes will be included in a future version of the note)

2. New work on input methods
3. Next Steps – Next meeting Thursday, March 26


Thanks!


Kim & Kathy 

Mobile Accessibility Taskforce Co-facilitators
 

--