WHATWG Wiki - User contributions [en]

Testsuite

2009-01-29T10:39:28Z

Takkaria: add easy reviewing to list of requirements

Existing tests URI: http://dev.w3.org/html5/tests/

== Requirements ==

* Each test needs a "reviewed" marker of some sort
* It must be easy to find tests where the spec has changed under them
* The barrier to contribution must be as low as possible
* Testcases should have somewhat stable URIs
* If test can be done using JavaScript preferably require it to be in JavaScript so engines can be more efficiently tested (i.e. automated).
* It must be easy to review tests

== Non-requirements ==

* There does not need to be a single consistent test harness for the whole of HTML5. (When sections can be tested in isolation, each section should use a test harness that is suited to that section's testing requirements. E.g. there is little value in fitting canvas tests and parser tests into the same framework, and it may add a lot of complexity.)

== Existing tests ==
* [http://samples.msdn.microsoft.com/ietestcenter/ IE's tests]
* [http://tc.labs.opera.com/html/ Opera's tests]
* [http://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit's tests]
* [http://philip.html5.org/tests/canvas/suite/tests/ Philip's canvas tests]
* [http://hixie.ch/tests/adhoc/html/ Hixie's ad-hoc tests]
* [http://lachy.id.au/dev/markup/tests/html5/ Lachlan's tests]
* [http://hg.gsnedders.com/php-html-5-direct/file/tip/tests/numbersTest gsnedders' number parsing tests]
* [http://simon.html5.org/test/html/ zcorpan's tests]
* [http://code.google.com/p/html5lib/source/browse/trunk/testdata/ html5lib tests]
* [http://hsivonen.iki.fi/test/moz/video-selection/ hsivonen's video tests]

Testsuite

2009-01-27T16:34:16Z

Takkaria: /* Existing tests */ more tests

Existing tests URI: http://dev.w3.org/html5/tests/

== Requirements ==

* Each test needs a "reviewed" marker of some sort
* It must be easy to find tests where the spec has changed under them
* The barrier to contribution must be as low as possible
* Testcases should have somewhat stable URIs
* If test can be done using JavaScript preferably require it to be in JavaScript so engines can be more efficiently tested (i.e. automated).

== Non-requirements ==

* There does not need to be a single consistent test harness for the whole of HTML5. (When sections can be tested in isolation, each section should use a test harness that is suited to that section's testing requirements. E.g. there is little value in fitting canvas tests and parser tests into the same framework, and it may add a lot of complexity.)

== Existing tests ==
* [http://samples.msdn.microsoft.com/ietestcenter/ IE's tests]
* [http://tc.labs.opera.com/html/ Opera's tests]
* [http://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit's tests]
* [http://philip.html5.org/tests/canvas/suite/tests/ Philip's canvas tests]
* [http://hixie.ch/tests/adhoc/html/ Hixie's ad-hoc tests]
* [http://lachy.id.au/dev/markup/tests/html5/ Lachlan's tests]
* [http://hg.gsnedders.com/php-html-5-direct/file/tip/tests/numbersTest gsnedders' number parsing tests]
* [http://simon.html5.org/test/html/ zcorpan's tests]
* [http://code.google.com/p/html5lib/source/browse/trunk/testdata/ html5lib tests]
* [http://hsivonen.iki.fi/test/moz/video-selection/ hsivonen's video tests]

Testsuite

2009-01-27T16:17:52Z

Takkaria: Add more testcase links

Existing tests URI: http://dev.w3.org/html5/tests/

== Requirements ==

* Each test needs a "reviewed" marker of some sort
* It must be easy to find tests where the spec has changed under them
* The barrier to contribution must be as low as possible
* Testcases should have somewhat stable URIs
* If test can be done using JavaScript preferably require it to be in JavaScript so engines can be more efficiently tested (i.e. automated).

== Non-requirements ==

* There does not need to be a single consistent test harness for the whole of HTML5. (When sections can be tested in isolation, each section should use a test harness that is suited to that section's testing requirements. E.g. there is little value in fitting canvas tests and parser tests into the same framework, and it may add a lot of complexity.)

== Existing tests ==
* [http://samples.msdn.microsoft.com/ietestcenter/ IE's tests]
* [http://tc.labs.opera.com/html/ Opera's tests]
* [http://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit's tests]
* [http://philip.html5.org/tests/canvas/suite/tests/ Philip's canvas tests]
* [http://hixie.ch/tests/adhoc/html/ Hixie's ad-hoc tests]
* [http://code.google.com/p/html5lib/source/browse/trunk/testdata/ html5lib tests]

Testsuite

2009-01-27T16:06:24Z

Takkaria: Add links to existing tests

Testsuite

2009-01-27T15:57:35Z

Takkaria: add initial requirements page

Parser tests

2008-07-10T11:52:36Z

Takkaria: Try to make the parser tests page a bit more readable, and make spaces more obvious using <tt>.

=Parser Tests=

This page documents the unit-test format(s) being used for implementations of the HTML5 parsing spec. The aim is to produce implementation-independent, self-describing tests that can be shared between any groups working on these technologies.

==Tokenizer Tests==
The test format is [http://www.json.org/ JSON]. This has the advantage that the syntax allows backward-compatible extensions to the tests and the disadvantage that it is relatively verbose.

===Basic Structure===

{"tests": [

{"description":"Test description",
"input":"input_string",
"output":[expected_output_tokens]},
"contentModelFlags":[content_model_flags],
"lastStartTag":last_start_tag,
"ignoreErrorOrder":ignore_error_order
]}

<tt>description</tt>, <tt>input</tt> and <tt>output</tt> are always present. The other values are optional.

<tt>input_string</tt> is a string literal containing the input string to pass to the tokenizer.

<tt>expected_output_tokens</tt> is a list of tokens, ordered with the first produced by the tokenizer the first (leftmost) in the list. The list must mach the '''complete''' list of tokens that the tokenizer should produce. Valid tokens are:

["DOCTYPE", name, public_id, system_id, correctness]
["StartTag", name, {attributes}'', true'']
["StartTag", name, {attributes}]
["EndTag", name]
["Comment", data]
["Character", data]
"ParseError"

<tt>public_id</tt> and <tt>system_id</tt> are either strings or <tt>null</tt>. <tt>correctness</tt> is either <tt>true</tt> or <tt>false</tt>; <tt>true</tt> corresponds to the force-quirks flag being false, and vice-versa.

When the self-closing flag is set, the <tt>StartTag</tt> array has <tt>true</tt> as its fourth entry. When the flag is not set, the array has only three entries for backwards compatibility.

<tt>content_model_flags</tt> is a list of strings from the set:
PCDATA
RCDATA
CDATA
PLAINTEXT
The test case applies when the tokenizer begins with its content model flag set to any of those values. If <tt>content_model_flags</tt> is omitted, it defaults to <tt>["PCDATA"]</tt>.

<tt>last_start_tag</tt> is a lowercase string that should be used as "the tag name of the last start tag token emitted" in the tokenizer algorithm. If it is omitted, it is treated as if "no start tag token has ever been emitted by this instance of the tokeniser".

<tt>ignore_error_order</tt> is a boolean value indicating that the order of <tt>ParseError</tt> tokens relative to other tokens in the output stream is unimportant, and implementations should ignore such differences between their output and <tt>expected_output_tokens</tt>. (This is used for errors emitted by the input stream preprocessing stage, since it is useful to test that code but it is undefined when the errors occur). If it is omitted, it defaults to <tt>false</tt>.

Multiple tests per file are allowed simply by adding more objects to the "tests" list.

All adjacent character tokens are coalesced into a single <tt>["Character", data]</tt> token.

=== Open Issues ===
* Is the format too verbose?
* Do we want to allow the test to pass if only a subset of the actual tokens emitted matches the expected_output_tokens list?

==Tree Construction Tests==

Each file containing tree construction tests consists of any number of tests separated by two newlines (LF) and a single newline before the end of the file. For instance:

<pre>[TEST]LF
LF
[TEST]LF
LF
[TEST]LF</pre>

Where [TEST] is the following format:

Each test must begin with a string "#data" followed by a newline (LF). All subsequent lines until a line that says "#errors" are the test data and must be passed to the system being tested unchanged, except with the final newline (on the last line) removed.

Then there must be a line that says "#errors". It must be followed by one line per parse error that a conformant checker would return. It doesn't matter what those lines are, although they can't be "#document-fragment", "#document", or empty, the only thing that matters is that there be the right number of parse errors.

Then there *may* be a line that says "#document-fragment", which must be followed by a newline (LF), followed by a string of characters that indicates the context element, followed by a newline (LF). If this line is present the "#data" must be parsed using the HTML fragment parsing algorithm with the context element as context.

Then there must be a line that says "#document", which must be followed by a dump of the tree of the parsed DOM. Each node must be represented by a single line. Each line must start with "| ", followed by two spaces per parent node that the node has before the root document node.
* Element nodes must be represented by a "<tt><</tt>" then the ''tag name string'' "<tt>></tt>", and all the attributes must be given, sorted lexicographically by UTF-16 code unit according to their ''attribute name string'', on subsequent nodes, as if they were children of the element node.
* Attribute nodes must have the ''attribute name string'', then an "=" sign, then the attribute value in double quotes (").
* Text nodes must be the string, in double quotes. Newlines aren't escaped.
* Comments must be "<tt><</tt>" then "<tt>!-- </tt>" then the data then "<tt> --></tt>".
* DOCTYPEs must be "<tt><!DOCTYPE </tt>" then the name then if either of the system id or public id is non-empty a space, public id in double-quotes, another space an the system id in double-quotes, and then in any case "<tt>></tt>".

The ''tag name string'' is the local name prefixed by a namespace designator. For the HTML namespace, the namespace designator is the empty string, i.e. there's no prefix. For the SVG namespace, the namespace designator is "svg ". For the MathML namespace, the namespace designator is "math ".

The ''attribute name string'' is the local name prefixed by a namespace designator. For no namespace, the namespace designator is the empty string, i.e. there's no prefix. For the XLink namespace, the namespace designator is "xlink ". For the XML namespace, the namespace designator is "xml ". For the XMLNS namespace, the namespace designator is "xmlns ".

If there is also a "#document-fragment" the bit following "#document" must be a representation of the HTML fragment serialization for the context element given by "#document-fragment".

For example:
<pre>
#data
OneTwo
#errors
3: Missing document type declaration
#document
| <html>
| <head>
| <body>
| 
| "One"
| 
| "Two"
</pre>

Tests can be found here: http://html5lib.googlecode.com/svn/trunk/testdata/tree-construction/

=== Open Issues ===
* should relax the order constraint?

Parser tests

2008-06-15T17:57:09Z

Takkaria: Update the documentation to make reference to the force-qurirks flag.

=Parser Tests=

This page documents the unit-test format(s) being used for implementations of the HTML5 parsing spec. The aim is to produce implementation-independent, self-describing tests that can be shared between any groups working on these technologies.

==Tokenizer Tests==
The test format is [http://www.json.org/ JSON]. This has the advantage that the syntax allows backward-compatible extensions to the tests and the disadvantage that it is relatively verbose.

===Basic Structure===

{"tests": [

{"description":"Test description",
"input":"input_string",
"output":[expected_output_tokens]},
"contentModelFlags":[content_model_flags],
"lastStartTag":last_start_tag,
"ignoreErrorOrder":ignore_error_order
]}

<tt>description</tt>, <tt>input</tt> and <tt>output</tt> are always present. The other values are optional.

<tt>input_string</tt> is a string literal containing the input string to pass to the tokenizer.

<tt>expected_output_tokens</tt> is a list of tokens, ordered with the first produced by the tokenizer the first (leftmost) in the list. The list must mach the '''complete''' list of tokens that the tokenizer should produce. Valid tokens are:

["DOCTYPE", name, public_id, system_id, correctness]
["StartTag", name, {attributes}'', true'']
["StartTag", name, {attributes}]
["EndTag", name]
["Comment", data]
["Character", data]
"ParseError"

<tt>public_id</tt> and <tt>system_id</tt> are either strings or <tt>null</tt>. <tt>correctness</tt> is either <tt>true</tt> or <tt>false</tt>; <tt>true</tt> corresponds to the force-quirks flag being false, and vice-versa.

When the self-closing flag is set, the <tt>StartTag</tt> array has <tt>true</tt> as its fourth entry. When the flag is not set, the array has only three entries for backwards compatibility.

<tt>content_model_flags</tt> is a list of strings from the set:
PCDATA
RCDATA
CDATA
PLAINTEXT
The test case applies when the tokenizer begins with its content model flag set to any of those values. If <tt>content_model_flags</tt> is omitted, it defaults to <tt>["PCDATA"]</tt>.

<tt>last_start_tag</tt> is a lowercase string that should be used as "the tag name of the last start tag token emitted" in the tokenizer algorithm. If it is omitted, it is treated as if "no start tag token has ever been emitted by this instance of the tokeniser".

<tt>ignore_error_order</tt> is a boolean value indicating that the order of <tt>ParseError</tt> tokens relative to other tokens in the output stream is unimportant, and implementations should ignore such differences between their output and <tt>expected_output_tokens</tt>. (This is used for errors emitted by the input stream preprocessing stage, since it is useful to test that code but it is undefined when the errors occur). If it is omitted, it defaults to <tt>false</tt>.

Multiple tests per file are allowed simply by adding more objects to the "tests" list.

All adjacent character tokens are coalesced into a single <tt>["Character", data]</tt> token.

=== Open Issues ===
* Is the format too verbose?
* Do we want to allow the test to pass if only a subset of the actual tokens emitted matches the expected_output_tokens list?

==Tree Construction Tests==

Each file containing tree construction tests consists of any number of tests separated by two newlines (LF) and a single newline before the end of the file. For instance:

<pre>[TEST]LF
LF
[TEST]LF
LF
[TEST]LF</pre>

Where [TEST] is the following format:

Each test must begin with a string "#data" followed by a newline (LF). All subsequent lines until a line that says "#errors" are the test data and must be passed to the system being tested unchanged, except with the final newline (on the last line) removed.

Then there must be a line that says "#errors". It must be followed by one line per parse error that a conformant checker would return. It doesn't matter what those lines are, although they can't be "#document-fragment", "#document", or empty, the only thing that matters is that there be the right number of parse errors.

Then there *may* be a line that says "#document-fragment", which must be followed by a newline (LF), followed by a string of characters that indicates the context element, followed by a newline (LF). If this line is present the "#data" must be parsed using the HTML fragment parsing algorithm with the context element as context.

Then there must be a line that says "#document", which must be followed by a dump of the tree of the parsed DOM. Each node must be represented by a single line. Each line must start with "| ", followed by two spaces per parent node that the node has before the root document node. Element nodes must be represented by a "<" then the tag name then ">", and all the attributes must be given, sorted lexicographically by UTF-16 code unit, on subsequent nodes, as if they were children of the element node. Attribute nodes must have the attribute name, then an "=" sign, then the attribute value in double quotes ("). Text nodes must be the string, in double quotes. Newlines aren't escaped. Comments must be "<" then "!-- " then the data then " -->". DOCTYPEs must be "<!DOCTYPE " then the name then if either of the system id or public id is non-empty a space, public id in double-quotes, another space an the system id in double-quotes, and then in any case ">".

If there is also a "#document-fragment" the bit following "#document" must be a representation of the HTML fragment serialization for the context element given by "#document-fragment".

For example:
<pre>
#data
OneTwo
#errors
3: Missing document type declaration
#document
| <html>
| <head>
| <body>
| 
| "One"
| 
| "Two"
</pre>

Tests can be found here: http://html5lib.googlecode.com/svn/trunk/testdata/tree-construction/

=== Open Issues ===
* should relax the order constraint?

Longdesc usage

2007-08-14T12:23:37Z

Takkaria:

'''Current status''': Hixie gave another list of 100 URLs which I'm going to be looking at soon.

This is an analysis of how the <img longdesc=""> attribute is used in the wild, based on the list of 62 pages which used the attribute, available at:
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/pages/tagattr/img/longdesc

The document list is included at the end of this page, numbered. When referring to pages, I just use their number.

== Errors ==

* 3, 10, 27, 31, and 46 were redirects; I did not check the pages their pointed to.
* 22, 35, and 37 no longer have the string "longdesc" in them.

== Results ==

A large number of the pages were from Wikipedia (or other MediaWiki installations): 1, 2, 6, 9, 11, 17, 19, 21, 24, 25, 29, 30, 36, 43, 45, 54, and 59. MediaWiki has a way of using longdesc particular to itself. Ignoring MediaWiki results:

* 2 pages used longdesc="" (5, 42)
* 3 pages used longdesc="..." linking to an image of some description (41, 44, 56)
* 12 pages used longdesc="..." not as an URL, but as a human-readable description:
** 4 of which look like SEO attempts (13, 18, 48, 61)
** 3 of which used the same string as they used for alt text (7, 23, 53)
** 3 of which has different alt and longdesc text (16, 28, 52)
** 1 of which used the same string as they did for title="" (15)
** 1 of which used URL-escaped text (49)
** 1 of which is in Russian, which I don't understand (32)
* 20 pages used longdesc="..." as an URL:
** 11 of which point to a location the same as one pointed to with a link nearby (20, 33, 34, 38, 40, 47, 50, 55, 57, 58, 60)
** 4 of which are broken links (4, 14, 26, 57)
** 2 of which are valid links but seems not to comply with the spec (12, 39)
** 2 of which is a correct use of the element (51, 62)
** 1 of which seems to be better dealt with as a hyperlink rather than a longdesc attribute (8)

On 51, ironically, the only longdesc attribute is used on a link to an automated accessibility checker's website. 62 seems to serve up rather unhelpful text/plain one-liners for longdesc, claiming to be accessible made by a company that does accessible web design.

== Links list ==

1: http://fr.wikipedia.org/wiki/Francesco_Borromini 
2: http://en.wikipedia.org/wiki/Motivation 
3: http://www.schirmer.com/composers/schoenberg_essay.html 
4: http://www.huntingtonhousing.com 
5: http://osierra.com 
6: http://ru.wikipedia.org/wiki/%D0%98%D1%81%D1%82%D0%BE%D1%80%D0%B8%D1%8F_%D0%90%D1%80%D0%BC%D0%B5%D0%BD%D0%B8%D0%B8 
7: http://www.norwalkoh.com/ 
8: http://www.domnowski.de/ 
9: http://de.wikipedia.org/wiki/Morscheid 
10: http://www.eng.rpi.edu 
11: http://en.wikipedia.org/wiki/Transport_in_Yemen 
12: http://www.aclu-ia.org/ 
13: http://airbrush-tanning.us 
14: http://www.pr-photography.org/ 
15: http://www.shakedown.fi/ 
16: http://www.vds.org.uk 
17: http://it.wikipedia.org/wiki/Voghiera 
18: http://www.babylaundryboutique.com/ 
19: http://de.wikipedia.org/wiki/D%C3%A4nische_Sprache 
20: http://www.coastal-fisherman.com/ 
21: http://fr.wikipedia.org/wiki/Anthemius_de_Tralles 
22: http://www.hometown.aol.co.uk/thewoburnrally/ 
23: http://www.oblates.us/spiritual_directory.htm 
24: http://en.wikipedia.org/wiki/Sint_Maarten_national_football_team 
25: http://en.wikipedia.org/wiki/Long_Grove,_Iowa 
26: http://www.integracomunicaciones.com/ 
27: http://www.bayern-evangelisch.de/ 
28: http://www.almaprnjavorac.com 
29: http://en.wikipedia.org/wiki/Osage,_Iowa 
30: http://en.wikipedia.org/wiki/Bob_Menendez 
31: http://weatheroffice.ec.gc.ca/city/pages/qc-150_metric_e.html 
32: http://www.paralife.narod.ru 
33: http://www.jagdhof.com 
34: http://www.austria-lustenau.at/ 
35: http://www.expressrealestateschool.com 
36: http://de.wikipedia.org/wiki/Guckheim 
37: http://www.vivian-cat.narod.ru/ 
38: http://www.svirp.dk/ 
39: http://www.francedirect.net 
40: http://www.pointvue.com/cis/ 
41: http://www.arabicdancer.co.uk/ 
42: http://kepek.utcaigyorsulas.hu 
43: http://es.wikipedia.org/wiki/Tomatina 
44: http://www.stopitnow.com/ 
45: http://en.wikipedia.org/wiki/THEOS 
46: http://www.wirtschaft.fh-gelsenkirchen.de/ 
47: http://www.sannong.com 
48: http://www.integrated-robotics.com 
49: http://www.waveney.gov.uk/ 
50: http://www.libraryspot.com/ 
51: http://www.teachers.ash.org.au/aussieed/ 
52: http://www.webmeister.dk 
53: http://www.magicdomico.com/ 
54: http://es.wikipedia.org/wiki/Azerbaiy%C3%A1n 
55: http://www.puntoluce.tv/ 
56: http://www.bss-ev.de/ 
57: http://www.lowvillegolf.com/ 
58: http://www.brandunity.com/ 
59: http://en.wikipedia.org/wiki/Minos 
60: http://www.cotondetulear.be/ 
61: http://www.granhotelguadalpinbanus.com 
62: http://www.libertas-solutions.com

Longdesc usage

2007-08-12T19:55:40Z

Takkaria:

This is an analysis of how the <img longdesc=""> attribute is used in the wild, based on the list of 62 pages which used the attribute, available at:
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/pages/tagattr/img/longdesc

The document list is included at the end of this page, numbered. When referring to pages, I just use their number.

== Errors ==

* 3, 10, 27, 31, and 46 were redirects; I did not check the pages their pointed to.
* 22, 35, and 37 no longer have the string "longdesc" in them.

== Results ==

A large number of the pages were from Wikipedia (or other MediaWiki installations): 1, 2, 6, 9, 11, 17, 19, 21, 24, 25, 29, 30, 36, 43, 45, 54, and 59. MediaWiki has a way of using longdesc particular to itself. Ignoring MediaWiki results:

* 2 pages used longdesc="" (5, 42)
* 3 pages used longdesc="..." linking to an image of some description (41, 44, 56)
* 12 pages used longdesc="..." not as an URL, but as a human-readable description:
** 4 of which look like SEO attempts (13, 18, 48, 61)
** 3 of which used the same string as they used for alt text (7, 23, 53)
** 3 of which has different alt and longdesc text (16, 28, 52)
** 1 of which used the same string as they did for title="" (15)
** 1 of which used URL-escaped text (49)
** 1 of which is in Russian, which I don't understand (32)
* 20 pages used longdesc="..." as an URL:
** 11 of which point to a location the same as one pointed to with a link nearby (20, 33, 34, 38, 40, 47, 50, 55, 57, 58, 60)
** 4 of which are broken links (4, 14, 26, 57)
** 2 of which are valid links but seems not to comply with the spec (12, 39)
** 2 of which is a correct use of the element (51, 62)
** 1 of which seems to be better dealt with as a hyperlink rather than a longdesc attribute (8)

On 51, ironically, the only longdesc attribute is used on a link to an automated accessibility checker's website. 62 seems to serve up rather unhelpful text/plain one-liners for longdesc, claiming to be accessible made by a company that does accessible web design.

== Links list ==

1: http://fr.wikipedia.org/wiki/Francesco_Borromini 
2: http://en.wikipedia.org/wiki/Motivation 
3: http://www.schirmer.com/composers/schoenberg_essay.html 
4: http://www.huntingtonhousing.com 
5: http://osierra.com 
6: http://ru.wikipedia.org/wiki/%D0%98%D1%81%D1%82%D0%BE%D1%80%D0%B8%D1%8F_%D0%90%D1%80%D0%BC%D0%B5%D0%BD%D0%B8%D0%B8 
7: http://www.norwalkoh.com/ 
8: http://www.domnowski.de/ 
9: http://de.wikipedia.org/wiki/Morscheid 
10: http://www.eng.rpi.edu 
11: http://en.wikipedia.org/wiki/Transport_in_Yemen 
12: http://www.aclu-ia.org/ 
13: http://airbrush-tanning.us 
14: http://www.pr-photography.org/ 
15: http://www.shakedown.fi/ 
16: http://www.vds.org.uk 
17: http://it.wikipedia.org/wiki/Voghiera 
18: http://www.babylaundryboutique.com/ 
19: http://de.wikipedia.org/wiki/D%C3%A4nische_Sprache 
20: http://www.coastal-fisherman.com/ 
21: http://fr.wikipedia.org/wiki/Anthemius_de_Tralles 
22: http://www.hometown.aol.co.uk/thewoburnrally/ 
23: http://www.oblates.us/spiritual_directory.htm 
24: http://en.wikipedia.org/wiki/Sint_Maarten_national_football_team 
25: http://en.wikipedia.org/wiki/Long_Grove,_Iowa 
26: http://www.integracomunicaciones.com/ 
27: http://www.bayern-evangelisch.de/ 
28: http://www.almaprnjavorac.com 
29: http://en.wikipedia.org/wiki/Osage,_Iowa 
30: http://en.wikipedia.org/wiki/Bob_Menendez 
31: http://weatheroffice.ec.gc.ca/city/pages/qc-150_metric_e.html 
32: http://www.paralife.narod.ru 
33: http://www.jagdhof.com 
34: http://www.austria-lustenau.at/ 
35: http://www.expressrealestateschool.com 
36: http://de.wikipedia.org/wiki/Guckheim 
37: http://www.vivian-cat.narod.ru/ 
38: http://www.svirp.dk/ 
39: http://www.francedirect.net 
40: http://www.pointvue.com/cis/ 
41: http://www.arabicdancer.co.uk/ 
42: http://kepek.utcaigyorsulas.hu 
43: http://es.wikipedia.org/wiki/Tomatina 
44: http://www.stopitnow.com/ 
45: http://en.wikipedia.org/wiki/THEOS 
46: http://www.wirtschaft.fh-gelsenkirchen.de/ 
47: http://www.sannong.com 
48: http://www.integrated-robotics.com 
49: http://www.waveney.gov.uk/ 
50: http://www.libraryspot.com/ 
51: http://www.teachers.ash.org.au/aussieed/ 
52: http://www.webmeister.dk 
53: http://www.magicdomico.com/ 
54: http://es.wikipedia.org/wiki/Azerbaiy%C3%A1n 
55: http://www.puntoluce.tv/ 
56: http://www.bss-ev.de/ 
57: http://www.lowvillegolf.com/ 
58: http://www.brandunity.com/ 
59: http://en.wikipedia.org/wiki/Minos 
60: http://www.cotondetulear.be/ 
61: http://www.granhotelguadalpinbanus.com 
62: http://www.libertas-solutions.com

Longdesc usage

2007-08-12T19:44:01Z

Takkaria:

This is an analysis of how the <img longdesc=""> attribute is used in the wild, based on the list of 62 pages which used the attribute, available at:
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/pages/tagattr/img/longdesc

The document list is included at the end of this page, numbered. When referring to pages, I just use their number.

== Errors ==

* 3, 10, 27, 31, and 46 were redirects; I did not check the pages their pointed to.
* 22, 35, and 37 no longer have the string "longdesc" in them.

== Results ==

A large number of the pages were from Wikipedia (or other MediaWiki installations): 1, 2, 6, 9, 11, 17, 19, 21, 24, 25, 29, 30, 36, 43, 45, 54, and 59. MediaWiki has a way of using longdesc particular to itself. Ignoring MediaWiki results:

* 2 pages used longdesc="" (5, 42)
* 3 pages used longdesc="..." linking to an image of some description (41, 44, 56)
* 12 pages used longdesc="..." not as an URL, but as a human-readable description:
** 3 of which used the same string as they used for alt text (7, 23, 53)
** 3 of which look like SEO attempts (13, 18, 48, 61)
** 3 of which has different alt and longdesc text (16, 28, 52)
** 1 of which used the same string as they did for title="" (15)
** 1 of which used URL-escaped text (49)
** 1 of which is in Russian, which I don't understand (32)
* 20 pages used longdesc="..." as an URL:
** 11 of which point to a location the same as one pointed to with a link nearby (20, 33, 34, 38, 40, 47, 50, 55, 57, 58, 60)
** 4 of which are broken links (4, 14, 26, 57)
** 2 of which are valid links but seems not to comply with the spec (12, 39)
** 2 of which is a correct use of the element (51, 62)
** 1 of which seems to be better dealt with as a hyperlink rather than a longdesc attribute (8)

On 51, ironically, the only longdesc attribute is used on a link to an automated accessibility checker's website. 62 seems to serve up rather unhelpful text/plain one-liners for longdesc, claiming to be accessible made by a company that does accessible web design.

== Links list ==

1: http://fr.wikipedia.org/wiki/Francesco_Borromini 
2: http://en.wikipedia.org/wiki/Motivation 
3: http://www.schirmer.com/composers/schoenberg_essay.html 
4: http://www.huntingtonhousing.com 
5: http://osierra.com 
6: http://ru.wikipedia.org/wiki/%D0%98%D1%81%D1%82%D0%BE%D1%80%D0%B8%D1%8F_%D0%90%D1%80%D0%BC%D0%B5%D0%BD%D0%B8%D0%B8 
7: http://www.norwalkoh.com/ 
8: http://www.domnowski.de/ 
9: http://de.wikipedia.org/wiki/Morscheid 
10: http://www.eng.rpi.edu 
11: http://en.wikipedia.org/wiki/Transport_in_Yemen 
12: http://www.aclu-ia.org/ 
13: http://airbrush-tanning.us 
14: http://www.pr-photography.org/ 
15: http://www.shakedown.fi/ 
16: http://www.vds.org.uk 
17: http://it.wikipedia.org/wiki/Voghiera 
18: http://www.babylaundryboutique.com/ 
19: http://de.wikipedia.org/wiki/D%C3%A4nische_Sprache 
20: http://www.coastal-fisherman.com/ 
21: http://fr.wikipedia.org/wiki/Anthemius_de_Tralles 
22: http://www.hometown.aol.co.uk/thewoburnrally/ 
23: http://www.oblates.us/spiritual_directory.htm 
24: http://en.wikipedia.org/wiki/Sint_Maarten_national_football_team 
25: http://en.wikipedia.org/wiki/Long_Grove,_Iowa 
26: http://www.integracomunicaciones.com/ 
27: http://www.bayern-evangelisch.de/ 
28: http://www.almaprnjavorac.com 
29: http://en.wikipedia.org/wiki/Osage,_Iowa 
30: http://en.wikipedia.org/wiki/Bob_Menendez 
31: http://weatheroffice.ec.gc.ca/city/pages/qc-150_metric_e.html 
32: http://www.paralife.narod.ru 
33: http://www.jagdhof.com 
34: http://www.austria-lustenau.at/ 
35: http://www.expressrealestateschool.com 
36: http://de.wikipedia.org/wiki/Guckheim 
37: http://www.vivian-cat.narod.ru/ 
38: http://www.svirp.dk/ 
39: http://www.francedirect.net 
40: http://www.pointvue.com/cis/ 
41: http://www.arabicdancer.co.uk/ 
42: http://kepek.utcaigyorsulas.hu 
43: http://es.wikipedia.org/wiki/Tomatina 
44: http://www.stopitnow.com/ 
45: http://en.wikipedia.org/wiki/THEOS 
46: http://www.wirtschaft.fh-gelsenkirchen.de/ 
47: http://www.sannong.com 
48: http://www.integrated-robotics.com 
49: http://www.waveney.gov.uk/ 
50: http://www.libraryspot.com/ 
51: http://www.teachers.ash.org.au/aussieed/ 
52: http://www.webmeister.dk 
53: http://www.magicdomico.com/ 
54: http://es.wikipedia.org/wiki/Azerbaiy%C3%A1n 
55: http://www.puntoluce.tv/ 
56: http://www.bss-ev.de/ 
57: http://www.lowvillegolf.com/ 
58: http://www.brandunity.com/ 
59: http://en.wikipedia.org/wiki/Minos 
60: http://www.cotondetulear.be/ 
61: http://www.granhotelguadalpinbanus.com 
62: http://www.libertas-solutions.com

Longdesc usage

2007-08-12T19:39:14Z

Takkaria: Second draft

This is an analysis of how the <img longdesc=""> attribute is used in the wild, based on the list of 62 pages which used the attribute, available at:
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/pages/tagattr/img/longdesc

The document list is included at the end of this page, numbered. When referring to pages, I just use their number.

== Errors ==

* 42 and 52 were inaccessible (I got 0 bytes back using curl)
* 3, 10, 27, 31, and 46 were redirects; I did not check the pages their pointed to.
* 22, 35, and 37 no longer have the string "longdesc" in them.

== Non-errors ==

A large number of the pages were from Wikipedia (or other MediaWiki installations): 1, 2, 6, 9, 11, 17, 19, 21, 24, 25, 29, 30, 36, 43, 45, 54, and 59. MediaWiki has a way of using longdesc particular to itself.

* 1 page used longdesc="" (5)
* 3 pages used longdesc="..." linking to an image of some description (41, 44, 56)
* 11 pages used longdesc="..." not as an URL, but as a human-readable description:
** 3 of which used the same string as they used for alt text (7, 23, 53)
** 1 of which used the same string as they did for title="" text (15)
** 1 of which had no alt text (28)
** 1 of which has an image with the text "Informing and Connecting people with Volunteering", the alt text "VDS Strapline 'Advancing the boundries and values of volunteering'", and the longdesc text "Changing the face of Volunteering in Scotland"
** 1 of which is in Russian, which I don't understand (32)
** 3 of which look like SEO attempts (13, 18, 48, 61)
** 1 of which used URL-escaped text (49)
* 20 pages used longdesc="..." as an URL:
** 11 of which point to a location the same as one pointed to with a link nearby (20, 33, 34, 38, 40, 47, 50, 55, 57, 58, 60)
** 4 of which are broken links (4, 14, 26, 57)
** 2 of which are valid links but seems not to comply with the spec (12, 39)
** 2 of which is a correct use of the element (51, 62)
** 1 of which seems to be better dealt with as a hyperlink rather than a longdesc attribute (8)

On 51, ironically, the only longdesc attribute is used on a link to an automated accessibility checker's website. 62 seems to serve up rather unhelpful text/plain one-liners as longdesc text.

== Links list ==

1: http://fr.wikipedia.org/wiki/Francesco_Borromini 
2: http://en.wikipedia.org/wiki/Motivation 
3: http://www.schirmer.com/composers/schoenberg_essay.html 
4: http://www.huntingtonhousing.com 
5: http://osierra.com 
6: http://ru.wikipedia.org/wiki/%D0%98%D1%81%D1%82%D0%BE%D1%80%D0%B8%D1%8F_%D0%90%D1%80%D0%BC%D0%B5%D0%BD%D0%B8%D0%B8 
7: http://www.norwalkoh.com/ 
8: http://www.domnowski.de/ 
9: http://de.wikipedia.org/wiki/Morscheid 
10: http://www.eng.rpi.edu 
11: http://en.wikipedia.org/wiki/Transport_in_Yemen 
12: http://www.aclu-ia.org/ 
13: http://airbrush-tanning.us 
14: http://www.pr-photography.org/ 
15: http://www.shakedown.fi/ 
16: http://www.vds.org.uk 
17: http://it.wikipedia.org/wiki/Voghiera 
18: http://www.babylaundryboutique.com/ 
19: http://de.wikipedia.org/wiki/D%C3%A4nische_Sprache 
20: http://www.coastal-fisherman.com/ 
21: http://fr.wikipedia.org/wiki/Anthemius_de_Tralles 
22: http://www.hometown.aol.co.uk/thewoburnrally/ 
23: http://www.oblates.us/spiritual_directory.htm 
24: http://en.wikipedia.org/wiki/Sint_Maarten_national_football_team 
25: http://en.wikipedia.org/wiki/Long_Grove,_Iowa 
26: http://www.integracomunicaciones.com/ 
27: http://www.bayern-evangelisch.de/ 
28: http://www.almaprnjavorac.com 
29: http://en.wikipedia.org/wiki/Osage,_Iowa 
30: http://en.wikipedia.org/wiki/Bob_Menendez 
31: http://weatheroffice.ec.gc.ca/city/pages/qc-150_metric_e.html 
32: http://www.paralife.narod.ru 
33: http://www.jagdhof.com 
34: http://www.austria-lustenau.at/ 
35: http://www.expressrealestateschool.com 
36: http://de.wikipedia.org/wiki/Guckheim 
37: http://www.vivian-cat.narod.ru/ 
38: http://www.svirp.dk/ 
39: http://www.francedirect.net 
40: http://www.pointvue.com/cis/ 
41: http://www.arabicdancer.co.uk/ 
42: http://kepek.utcaigyorsulas.hu 
43: http://es.wikipedia.org/wiki/Tomatina 
44: http://www.stopitnow.com/ 
45: http://en.wikipedia.org/wiki/THEOS 
46: http://www.wirtschaft.fh-gelsenkirchen.de/ 
47: http://www.sannong.com 
48: http://www.integrated-robotics.com 
49: http://www.waveney.gov.uk/ 
50: http://www.libraryspot.com/ 
51: http://www.teachers.ash.org.au/aussieed/ 
52: http://www.webmeister.dk 
53: http://www.magicdomico.com/ 
54: http://es.wikipedia.org/wiki/Azerbaiy%C3%A1n 
55: http://www.puntoluce.tv/ 
56: http://www.bss-ev.de/ 
57: http://www.lowvillegolf.com/ 
58: http://www.brandunity.com/ 
59: http://en.wikipedia.org/wiki/Minos 
60: http://www.cotondetulear.be/ 
61: http://www.granhotelguadalpinbanus.com 
62: http://www.libertas-solutions.com

Longdesc usage

2007-08-12T19:22:33Z

Takkaria: WIP, just so if the browser crashes I don't lose it

This is an analysis of how the <img longdesc=""> attribute is used in the wild, based on the list of 62 pages which used the attribute, available at:
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/pages/tagattr/img/longdesc

The document list is included at the end of this page, numbered. When referring to pages, I just use their number.

== Errors ==

* 42 and 52 were inaccessible (I got 0 bytes back using curl)
* 3, 10, 27, 31, and 46 were redirects; I did not check the pages their pointed to.
* 22, 35, and 37 no longer have the string "longdesc" in them.

== Non-errors ==

A large number of the pages were from Wikipedia (or other MediaWiki installations): 1, 2, 6, 9, 11, 17, 19, 21, 24, 25, 29, 30, 36, 43, 45, 54, and 59. MediaWiki has a way of using longdesc particular to itself.

* 1 page used longdesc="" (5)
* 3 pages used longdesc="..." linking to an image of some description (41, 44, 56)
* 8 pages used longdesc="..." not as an URL, but as a human-readable description:
** 3 of which used the same string as they used for alt text (7, 23, 53)
** 1 of which used the same string as they did for title="" text (15)
** 1 of which had no alt text (28)
** 2 of which look like SEO attempts (48, 61)
** 1 of which used URL-escaped text (49)
* x pages used longdesc="..." as an URL:
** 9 of which point to a location the same as one pointed to with a link nearby (20 33 34 38 47 50 55 57 60)
** 3 of which are broken links (4, 14, 57)

1: http://fr.wikipedia.org/wiki/Francesco_Borromini 
2: http://en.wikipedia.org/wiki/Motivation 
3: http://www.schirmer.com/composers/schoenberg_essay.html 
4: http://www.huntingtonhousing.com 
5: http://osierra.com 
6: http://ru.wikipedia.org/wiki/%D0%98%D1%81%D1%82%D0%BE%D1%80%D0%B8%D1%8F_%D0%90%D1%80%D0%BC%D0%B5%D0%BD%D0%B8%D0%B8 
7: http://www.norwalkoh.com/ 
8: http://www.domnowski.de/ 
9: http://de.wikipedia.org/wiki/Morscheid 
10: http://www.eng.rpi.edu 
11: http://en.wikipedia.org/wiki/Transport_in_Yemen 
12: http://www.aclu-ia.org/ 
13: http://airbrush-tanning.us 
14: http://www.pr-photography.org/ 
15: http://www.shakedown.fi/ 
16: http://www.vds.org.uk 
17: http://it.wikipedia.org/wiki/Voghiera 
18: http://www.babylaundryboutique.com/ 
19: http://de.wikipedia.org/wiki/D%C3%A4nische_Sprache 
20: http://www.coastal-fisherman.com/ 
21: http://fr.wikipedia.org/wiki/Anthemius_de_Tralles 
22: http://www.hometown.aol.co.uk/thewoburnrally/ 
23: http://www.oblates.us/spiritual_directory.htm 
24: http://en.wikipedia.org/wiki/Sint_Maarten_national_football_team 
25: http://en.wikipedia.org/wiki/Long_Grove,_Iowa 
26: http://www.integracomunicaciones.com/ 
27: http://www.bayern-evangelisch.de/ 
28: http://www.almaprnjavorac.com 
29: http://en.wikipedia.org/wiki/Osage,_Iowa 
30: http://en.wikipedia.org/wiki/Bob_Menendez 
31: http://weatheroffice.ec.gc.ca/city/pages/qc-150_metric_e.html 
32: http://www.paralife.narod.ru 
33: http://www.jagdhof.com 
34: http://www.austria-lustenau.at/ 
35: http://www.expressrealestateschool.com 
36: http://de.wikipedia.org/wiki/Guckheim 
37: http://www.vivian-cat.narod.ru/ 
38: http://www.svirp.dk/ 
39: http://www.francedirect.net 
40: http://www.pointvue.com/cis/ 
41: http://www.arabicdancer.co.uk/ 
42: http://kepek.utcaigyorsulas.hu 
43: http://es.wikipedia.org/wiki/Tomatina 
44: http://www.stopitnow.com/ 
45: http://en.wikipedia.org/wiki/THEOS 
46: http://www.wirtschaft.fh-gelsenkirchen.de/ 
47: http://www.sannong.com 
48: http://www.integrated-robotics.com 
49: http://www.waveney.gov.uk/ 
50: http://www.libraryspot.com/ 
51: http://www.teachers.ash.org.au/aussieed/ 
52: http://www.webmeister.dk 
53: http://www.magicdomico.com/ 
54: http://es.wikipedia.org/wiki/Azerbaiy%C3%A1n 
55: http://www.puntoluce.tv/ 
56: http://www.bss-ev.de/ 
57: http://www.lowvillegolf.com/ 
58: http://www.brandunity.com/ 
59: http://en.wikipedia.org/wiki/Minos 
60: http://www.cotondetulear.be/ 
61: http://www.granhotelguadalpinbanus.com 
62: http://www.libertas-solutions.com