See also: IRC log
<Judy> silvia, do you plan to join?
<silvia> I have a busy schedule today, sorry
<silvia> if you need me, just type my name and I can join though
<janina> 4http://www.w3.org/2002/09/wbs/44061/20080526_media-requirements/results
<janina> http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements
<Judy> ---------------------------
<MikeSmith> scribe: MikeSmith
Sean Hayes has joined
John Foliot is out today, Janina is chairing
[reviewing requirements together]
janina: we did not make an
representations that we would reply to people's comments
... so no action necessarily needed here
silvia: I suggest putting a reply to this question in the minutes
[discussion is about comment regarding inclusion of markup for speech synthesis]
answer to question about whether such formats exist: Yes
Sean: Timed Text can also be used for speech markup...
[going on to next comment from Philip J]
the comment: "Is copyright information and usage rights really relevant to users of this technology? It seems like a general requirements unrelated to accessibility which should be suggested for <audio>/<video>, if at all."
silvia: it's good to have it in
the requirements, but it should be solved more generally
... e.g., as is being done in the Media Annotations WG
Judy: so remove it? keep it but
tie it to other work?
... is there a suggestion?
Eric: I would suggest it be listed as a general requirement any time we pull in resources that are not the [master media resource]
Eric: I think we should remove it
from this section
... because we are otherwise implying that it's not important
in other sections as well
[we have agreement to remove it from this section]
[Silvia is making changes to the source live]
janina: resolution on TAD-3 is "if you can support it, you should"
Philip's comment about that was, "Sounds like a quality of implementation issue for UAs, not something all UAs will be able to do on all platforms"
[no objections to making that change]
janina: this is a UA issue, not a user issue
Eric: this is one of those that there is no way to support on all platforms
silvia: we should document what we expect the default/minimum to be
Eric: it won't be a very good
user experience if a UA is not able to handle it
... because the descriptions will be out of sync
janina: I can't see this being
used in, say, a Hollywood movie
... it seems like something that's limited to the case of using
in an [instructional context only]
... this is new ground here.. brand new... have not had this
ability in the past
[we are btw discussing TAD-4]
Eric: amount that a UA keeps buffered is not infinite
[changes made to requirements doc]
moving on to comment from Eric: "If we want people to be able to create interoperable pages, this requirement must specify a TAD file format.
"
plus:
(TAD-1), (TAD-2), (TAD-4), and (TAD-5) Aren't these all requirements for the TAD file format?
(TAD-3) This won't be possible on all platforms, for example devices that only allow one mode of audio output.
"
janina: I think, Eric, I agree with you
<scribe> ACTION: janina to add some introductory text to requirement docs clarifying that these are user requirements, not necessarily UA requirements [recorded in http://www.w3.org/2010/06/16-html-a11y-minutes.html#action01]
<trackbot> Created ACTION-50 - Add some introductory text to requirement docs clarifying that these are user requirements, not necessarily UA requirements [on Janina Sajka - due 2010-06-23].
next comment was from Marco Ranon, about a typo, and that is now fixed
next comment is from Masatomo Kobayashi, "TAD-2 Could label the three specific requirements so that we could easily refer to each item?"
[not clear to scribe what the resolution was on Kobayashi-san's "(TAD-3) This won't be possible on all platforms, for example devices that only allow one mode of audio output." comment, so would like for somebody to please record that here if possible]
<silvia> Koboyashi TAD-3 comment was already resolved through addressing Philip's comment
<scribe> scribe: Sean
<janina> Rich is asking for API support
Judy: Should be 'support presentation of'
eric: we are documenting user requirements, not UA reqts
Judy: 'support presentation of'
Do we want the additional specificity
Silvia: has made edit
judy: access to textual representation of description
in order that it can be presented to a screen reader
support for different options for the overflow case
silvia: addressing richards comment may have addresed this
No W3C recommendation on emotional markup
moving to clear audio
moving to extended audio description
Eric: Big difference between a demo and shipping code
Janina: this is a new user requirement
if a major player wants to do it then fine
Eric: should this be listed as a requirement
Silvia: should soften must into "advanced functionality"
Judy: what does detailed user control mean
Silvia: what to do in the case of overflow
Judy: This requires too much
domain knowledge
... make conditional and reference TAD 4
comment is SMIL would be an enormous undertaking
Sean: could this be achieved with a simpler technology?
Silvia: These are technical comments, and we shouldnt go there in this doc
Eric: I'm concerned that if we come out with a doc saying these are the reqts, then its a conclusion all need to be supported by UA
Janina: This is an advanced feature
<silvia> How about: Note that this is an advanced feature and would only be expected by advanced systems.
Silvia: How about: Note that this is an advanced feature and would only be expected by advanced systems
Judy: Capture a note to provide definition of EAD
Eric: the crux is the strictness of the synchronisation
without it wont provide a good user experience
Judy: response is?
Janina: Not convinced that loose synchronisation is acceptable
EAD 1 should be split into two provisions
Silvia: re-order to clarify that its the control that is key
Janina: Previous section is
covering this area too
... 3 out of 17 is not fast enough
there is too much to go throgh, suggesting a virtula f2f
Judy: suggest people to pair up and take on different sections
Eric: +1 to Judy
Janina: 3 teams Sean & silvia; Eric and John; Janina and Judy
Judy: Discovery is huge, rest is fairly even
Sean: load balance in email
Silivia: Will do the assignments
teams to cover their work by next tuesday
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/synx/sync/ Succeeded: s/support for presentation of/support presentation of/ Succeeded: s/2/4/ Found Scribe: MikeSmith Inferring ScribeNick: MikeSmith Found Scribe: Sean Inferring ScribeNick: Sean Scribes: MikeSmith, Sean ScribeNicks: MikeSmith, Sean WARNING: No "Topic:" lines found, but dash separators were found. Defaulting to -dashTopics option. Default Present: Eric_Carlson, Janina, Judy, Mike, silvia, [Microsoft] Present: Janina Judy Silvia Sean MikeSmith Eric Got date from IRC log name: 16 Jun 2010 Guessing minutes URL: http://www.w3.org/2010/06/16-html-a11y-minutes.html People with action items: janina WARNING: Possible internal error: join/leave lines remaining: <scribe> Sean Hayes has joined WARNING: Possible internal error: join/leave lines remaining: <scribe> Sean Hayes has joined[End of scribe.perl diagnostic output]