PFWG Review for Mobile Web Application Best Practices

The following are comments from the Protocols and Formats Working Group
on the Mobile Web Application Best Practices draft
http://www.w3.org/TR/2010/WD-mwabp-20100713/. Approval to send this as a
PFWG comment is archived at http://www.w3.org/2010/07/28-pf-minutes#item06.

Comment 1

> 3.5.3 Design for Multiple Interaction Methods 3.5.3.1 What it means …
>  • Focus Based: The browser focus "jumps" from link to link;

and

> 3.5.3.2 How to do it Focus Based: …
> Focus area will jump automatically from one selectable element to
> another (e.g. from link to link) without affecting usability even
> when widely spaced.

Suggest changing "from link to link" to "from element to element."

Comment 2

Suggest adding a fourth type of interaction method to 3.5.3.1:

Assistive Technology Based: Events are controlled by a software
application (e.g. screen reader or voice control application) acting on
behalf of the user.

Comment 3

> 3.5.3.2 How to do it Touch Based: … Selectable elements must be large
> enough to be easily selected (e.g. list items should have a height of
> at least 30px);

Suggest using a physical size rather than a pixel size, as device
resolutions and DPI scale can vary from device to device, or explain in
better detail that this is not referring to physical screen pixels.
Mobile devices today range from less than 72 dpi to greater than 300 dpi.

Comment 4

Suggest adding a fourth type of interaction method to 3.5.3.2:

Assistive Technology Based:

• Follow recommendations outlined in the Web Content Accessibility
Guidelines 2.0 [http://www.w3.org/TR/WCAG20/]
• For mobile web applications that allow creation of web content, follow
recommendations outlined in the Authoring Tool Accessibility Guidelines
2.0 [http://www.w3.org/TR/ATAG20/]
• Once the spec reaches CR, follow recommendations outlined in
Accessible Rich Internet Applications 1.0 [http://www.w3.org/TR/wai-aria/]
• Elements should be operable through means outside the primary
interaction method for each device. For example, on a device where the
primary interaction model is touch-based, assistive technology software
may operate using a focus-based interaction model even though there is
no concept of focus in the primary interaction model.

-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>