Evaluation and Repair Tools Working Group Teleconference

http://www.w3.org/WAI/ER/WD-AERT/ED-AERT

http://lists.w3.org/Archives/Public/public-wai-ert/2013Oct/0012.html

[[- 2.1.8. Crawling. Editorial comment: the list refers to topics already

dealt with in previous sections. There is nothing wrong with that but,

should we include linked cross-references to those sections?]]

#1. try to avoid requiring people to move back and forth to read a document

#2. where necessary to reference other sections, add cross-references

#3. where cross-references are added, make sure it is clear that they are cross-references (so that readers can decide if they want to follow them or not)

#4. when listing items, make sure you don't list different types of items (eg. new and old content can be confusing)

#5. don't add new information to previous sections from another sections -- add the information to the section itself and only cross-reference if necessary

[[- 2.2.3 Development of own tests and test extensions. Instead of "advanced

tools offer an API so developers can create their own tests", I would

suggest "advanced tools define an API which developers can implement so as

to integrate the tests they create with the tool". Rationale: the test

integration API is not *provided* by the tool, but indeed *required* by it

from any third party who wishes to have their developments integrated.]]

[[a) Localization is broader than translation. Maybe the case I linked in

the minutes is already covered by 2.4.2 (functionality customization), but

there are other aspects as well that go beyond translation (e.g. icons,

formatting, directionality, UI layout, units, etc.) Although I would not

suggest listing all those items, I would nonetheless make explicit that

localization is much more than translation.]]

http://en.wikipedia.org/wiki/Internationalization_and_localization

"Localization is important for making your tool more usable for people in different regions and who speak other languages. This includes translating and adapting the user interface and reports accordingly. The W3C Internationalization Activity provides more resources on this topic. There are also translations for Web Content Accessibility Guidelines available."

[[b) Internationalized tools need to deal correctly with non-English (or

non-local) contents. Typical internationalization errors happen, e.g.,

when you are going to render the errors on the content and you see

everything riddled with question marks, when a readability evaluation

technique is only applicable to English contents, etc. I'm not sure if

this should be considered either under the same point as the localization

of the UI or separately, but I think it merits being mentioned anyway.]]

add to section 2.1

also note the tools that evaluate "readability" and how that applies to different languages

probably need to add to several sections, not only 2.1

[[2.1.3 Web applications]]

"Emulating User Actions"

"Dynamic Content" or "Interactive Content"

NO MEETING NEXT WEEK