IRC log of er on 2013-10-30

Timestamps are in UTC.

13:31:12 [RRSAgent]
RRSAgent has joined #er
13:31:12 [RRSAgent]
logging to
13:31:14 [trackbot]
RRSAgent, make logs public
13:31:14 [Zakim]
Zakim has joined #er
13:31:16 [trackbot]
Zakim, this will be 3794
13:31:16 [Zakim]
ok, trackbot; I see WAI_ERTWG()9:30AM scheduled to start now
13:31:17 [trackbot]
Meeting: Evaluation and Repair Tools Working Group Teleconference
13:31:17 [trackbot]
Date: 30 October 2013
13:31:26 [shadi]
zakim, this is ert
13:31:26 [Zakim]
ok, shadi; that matches WAI_ERTWG()9:30AM
13:31:33 [shadi]
zakim, who is on the phone?
13:31:33 [Zakim]
On the phone I see ??P19
13:31:41 [samuelm]
zakim, ??P19 is me
13:31:41 [Zakim]
+samuelm; got it
13:32:37 [Zakim]
13:34:11 [shadi]
13:34:36 [Zakim]
13:35:00 [shadi]
13:35:32 [shadi]
zakim, ??p21 is carlos
13:35:32 [Zakim]
+carlos; got it
13:37:07 [shadi]
[[- 2.1.8. Crawling. Editorial comment: the list refers to topics already
13:37:07 [shadi]
dealt with in previous sections. There is nothing wrong with that but,
13:37:07 [shadi]
should we include linked cross-references to those sections?
13:37:07 [shadi]
13:51:03 [shadi]
#1. try to avoid requiring people to move back and forth to read a document
13:51:21 [shadi]
#2. where necessary to reference other sections, add cross-references
13:52:12 [shadi]
#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)
13:52:44 [shadi]
#4. when listing items, make sure you don't list different types of items (eg. new and old content can be confusing)
13:53:43 [shadi]
#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
13:55:03 [shadi]
[[- 2.2.3 Development of own tests and test extensions. Instead of "advanced
13:55:03 [shadi]
tools offer an API so developers can create their own tests", I would
13:55:03 [shadi]
suggest "advanced tools define an API which developers can implement so as
13:55:03 [shadi]
to integrate the tests they create with the tool". Rationale: the test
13:55:04 [shadi]
integration API is not *provided* by the tool, but indeed *required* by it
13:55:04 [shadi]
from any third party who wishes to have their developments integrated.]]
14:02:19 [shadi]
[[a) Localization is broader than translation. Maybe the case I linked in
14:02:19 [shadi]
the minutes is already covered by 2.4.2 (functionality customization), but
14:02:19 [shadi]
there are other aspects as well that go beyond translation (e.g. icons,
14:02:19 [shadi]
formatting, directionality, UI layout, units, etc.) Although I would not
14:02:20 [shadi]
suggest listing all those items, I would nonetheless make explicit that
14:02:21 [shadi]
localization is much more than translation.]]
14:03:35 [shadi]
14:06:34 [shadi]
"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."
14:09:03 [shadi]
[[b) Internationalized tools need to deal correctly with non-English (or
14:09:03 [shadi]
non-local) contents. Typical internationalization errors happen, e.g.,
14:09:03 [shadi]
when you are going to render the errors on the content and you see
14:09:03 [shadi]
everything riddled with question marks, when a readability evaluation
14:09:03 [shadi]
technique is only applicable to English contents, etc. I'm not sure if
14:09:04 [shadi]
this should be considered either under the same point as the localization
14:09:06 [shadi]
of the UI or separately, but I think it merits being mentioned anyway.]]
14:13:28 [shadi]
add to section 2.1
14:15:03 [shadi]
also note the tools that evaluate "readability" and how that applies to different languages
14:19:10 [shadi]
probably need to add to several sections, not only 2.1
14:19:24 [shadi]
[[2.1.3 Web applications]]
14:24:35 [shadi]
"Emulating User Actions"
14:30:07 [shadi]
"Dynamic Content" or "Interactive Content"
14:30:38 [Zakim]
14:30:40 [shadi]
14:30:57 [Zakim]
14:30:58 [Zakim]
14:30:58 [Zakim]
WAI_ERTWG()9:30AM has ended
14:30:58 [Zakim]
Attendees were samuelm, Shadi, carlos
14:50:58 [shadi]
trackbot, end meeting
14:50:58 [trackbot]
Zakim, list attendees
14:50:58 [Zakim]
sorry, trackbot, I don't know what conference this is
14:51:06 [trackbot]
RRSAgent, please draft minutes
14:51:06 [RRSAgent]
I have made the request to generate trackbot
14:51:07 [trackbot]
RRSAgent, bye
14:51:07 [RRSAgent]
I see no action items