"Ciel ! Ma page invalide" or how to be caught!

Author(s) and publish date

By:
Published:
Skip to 20 comments

We are often recommending Web developers to create good Web pages and to follow Web standards. But do we stand by our own criterias of quality? How much do we eat our own dog food? So we ran the Log Validator script recently on the whole QA Web site and we found out that we were invalid! Time to apply our own little method : Improve the quality of the Web site step by step.

Results for module basic : HTML Validation

Here are the 630 most popular documents overall for the W3C QA Space.

Results for module HTMLValidator

Here are the 4 most popular invalid document(s) that I could find in the logs for the W3C QA Space.

Rank Hits #Error(s) Address
20 42 18 http://www.w3.org/QA/2006/01/failed_commitments.html
63 15 3 http://www.w3.org/QA/WG/2004/06/QAH-issues
86 9 1 http://www.w3.org/QA/Tools/LogValidator/Manual-Modules

Conclusion : You asked for 100 invalid HTML document but I could only find 4 by processing (all the) 100 document(s) in your logs. This means that about 4% of your most popular documents were invalid. NOTE: I stopped after processing 100 documents: Maybe you could set MaxDocuments to a higher value?

Here are the 49 most popular document(s) with broken links that I could find in the logs for the W3C QA Space.

Rank Hits #Error(s) Address
6 327 4 http://www.w3.org/QA/
9 199 1 http://www.w3.org/QA/2002/04/valid-dtd-list.html
11 110 1 http://www.w3.org/QA/Activity.html
16 68 1 http://www.w3.org/QA/IG/
18 65 1 http://www.w3.org/QA/Library/
22 52 1 http://www.w3.org/QA/2005/08/specgl-errata
24 48 11 http://www.w3.org/QA/TheMatrix
25 47 1 http://www.w3.org/QA/Tools/qa-dev
28 44 1 http://www.w3.org/QA/2006/03/minutes_of_qa_ig_f2f_at_the_w3.html
30 43 1 http://www.w3.org/QA/Tools/LogValidator/
31 43 1 http://www.w3.org/QA/2006/02/buy_standards_compliant_web_si.html
32 42 1 http://www.w3.org/QA/WG/qaframe-primer
33 42 1 http://www.w3.org/QA/2006/02/ruby_annotation_to_change_the.html
34 42 1 http://www.w3.org/QA/2006/01/failed_commitments.html
36 41 1 http://www.w3.org/QA/2006/02/content_negotiation.html
37 41 3 http://www.w3.org/QA/archive/w3cqa_news/technology_101/
38 41 1 http://www.w3.org/QA/2006/03/
40 41 3 http://www.w3.org/QA/2006/02/
41 41 3 http://www.w3.org/QA/archive/technology/css/
42 41 1 http://www.w3.org/QA/WG/
43 41 2 http://www.w3.org/QA/archive/technology/http/
45 40 3 http://www.w3.org/QA/archive/web_spotting/opinions_editorial/
46 39 1 http://www.w3.org/QA/Tips/iso-date
50 37 1 http://www.w3.org/QA/2002/04/Web-Quality
52 36 2 http://www.w3.org/QA/Tips/use-links
53 36 4 http://www.w3.org/QA/archive/web_spotting/tutorials/
54 35 9 http://www.w3.org/QA/archive/w3cqa_news/publications/
55 35 7 http://www.w3.org/QA/archive/w3cqa_news/tools/
56 33 2 http://www.w3.org/QA/2006/01/quality_assurance_interest_gro.html
57 33 5 http://www.w3.org/QA/archive/w3cqa_news/qaig_life/
58 32 4 http://www.w3.org/QA/archive/w3cqa_news/meetings/
60 32 1 http://www.w3.org/QA/WG/2005/01/test-faq
61 32 5 http://www.w3.org/QA/archive/technology/html/
63 28 1 http://www.w3.org/QA/Agenda/
67 25 1 http://www.w3.org/QA/Tools/LogValidator
73 21 1 http://www.w3.org/QA/2002/09/Step-by-step
75 20 1 http://www.w3.org/QA/2002/07/WebAgency-Requirements
77 18 1 http://www.w3.org/QA/2004/08/QAH-charter.html
78 18 1 http://www.w3.org/QA/Activity
80 17 1 http://www.w3.org/QA/IG/charter.html
84 15 1 http://www.w3.org/QA/WG
85 15 1 http://www.w3.org/QA/WG/2004/06/QAH-issues
86 15 1 http://www.w3.org/QA/Tips/uri-manage
87 14 2 http://www.w3.org/QA/2004/08/QAH-qapd-text.html
89 13 1 http://www.w3.org/QA/Library
91 13 11 http://www.w3.org/QA/WG/qawg-issues-html
96 13 1 http://www.w3.org/QA/IG
97 13 1 http://www.w3.org/QA/Tools/qa-dev/
100 12 4 http://www.w3.org/QA/WG/qaframe-spec-extech

Conclusion : I had to check 100 document(s) in order to find 49 HTML documents with broken links. This means that about 49% of your most popular documents needs fixing. NOTE: I stopped after processing 100 documents: Maybe you could set MaxDocuments to a higher value?

Next Step? Fixing!

We will run again this program every month and see if we can respect what we predicate. When there will be issues which seems more difficult to overcome, we will explain the solution we have found and adopted to solve them.

Related RSS feed

Comments (20)

Comments for this post are closed.