Standards Compliancy


Cascading Style Sheet (CSS) Compliancy

I keep this website compliant to Cascading Style Sheet (CSS) standards using the automated checking service provided by the World Wide Web Consortium (W3C) at http://jigsaw.w3.org/css-validator/. This has been very useful in detecting errors and for suggesting improvements in cross browser compatibility of my pages. In the footer of every page on this site, there is a link labelled 'Test CSS'. This refers the currently displayed page to this testing service and gives the results within a few seconds. The URL of this referral service is http://jigsaw.w3.org/css-validator/check/referer. All of the pages on this site should pass and therefore be eligible to display this W3C logo:

CSS Compliancy Logo

Hyper Text Markup Language (HTML) Compliancy

I keep this website compliant to HTML 4.01 (strict) standards using the automated checking service provided by the World Wide Web Consortium (W3C) at http://validator.w3.org/. This has been very useful in detecting errors in my HTML code. In the footer of every page on this site, there is a link labelled 'Test HTML'. This refers the currently displayed page to this testing service and gives the results within a few seconds. The URL used for this referral service is http://validator.w3.org/check?uri=<URI>, where <URI> is replaced by the full webpage address. All of the pages on this site should pass the test for HTML 4.01 (strict) and therefore be eligible to display this W3C logo:

HTML 4.01 (strict) Compliancy Logo

The W3C Link Checker

From time to time I check the links on some of my pages using the W3C Link Checker at http://validator.w3.org/checklink/. These pages include the sitemap page, the links page and the cycletouring kit pages.



W3C Accessibility guidelines V1.0

In the future I would like to be able to claim compliancy against the W3C Accessability Guidelines V1.0. These 14 guidelines should each be considered when authoring a web page:

  1. Provide equivalent alternatives to auditory and visual content
  2. Don't rely on colour alone
  3. Use markup and style sheets and do so properly
  4. Clarify natural language use
  5. Create tables that transform gracefully
  6. Ensure that pages featuring new technologies transform gracefully
  7. Ensure user control of time-sensitive content changes
  8. Ensure direct accessibilty of embedded user interfaces
  9. Design for device-independence
  10. Use interim solutions
  11. Use W3C technologies and guidelines
  12. Provide context and orientation information
  13. Provide clear navigation mechanisms
  14. Ensure that documents are clear and simple

Depending on the level of compliancy that I achieve against the guidelines, I will be allowed to display one of the following W3C logos on each page:


Level A conformance icon, 
          W3C-WAI Web Content Accessibility Guidelines 1.0 Level Double-A conformance icon, 
          W3C-WAI Web Content Accessibility Guidelines 1.0 Level Triple-A conformance icon, 
          W3C-WAI Web Content Accessibility Guidelines 1.0

© Copyright  Piers Pettman - This page last updated 08 July 2006
Accessibility |  Test HTML |  Test CSS |  Home |  Site Map

W3C CSS Compliancy Logo W3C HTML 4.01 (Strict) Compliancy Logo