ACTION-660: Input to BP2, on Constraints and Capabilities of the Mobile Context - Interaction Issues

Hi all,

This is one of a series of emails addressing ACTION-660. This thread
will address the requirements and recommendations for "Constraints and
Capabilities of the Mobile Context - Interaction Issues" in BP2.

Here is the current editor's draft text in the Requirements (2) and Best
Practice Statements (5) sections:
+++++
2.7.2 Interaction Issues

As addressed in BP1, issues of interaction with applications on mobile
devices can also be applicable to web applications in general, e.g.
- limited keypad, e.g. 16-key, leading to difficulty in selecting
characters, and the need for application help in selecting the input
character type 
- physical keying difficulty due to small key size 
- form field navigation 
- overall difficulty in entering text impacting usability, e.g. for
forms and long URLs 
- no pointing device 
- variations in softkeys for navigation and local application menus

However, evolution of mobile devices is adding additional specific
issues that need to be addressed in the mobile context, including:
- new pointing methods, e.g. touch screens  
- dynamic changes in keyboard layout, e.g. between 16-key, querty, and
soft keyboards 
- solve the top left navigation problem [need a definintion of what this
is, and consideration of whether it is actually testable]   

5.7.2 Interaction Issues
(no text yet)
+++++

[bryan] We need specific recommendations to address the requirements
related to the "additional specific issues".

Best regards,
Bryan Sullivan | AT&T