W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2006

UAWG comment on the Mobile Web document

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 09 Feb 2006 08:44:59 -0600
To: Jan Richards <jan.richards@utoronto.ca>, Al Gilman <Alfred.S.Gilman@ieee.org>, WAU-ua <w3c-wai-ua@w3.org>
Message-id: <HDEAKIPKOHBCMDILOOPNOEGLEOAB.jimallan@tsbvi.edu>

Mobile Web Best Practices 1.0

User Agent (browser) developers are participants in the mobile value chain.
The user agents for mobile devices should conform with UAAG [1] guidelines
appropriate. This is especially true now that some mobile devices have
add-on assistive technology such as screen readers.

The document's purpose is aimed more at content developers rather than the
tools to render the content. Underlying this purpose is a continuing
discussion of the limitations of the devices and user agents involved (such
as screen size, color depth, input limitations, memory, etc.)

Specific comments:

section 3.1
which ever content adaptation implementation model is used, the model must
retain necessary accessibility information (alt, label, etc.) and convey
that information to the mobile device and the user.

The following Best Practices Statements should reference UAAG checkpoints.

5.29 Refreshing, Redirection, and Spawned Windows
should reference
UAAG 2.4 Allow time-independent interaction (P1) - 1. For rendered content
where user input is only possible within a finite time interval controlled
by the user agent, allow configuration to provide a view where user
interaction is time-independent.

UAAG 3.5 Toggle automatic content retrieval (P1) 1. Allow configuration so
that the user agent only retrieves content on explicit user request.

5.3.7 Background Images
should reference
UAAG 3.1 Toggle background images (P1) - 1. Allow configuration not to
render background image content.

5.4.3 Structural Elements
should reference
UAAG 10.4 Provide outline view (P2) - 1. Make available to the user an
"outline" view of rendered content, composed of labels for important
structural elements (e.g., heading text, table titles, form titles, and
other labels that are part of the content).

This is all I am able to provide today.

[1] http://www.w3.org/TR/2002/REC-UAAG10-20021217/

Jim Allan, Webmaster & Statewide Technical Support Specialist
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
---> Share to Win!! <---
Received on Thursday, 9 February 2006 14:44:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:35 UTC