W3C Mobile Web Initiative

The W3C mobileOK™ Checker

François Daoust <fd@w3.org>
W3C Mobile Web Initiative


2009 NEM Summit
Saint-Malo, France, 29 September 2009

EU FP7 Logo
Supported by MobiWeb2.0, funded by European Union's FP7.


Table of Contents
Photo by Elaine Vallet

  1. The World Wide Web Consortium
  2. Mobile Web Best Practices / mobileOK™
  3. The W3C mobileOK Checker
  4. Checker Usage
  5. Future work

First part:
The World Wide Web Consortium

The W3C

Leading the Web to its full potential...

The W3C is a set of tables around which members gather and sit to discuss and agree on something The W3C is a process that ensures resulting standards are stable and interoperable
The W3C is a technical team that ensures standards consistency
Photos by mnadi and psd

Web standards

Standards are bricks on top of which anyone can build
Photo by Elaine Vallet

Privacy, Semantic Web, Accessibility, eGovernement, Mobile Web, ...

The Mobile Web Initiative

Sponsors of the W3C Mobile Web Initiative

Tim Berners-Lee Making Web access from a mobile device as simple as Web access from a desktop device.
Tim Berners-Lee, W3C Director and inventor of the Web

Second part:
The Mobile Web Best Practices / mobileOK™

Mobile Web Best Practices - Why?

Beaucoup de terminaux mobiles sur le marché A bad User eXperience scares people away

User eXperience!

Mobile Web Best Practices - Overview

Mobile Web Best Practices in handy flipcards

Mobile Web Best Practices 1.0:

Mobile Web Best Practices - Example

Without BP
- desktop (good) -
Beethoven - bad - desktop
- phone (bad!) -
Beethoven - bad - phone 
BP inside
- desktop (still good!) -
Beethoven - good - desktop
- phone (good) -
Beethoven - good - phone 

The mobileOK mark

Le logo mobileOK

Third part:
The W3C mobileOK Checker

From Best Practices to mobileOK

The mobileOK Checker Java library is a reference of the mobileOK Basic Tests 1.0 specification that defines formal tests to run to check a consistent set of Mobile Web Best Practices

The W3C mobileOK Checker


The online W3C mobileOK Checker

Categories and severity

Errors are categorized and assigned a severity level to educate authors about the main problems that affect the mobile-friendliness of their page

Encourage time-constrained authors
to address critical problems first

Score and page statistics

The mobileOK score, between 0 and 100, encourages authors to improve the mobile-friendliness of the page

Fourth part:
W3C mobileOK Checker Usage

State of the mobile Web...
... seen by the W3C mobileOK Checker

The state of the mobile Web as seen through the eyes of the mobileOK Checker shows that 10 percent of Web pages are mobileOK. The statistics are biased towards mobile-friendliness because tests were conducted against the set of Web addresses entered by users of the tool.
Repartition per number of sub-tests failed
(on ~60000 Web addresses checked by the tool since April 2008)

Examples of mobileOK Web sites: Google search engine, the official mobile version of Wikipedia, the T-Online portal, Remember the milk, the mobile version of Voici.

Level of Adherence to Best Practices

Mobile Web Best Practices not followed
Best Practice Best Practice explained URIs (%) Domains (%)
VALID_MARKUP Create documents that validate to published formal grammars. 77% 87%
MEASURES Do not use pixel measures and do not use absolute units in markup language attribute values and style sheet property values. 58% 68%
PAGE_SIZE_LIMIT Ensure that the overall size of page is appropriate to the memory limitations of the device. 54% 66%
CHARACTER_ENCODING_USE Indicate in the response the character encoding being used. 49% 61%
IMAGES_SPECIFY_SIZE Specify the size of images in markup, if they have an intrinsic size. 48% 58%
CONTENT_FORMAT_SUPPORT Send content in a format that is known to be supported by the device. 39% 51%
CACHING Provide caching information in HTTP responses. 39% 50%
TABLES_LAYOUT Do not use tables for layout. 34% 38%
POP_UPS Do not cause pop-ups or other windows to appear and do not change the current window without informing the user. 30% 34%
HTTP_RESPONSE (Not a real best practice) 27% 33%

Fifth part:
Future work

Towards a decision-making tool

Moving away from a failure reporting tool to a decision-making tool, where Web authors can find out easily the severity and costs associated with failures reported by the Checker and plan updates according to the time they are willing to spend on improving the mobile-friendliness of their pages



Training courses on the Mobile Web Best Practices

  • Online course: 12th October 2009
  • Face to face course: 14th October 2009, in Cambridge

The End


François Daoust <fd@w3.org>

W3C Mobile Web Initiative


EU FP7 Logo
Supported by MobiWeb2.0,
funded by European Union's FP7.