Implementation report for the Semantic Frenzy Weblog


31 July 2006

Older Version(s):

This Version:
Latest Version:


Some changes have been made since the last test, completing some of the tasks that have been derived from the test results. Important remaining tasks are implementing accesskeys in some subpages.

Kept in mind: For future content creation (i.e. blog postings):

Changes in the markup:

Changes in the weblog system's settings


Results of checking the web site with the Best Practices

Please indicate whether the implementation complies with the Best Practice, doesn't comply, complies partially, or whether the Best Practice doesn't apply; please indicate in the comments column any feedback or remarks that needs to accompany these.

Best Practice Pass Fail Partial N/A Comments
1. [THEMATIC_CONSISTENCY] Ensure that content provided by accessing a URI yields a thematically coherent experience when accessed from different devices. X

Postnames are used for permalinks in syntax like:
2. [CAPABILITIES] Exploit device capabilities to provide an enhanced user experience.

3. [DEFICIENCIES] Take reasonable steps to work around deficient implementations.

4. [TESTING] Carry out testing on actual devices as well as emulators. X

Graphical browsers:
  • IE
  • Gecko (Firefox, Mozilla)
  • Opera for desktop
  • Opera for desktop with small-screen-rendering (there are some rendering differences to Opera Mini although Opera Mini uses SSR, too)
  • Lynx
  • (Poodle predictor, which simulates googlebot)
Mobile browsers:
  • Siemens S65 (with Openwave
  • Opera Mini
  • Opera Mini 2
  • Siemens S65 (with SMTK Emulator)
  • Opera Mini and Opera Mini 2, both on SMTK Emulator
5. [URIS] Keep the URIs of site entry points short. X

6. [NAVBAR] Provide only minimal navigation at the top of the page. X

7. [BALANCE] Take into account the trade-off between having too many links on a page and asking the user to follow too many links to reach what they are looking for.

8. [NAVIGATION] Provide consistent navigation mechanisms. X

9. [ACCESS_KEYS] Assign access keys to links in navigational menus and frequently accessed functionality.


Implemented partially. Starting page is complete; subpages with comments need implementation
10. [LINK_TARGET_ID] Clearly identify the target of each link.

11. [LINK_TARGET_FORMAT] Note the target file's format unless you know the device supports it. X

Done for internal links, in external resources the user will be informed if the link target is obvious not accessible (PDF, Flash, etc.)
12. [IMAGE_MAPS] Do not use image maps unless you know the device supports them effectively.

No image maps used so far
13. [POP_UPS] Do not cause pop-ups or other windows to appear and do not change the current window without informing the user. X

14. [AUTO_REFRESH] Do not create periodically auto-refreshing pages, unless you have informed the user and provided a means of stopping it. X

15. [REDIRECTION] Do not use markup to redirect pages automatically. Instead, configure the server to perform redirects by means of HTTP 3xx codes. X

16. [EXTERNAL_RESOURCES] Keep the number of externally linked resources to a minimum.

17. [SUITABLE] Ensure that content is suitable for use in a mobile context. X

18. [CLARITY] Use clear and simple language.


Since this is a weblog with strong technically oriented context, using a simple language is quite difficult. But I try.
19. [LIMITED] Limit content to what the user has requested.

20. [PAGE_SIZE_USABLE] Divide pages into usable but limited size portions. X

Wordpress is configured to show fewer posts on the start page.
21. [PAGE_SIZE_LIMIT] Ensure that the overall size of page is appropriate to the memory limitations of the device.


See above
22. [SCROLLING] Limit scrolling to one direction, unless secondary scrolling cannot be avoided. X

23. [CENTRAL_MEANING] Ensure that material that is central to the meaning of the page precedes material that is not.

24. [GRAPHICS_FOR_SPACING] Do not use graphics for spacing. X

25. [LARGE_GRAPHICS] Do not use images that cannot be rendered by the device. Avoid large or high resolution images except where critical information would otherwise be lost. X

26. [USE_OF_COLOR] Ensure that information conveyed with color is also available without color. X

27. [COLOR_CONTRAST] Ensure that foreground and background color combinations provide sufficient contrast. X

28. [BACKGROUND_IMAGE_READABILITY] When using background images make sure that content remains readable on the device. X

29. [PAGE_TITLE] Provide a short but descriptive page title. X

30. [NO_FRAMES] Do not use frames. X

31. [STRUCTURE] Use features of the markup language to indicate logical document structure. X

32. [TABLES_SUPPORT] Do not use tables unless the device is known to support them. X

33. [TABLES_NESTED] Do not use nested tables. X

34. [TABLES_LAYOUT] Do not use tables for layout. X

35. [TABLES_ALTERNATIVES] Where possible, use an alternative to tabular presentation.

no tabular presentation used
36. [NON-TEXT_ALTERNATIVES] Provide a text equivalent for every non-text element. X

37. [OBJECTS_OR_SCRIPT] Do not rely on embedded objects or script. X

38. [IMAGES_SPECIFY_SIZE] Specify the size of images in markup, if they have an intrinsic size.

Will be used in the future
39. [IMAGES_RESIZING] Resize images at the server, if they have an intrinsic size.


40. [VALID_MARKUP] Create documents that validate to published formal grammars. X

Valid XHTML Basic
41. [MEASURES] Do not use pixel measures and do not use absolute units in markup language attribute values and style sheet property values. X

42. [STYLE_SHEETS_USE] Use style sheets to control layout and presentation, unless the device is known not to support them. X

If a browser uses media:screen instead of media:handheld (like IE for Pocket PC or MiniMozilla) the user will have a good user experience, too.
43. [STYLE_SHEETS_SUPPORT] Organize documents so that if necessary they may be read without style sheets. X

Markup is used semantically correct. Moreover it can be validated with the "outline" option resulting in a display of the content structure
44. [STYLE_SHEETS_SIZE] Keep style sheets small. X

  • Stylesheet screen: 3,29kb
  • Stylesheet print: 517 bytes
  • Stylesheet handheld: 292 bytes
45. [MINIMIZE] Use terse, efficient markup. X

The whole XHTML markup is hand-crafted ;)
46. [CONTENT_FORMAT_SUPPORT] Send content in a format that is known to be supported by the device. X

  • Document format is XHTMl Basic
  • MIME type is defined as "application/xhtml+xml" in the markup, but is being sent as "text/html" by the server
47. [CONTENT_FORMAT_PREFERRED] Where possible, send content in a preferred format. X

See above
48. [CHARACTER_ENCODING_SUPPORT] Ensure that content is encoded using a character encoding that is known to be supported by the device. X

utf-8, tested with all devices listed in 4.
49. [CHARACTER_ENCODING_USE] Indicate in the response the character encoding being used. X

50. [ERROR_MESSAGES] Provide informative error messages and a means of navigating away from an error message back to useful information.

Actually only error messages from an older page in german language is displayed. this will be changed in the future.
51. [COOKIES] Do not rely on cookies being available. X

52. [CACHING] Provide caching information in HTTP responses.

Will be implemented
53. [FONTS] Do not rely on support of font related styling. X

54. [MINIMIZE_KEYSTROKES] Keep the number of keystrokes to a minimum. X

55. [AVOID_FREE_TEXT] Avoid free text entry where possible. X

some contents of the comment's form (name, e-mail adress and website URl) can be saved in a cookie if a UA supports them.
56. [PROVIDE_DEFAULTS] Provide pre-selected default values where possible. X

See above
57. [DEFAULT_INPUT_MODE] Specify a default text entry mode, language and/or input format, if the device is known to support it.

See above
58. [TAB_ORDER] Create a logical order through links, form controls and objects. ?

Tabindex is used consistently but not supported by XHTML Basic (according to the W3 Validator)
59. [CONTROL_LABELLING] Label all form controls appropriately and explicitly associate labels with form controls. X

60. [CONTROL_POSITION] Position labels so they lay out properly in relation to the form controls they refer to. X

Mirko Prugovecki
newsletter (a)