22:02:46 RRSAgent has joined #html-a11y
22:02:46 logging to http://www.w3.org/2010/07/28-html-a11y-irc
22:02:51 zakim, this will be WAI_PFWG(A11Y)
22:02:51 ok, janina, I see WAI_PFWG(A11Y)6:00PM already started
22:02:58 zakim, call janina
22:02:58 ok, janina; the call is being made
22:03:00 +Janina
22:04:11 JF has joined #html-a11y
22:04:12 zakim, who's here?
22:04:12 On the phone I see Judy, John_Foliot, Janina
22:04:13 On IRC I see JF, RRSAgent, Zakim, janina, silvia, trackbot
22:04:27 plh has joined #html-a11y
22:04:43 +Plh
22:06:02 + +61.2.801.2.aaaa
22:06:10 zakim, aaaa is Silvia
22:06:10 +Silvia; got it
22:08:23 Meeting: HTML-A11Y telecon
22:08:23 Chair: John_Foliot
22:08:23 agenda: this
22:08:23 agenda+ Identify Scribe
22:08:23 agenda+ Actions Review http://www.w3.org/WAI/PF/HTML/track/actions/open
22:08:24 agenda+ Summary--User Requirements and Technical Implications
22:08:26 agenda+ Starting a Technical Gap Analysis
22:08:28 agenda+ next meetings, confirm date/time, choose scribe
22:08:30 agenda+ be done
22:08:32
22:08:56 1. Action Item Review
22:09:40 http://www.w3.org/WAI/PF/HTML/track/actions/open
22:09:53 scribe: silvia
22:11:09 judy: can we pick up an action item for pairs of people to do edits to the requirements document
22:11:22 … I have a few more edits to do in the next few days
22:12:52 silvia: I have edited all of the items that Sean and I had to do
22:13:03 … only the extended captions section could do with a group discussion
22:13:25 … to have a better grasp on what features we need
22:13:43 JF: we have discussed it over the last weeks on the calls, though the minutes may not have everythings
22:14:23 Janina: I think we have discussed extended descriptions, but not extended captions
22:14:38 Judy: let's add it to the agenda
22:14:52 Janina: can do after action item 2
22:15:53 JF: Eric and my feedback still has to go into the wiki
22:16:04 Judy has joined #html-a11y
22:16:30 2. Summary--User Requirements and Technical Implications
22:17:30 Janina: review the summary that Janina posted
22:18:18 … maybe lets discuss the use case for extended captioning first
22:18:26 http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements#Extended_Time-aligned_Text_Cues
22:19:03 q+
22:21:02 q+ to contemplate the interpretation of this new title of the requirements
22:22:01 silvia: it is now called extended time-aligned text cues and not any more extended captioning
22:23:00 … the idea behind it is to allow people that have slower reading speed and need more explanation about the captions to get this information from the stream
22:23:09 … things like pausing at the end of a cue to catch up on reading
22:23:22 … and having links to abbreviation explanations etc
22:24:08 Janina: this should be something that should be available to normal captions, too
22:24:15 … I don't see it necessary to have it separate
22:24:41 Judy: the title needs to be reformulated - "cue"s are more like events and not captions
22:25:59 JF: I actually like the idea of removing the word "caption" because the use cases go far beyond just caption users
22:26:29 Judy: we haven't removed the general caption section, so that may be ok
22:27:37 Judy: literacy level of hearing and vision impaired people in comparison to the general population is very different in different countries
22:27:52 Janina: it's not necessary to talk about this in the document
22:28:09 JF: it's not a technical issue
22:29:37 Janina: if the distinction between captions and this section has to do with more extra content beyond dialog, I'm not sure it's necessary
22:30:32 … pause content & review is a need
22:30:40 … hyperlinks is a need
22:31:17 q+
22:31:33 q-
22:33:08 silvia: there is a separate section for these extensions because there is new functionality that is not traditionally understood under the keyword "caption"
22:34:06 Janina: I don't see that we need a different file format for this
22:34:33 JF: no, we don't need a new file format for this, but we need extra functionality
22:36:36 Janina: it doesn't change the timeline, it just introduces pauses
22:36:46 Judy: let's not get bogged down into too much detail
22:37:28 … maybe we need to have an offline discussion on this
22:38:02 JF: I believe we're at the point where we wanted to do a review of Janina's technical requirements document
22:38:08 http://lists.w3.org/Archives/Public/public-html-a11y/2010Jul/0126.html
22:38:10 s/document/email/
22:39:28 Janina: in the process of discussing in recent weeks, I came up with these terms
22:40:25 JF: are there any holes?
22:40:44 Janina: I am becoming strongly convinced that extended captions and captions are the same file
22:40:58 … other than that I think we are complete
22:41:29 q+
22:41:29 JF: are we at the point where the requirements document can be sent up the foodchain?
22:41:47 q+ to address John's question
22:42:00 … do we need to make this email a more formal document?
22:42:46 Judy: it would be good to get feedback from those not in the meeting
22:42:58 … also, we should look at the different format options
22:43:23 … we had laied out last week what comes next
22:43:49 JF: we said that once we were happy about the requirements doc, we would take another look at the technical implications
22:44:32 … discuss XML formats
22:44:43 … discuss streaming implications
22:46:37 judy confirms that we still have user requirement edits to complete.
22:46:45 http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements#Extended_Time-aligned_Text_Cues
22:48:30 silvia: to some extend we need to finish editing the user requirements before we can specify the detailed technical requirements
22:51:52 … Janina's email is a great summary document on the technical conclusions
22:52:02 .. it would be good to turn that into a document in the wiki, too
22:52:37 … in addition, we can go through the user requirements document and add some small technical conclusions on each requirement
22:53:26 Judy: I'm hoping we can get the details in the wiki asap we can move forward with discussions on file format
22:55:17 silvia: what makes this even more urgent is that Ian has now included a file format and media a11y solution into the HTML5 spec
22:55:40 … even if the file format is only in the WHATWG spec - it has had influence on the general solution
22:56:07 JF: timeline and milestones are indeed important
22:56:17 … but we need to answer the open questions
22:57:15 Janina: if I understand silvia correctly, it makes sense to put a bit more effort into the requirements document to have the individual requirements in the document
22:59:40 silvia: I don't think it's much extra effort - we have discussed all of these details already
23:00:37 … as I was editing the wiki and included the feedback from the questionnaire, I have included technical notes underneath the individual user requirements to give better understanding to technical people what the user needs actually mean
23:00:46 -Plh
23:01:10 … this doesn't need a new document, but just dense notes underneath the individual user requirements
23:01:36 … but an extra document that captures the high-level technical conclusions that Janina has summarised would be good
23:02:13 JF: Eric and I have been discussing the technical consequences of the user requirements, too
23:02:27 … we should indeed put the summary page into the wiki
23:02:40 Janina: anyone against including the summary page into the wiki?
23:03:02 … I'm in favor of it and I hope we can pull this all together real soon
23:03:24 JF: I'll create the wiki page
23:03:39 3. Starting a Technical Gap Analysis
23:05:01 JF: do we want to spend the next 25 min on this?
23:05:26 silvia: what do we mean by "technical gap analysis"? does it mean we compare the current HTML5 spec with our requirements to identify gaps?
23:09:43 JF: yes, probably
23:19:27 q+
23:20:11 general discussion about approach
23:20:48 … it seems the group agrees to discourage browser vendors at this stage from implementing anything
23:20:58 … we as a group need to do a good analysis of what is being proposed
23:21:11 … we as a group also need to analyse alternatives of what is being proposed
23:23:54 … we should also invite others to explain how the current spec is meeting our user requirements
23:26:42 https://wiki.mozilla.org/Accessibility/Video_Text_Format <- is an alternative format that I am playing with
23:27:29 https://wiki.mozilla.org/Accessibility/Video_Text_Format_Comparison
23:27:33 ack j
23:27:33 Judy, you wanted to address John's question and to
23:30:11 q+
23:31:30 silvia: I've been experimenting with the above format and comparing to other options to find out about advantages/disadvantages
23:31:51 q+ to contemplate the effects of the timing of this approach, and to think about a few things
23:31:54 JF: I think it's important that we can show that we are indeed looking at other options
23:41:19 JF_ has joined #html-a11y
23:42:09 silvia: also note there is a new subtitling format in development in the subtitling community called AS6
23:42:50 judy will get back to wrap up of user requirement edits, to finish that
23:43:20 JF: ongoing action items for user requirements edits
23:43:40 … new wiki page to add with summary on technical requirements
23:44:29 -John_Foliot
23:44:32 -Judy
23:44:33 -Janina
23:44:33 -Silvia
23:44:35 WAI_PFWG(A11Y)6:00PM has ended
23:44:36 Attendees were Judy, John_Foliot, Janina, Plh, +61.2.801.2.aaaa, Silvia
23:44:42 zakim, bye
23:44:42 Zakim has left #html-a11y
23:44:57 rrsagent, make log public
23:45:05 rrsagent, make minutes
23:45:05 I have made the request to generate http://www.w3.org/2010/07/28-html-a11y-minutes.html janina
23:45:20 OK!
23:45:25 Thanks, Silvia!
23:45:46 let me try again ...
23:45:52 rrsagent, make log public
23:46:01 rrsagent, make minutes
23:46:01 I have made the request to generate http://www.w3.org/2010/07/28-html-a11y-minutes.html janina
23:46:08 thanks a lot, Janina!
23:46:22 Anytime.
23:46:35 They come up public for me now