Friday, October 05, 2007

W3C Mobile Web Best Practices checker

W3C's Mobile Web Best Practices Working Group have a set of tests for what makes a mobile web page: "mobileOK Basic". Some of this have been implemented in the W3C Mobile Web Best Practices checker. This goes a bit further than a syntax checker, and for example tells you if your web page is too big for the average phone, but not as far as accessibility tests.

Just for fun I ran the tests on the W3C Mobile Group's own web page:

Results of checking W3C Mobile Web Best Practices Working Group

This page failed on 5 tests

  1. The page is not valid with regard to the XHTML Basic 1.1 DTD.
    This test is related to the following Best Practices: VALID_MARKUP (techniques)
  2. The markup of the page is bigger (19138 bytes) than the upper limit of Default Delivery Context.
    This test is related to the following Best Practices: PAGE_SIZE_USABLE (techniques) PAGE_SIZE_LIMIT (techniques)
  3. The added sizes of the markup and of the external resources embedded in the page are bigger (27608 bytes) than the upper limit of Default Delivery Context.
    This test is related to the following Best Practices: PAGE_SIZE_USABLE (techniques) PAGE_SIZE_LIMIT (techniques)
  4. The image at line 23 column 12 has no width set in the markup.
    This test is related to the following Best Practices: IMAGES_SPECIFY_SIZE (techniques) GRAPHICS_FOR_SPACING (techniques) IMAGES_RESIZING (techniques)
  5. The image at line 23 column 12 has no height set in the markup.
    This test is related to the following Best Practices: IMAGES_SPECIFY_SIZE (techniques) GRAPHICS_FOR_SPACING (techniques) IMAGES_RESIZING (techniques)

The page passed 11 tests

  1. The page provides caching information and does cache validation.
  2. No links are set to open in a separate window.
  3. The page doesn't use objects nor scripts.
  4. The page doesn't use tables.
  5. The page doesn't use image maps.
  6. The page doesn't use auto-refresh nor redirects.
  7. None of the length attributes use absolute values.
  8. The page has no item with a width set to more than the allowed size.
  9. All the images have an alt attribute set; make sure it describes well the content of the image.
  10. The page uses a logical order of headings.
  11. The page has a title set to "W3C Mobile Web Best Practices Working Group"; check it is well descriptive of the content

This page raised 11 warnings

  1. The page has text/html as a media type; that media type is not recommended for the Default Delivery Context.
    This test is related to the following Best Practices: CONTENT_FORMAT_SUPPORT (techniques) CONTENT_FORMAT_PREFERRED (techniques)
  2. The link to http://ready.mobi at line 45 column 0 targets a resource whose media type None is not supported by Default Delivery Context; the text of the link should make that clear.
    http://ready…
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  3. The link to http://dev.w3.org/cvsweb/2007/mobileok-ref/ at line 51 column 42 targets a resource whose media type None is not supported by Default Delivery Context; the text of the link should make that clear.
    …k to date in CVS at 
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  4. The link to mailto:public-bpwg-comments@w3.org at line 112 column 134 targets a resource with a scheme mailto not supported by Default Delivery Context; the text of the link should make that clear.
    …e send a message to 
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  5. The link to mailto:daniel.Appelquist@vodafone.com at line 143 column 32 targets a resource with a scheme mailto not supported by Default Delivery Context; the text of the link should make that clear.
    …ng Group Chairs are 
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  6. The link to mailto:jrabin@mtld.mobi at line 143 column 107 targets a resource with a scheme mailto not supported by Default Delivery Context; the text of the link should make that clear.
    …Appelquist and Jo Rab…
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  7. The link to mailto:mike@w3.org at line 144 column 17 targets a resource with a scheme mailto not supported by Default Delivery Context; the text of the link should make that clear.
    …Staff Contact is Michael(tm)…
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  8. The link to http://www.w3.org/blog/BPWG?tempskin=_rdf at line 190 column 5 targets a resource whose media type application/xml is not supported by Default Delivery Context; the text of the link should make that clear.
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  9. The link to http://www.w3.org/blog/BPWG?tempskin=_rdf&disp=comments at line 191 column 5 targets a resource whose media type application/xml is not supported by Default Delivery Context; the text of the link should make that clear.
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  10. The link to http://www.w3.org/blog/BPWG?tempskin=_atom at line 195 column 5 targets a resource whose media type application/atom+xml is not supported by Default Delivery Context; the text of the link should make that clear.
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)
  11. The link to http://www.w3.org/blog/BPWG?tempskin=_atom&disp=comments at line 196 column 5 targets a resource whose media type application/atom+xml is not supported by Default Delivery Context; the text of the link should make that clear.
    This test is related to the following Best Practices: LINK_TARGET_FORMAT (techniques)

The following information can help assess the conformance of the page to the Best Practices

  1. The page uses style sheets; check that it can be used in a device where style sheets aren't available.
  2. The markup contains 10 percent of unneeded whitespaces summing up to 918 extraneous characters.

Non-Applicable

The following information shows which Best Practices were not applicable to the said page. ...

Labels: , ,

0 Comments:

Post a Comment