Comments on Developers' Guide to Features of Web Accessibility Evaluation Tools

The following are items I noticed from the i18n point of view while 
reading http://www.w3.org/TR/2014/WD-WAET-20140724/

I'm not raising tracker items for these, since the document is still 
very new, and i don't think we need to formally track the comments at 
this point.

2.1.2 Content encoding and content language
"Furthermore, web content can be transmitted using different character 
encodings and sets (like ISO-8859-1, UTF-8, UTF-16, etc.), which demands 
from the evaluation tools the capacity to handle them."

HTML5 treats iso 8859-1 as Windows-1252, so maybe better to replace with 
the latter. However, with HTML5 there is a strong push to abandon legacy 
encodings and just use UTF-8: it would be good to acknowledge this and, 
rather than assuming that content can be in many encodings, say that it 
is possible to sometimes encounter some pages in legacy encodings.

None of those pages are likely to be in UTF-16, and you should remove 
this from your list of examples.

These comments apply elsewhere in the doc where character encodings are 
referred to.




3.4 Side-by-Side Comparison of the Example Tools
"ISO-8859-1, UTF-8, UTF-16; any language supported by these encodings"

*All* languages are supported by UTF-8, which should be the encoding of 
choice for all new developments.


Hope that helps,
RI

Received on Friday, 15 August 2014 16:43:53 UTC