Mobile Web Best Practices Working Group News

Guidelines for Web Content Transformation Proxies open for review — 29 October 2009

More than a year ago, we, the Mobile Web Best Practices Working Group, published a Last Call of a document then called Content Transformation Guidelines, and invited the community to review the document. The document provides guidance to Content Transformation proxies as to whether and how to transform Web content.

Many comments were received. They triggered extensive discussions within the group. Finding the right balance between allowing proxies to alter content that would otherwise not display successfully on mobile devices and reducing side-effects such proxies may have on Web applications already designed for mobile devices is no easy task! Significant changes were brought to the document as a result and another Last Call was published a couple of weeks ago under the title Guidelines for Web Content Transformation Proxies 1.0.

We think we have addressed and replied to all the comments, providing rationale when we have not incorporated the suggested changes. We deeply thank last year's commenters, and apologize for the time it took to address the comments!

Once again, we would like to invite the community at large (and in particular mobile Web authors who are impacted by the deployment of such transcoding proxies) to review and comment the document. The Status of This Document section contains a list of the changes made in response to user feedback.

The Last Call review period ends on 6 November 2009. Comments should be sent to the public-bpwg-comments@w3.org public mailing-list (with public archives).

Francois Daoust Permalink

Mobile Web and Web Content Accessibility — 13 July 2009

The Mobile Web Best Practices Working Group (BPWG) and the WAI Education and Outreach Working Group (EOWG) published the W3C Working Group Note: Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG). People with disabilities using computers have similar interaction limitations as people without disabilities who are using mobile devices. This note describes the similarities and differences between the requirements Web Content Accessibility Guidelines (WCAG) and Mobile Web Best Practices 1.0 (MWBP). Following these two guidelines makes your Web content more accessible to everyone regardless of situation, environment, or device. Designing the guidelines together, instead of separately, can make the process more efficient. This note includes the following pages:

Introductory information and links to related documents are in Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices.

Yeliz Yesilada 1 comment Permalink

First extension to the mobileOK Checker library released to check files! — 2 July 2009

A new extension to the W3C mobileOK open source library is available that can be used to validate pages served via the file URI scheme. The W3C mobileOK open source Java library has been developed in such a way that it is very easy to extend. We strongly encourage people to extend this library so that a better infrastructure is provided to designers for creating mobile-friendly content.

The mobileOK Basic Tests 1.0 Checker library provides a reference implementation of the tests specified in the W3C mobileOK Scheme 1.0. This scheme requires that pages are served via HTTP protocol, however there might be some cases where validating pages that are stored locally would be useful. Therefore, this new extension has been created and can be used to validate pages served via file URI scheme. The extension is designed and implemented in a way that does not affect the basic reference implementation. It is also important to note that validating pages only with this extension does not guarantee that the page is mobileOK as some tests require HTTP connection. This extension has to be used in-coordination with the W3C mobileOK Checker and does not replace the core mobileOK library.

If you want to use this extension with the main library then you need to download and install it.

A technical documentation explains in detail how this extension can be installed and used.

This extension has been developed as part of the UK EPSRC funded RIAM (Reciprocal Interoperability of Accessible and Mobile Webs) project with the help of the Mobile Web Best Practices Checker Task Force.

Yeliz Yesilada Permalink

<< Previous Page :: Next Page >>

Contacts: Daniel Appelquist, Jo Rabin, Chairs
Dominique Hazaël-Massieux and François Daoust, W3C Team Contacts