- From: Simon Pieters <zcorpan@gmail.com>
- Date: Fri, 08 Jun 2007 06:20:04 +0200
- To: joeclark@fawny.org
- Cc: www-archive@w3.org
Hi Joe,
FWIW. I have a few comments on the 2007-06-07 draft of WCAG Samurai Errata
for WCAG 1.0.
Use those only if Unicode, or another declared character encoding,
Regardless of used character encoding, you can always use any Unicode
character by using character references in HTML. Therefore, I suggest
removing ", or another declared character encoding,".
You may use any version of CSS.
Should be "... level of CSS.".
When a page has translations available, link rel="alternate translation"
must be used, with appropriate href to the translated page."
Why isn't this <link rel="alternate" hreflang="...">? "translation" is not
a predefined rel keyword in HTML. (According to HTML5, the combination
rel=alternate and hreflang means translation. According to HTML4, the
combination of rel=alternate and lang means translation.)
You may use ... your own custom-written XHTML document type.
Why are custom DTDs allowed? Isn't it better to say that validation errors
due to <embed> elements can be ignored? Or have people use HTML5 if they
want to use <embed>? Allowing any custom DTD basically removes the
requirement to use conforming markup.
HTH,
--
Simon Pieters
Received on Friday, 8 June 2007 04:20:08 UTC