<trackbot> Date: 29 September 2014

<janina> trackbot, who's on the phone?

<trackbot> Sorry, janina, I don't understand 'trackbot, who's on the phone?'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.

<scribe> ScribeNick: ShaneM

Media Accessibility User Requirements Comments

<janina> [3] [27]http://lists.w3.org/Archives/Public/public-html-a11y/2014Sep/0045.html

<janina> [4] [28]http://lists.w3.org/Archives/Public/public-html-a11y/2014Sep/0046.html

janina: the only thing between us and finalizing is addressing these two comments, any other comments that might come in soon, and the feedback from EO.
... EO indicates that they can't get to it until TPAC. That's okay. We just need to finalize this calendar year.
... we are only expecting comments from EO about section 2.
... The EO document and our document should be sync'd. We have known about this all along.
... Should we tie the comments back to bugs?

MarkS: Yes - it helps to connect repository checkins to specific issues.
... do we have a product in Bugzilla?

janina: Yes, but I dont have the details. I can get them in the next hour.

MarkS: Okay - if you can get me that information then I can create the bugs.

Bug from Bronwyn Lapham

The question is were we talking about relocating the description in time or spatially?

JF: Not in time. And DV-6 talks about volume. This is about moving the description around within the mix (for example moving it far into the 'right' of the sound).
... basically we are talking about 'zenith'. You could have it 'whispered in one ear'.

janina: we have certainly spent enough time in recording studios. Regardless of how it is originally mixed, what we want to do is allow the user to relocate it to afford them the best clarity.
... if it is possible to locate it away from the 'main audio' that would be helpful.

JF: I am not sure how an engineer would address this short of having independent volume control and location for the descriptive track.

janina: we do say early on that we do not expect every tool to enable everything we discuss.

ShaneM: I didn'
... t read it this way. Can we clarify.

MarkS: Yes. It doesn't hurt to have it in there, but it needs to be clear.

JF: How do we provide that sort of explanantion?
... we have all of these requirements, but we have never really expanded on the intent.
... if you back to look at WCAG we have a requirement, the understanding, and the techniques. This document does not currently expand on our requirements like that.

<MarkS> SM: When i read it, I actually didn't have any idea what it meant. What does "in the audio field" mean in this context. Now that I've heard the discussion today, I understand.

<MarkS> JS: I can take a stab at rewriting this.

<MarkS> SM: is it just spatially (virtually) or is it frequency as well (low/high pitch)

<MarkS> ...listening to rec of kindergartners and there is a low voice describing their actions, you may want to be able to switch the pitch of a particular track

<MarkS> JF: I don't think we've discussed that shane, so its an interesting facet to consider

<MarkS> JS: They are supposed to consider that when they choose a reader/describer

ShaneM: For example it when there is a single reader of an audio book, it is difficult to understand when a character is speaking vs. when there is narration.

janina: I am willing to take a crack at rewriting this.

JF: We do have the 'green' notes that we use sometimes to add clarity.

janina: should I add a mention of pitch-shifting?

ShaneM: Don't add it on my account - I am not an expert on this topic.

janina: this is aimed at tools that help people. These are tool requirements, not production requirements.

JF: It is really about requiring a mechanism for adjusting the descriptive track. It includes volume and pan.
... any system that supports multi-track should be able to do this easily.
... I have not seen this delivered on the web other than in streaming video e.g. Netflix, or in 5.1 or 6.1 surround.

janina: I think you can do this in software if you load the right libraries.
... pitch-shifting is a little harder, as it requires number crunching.

JF: The only way this can be done is to maintain it as a separate track. It can't be pre-mixed.

ShaneM: But a client-side control could influence the mix from the server if the server had the tracks separated.

Andrew Norman Comments

JF: First comment - augment 2.5 to make it clear that people with cochlear implants don't have volume risk, but DO have a risk of overwhelming the brain.
... As this is an EO section, and they have thought about this, can we let them write this?

janina: Yes, that seems like a good idea.

The second is about people with motor skill challenges.

JF: I agree that clickable objects need to be of a certain size. This isn't just a media player issue.

janina: I agree - it seems like a UAAG requirement.

JF: and this isn't just about people with diseases. People who are using sub-standard controls or have other physical impairments can have problems too.

janina: I think it is out of scope for this document.

JF: yes, but we do cover system requirements. including access to system controls and menus

janina: yes, but our list is media specific. This is an over arching requirement (e.g., something from UAAG)

JF: we have 5 requirements in this space (reads them)
... maybe we should add a new requirement about this?

janina: or should be point to UAAG?

JF: In our checklist we said we would reference other guidelines like UAAG. But that doesn't mean we don't have a local related requirement.
... KA-1 is a requirement that maps back to WCAG 2.1.1 and UAAG 4.1.1 as
... 'A' requirements
... Adding a KA-6 - ensure that on-screen controls are of a sufficient size to be manipulated by people with substandard controls or physical impairments.

janina: JF, want to take a stab at it and then run it by UAAG?

JF: Wordsmith a new requirement KA-6. and then we can run it by UAAG.

janina: substandard is a little loaded. some other term that is a term of art and already used by UAAG.

JF: Mr. Norman also suggests some text for specific requirements for control placement, timing, and volume control.
... I think we want to decouple it from the neurological because it should be way more than that. But there is a good seed of a requirement here.

write it up and then discuss it next Monday.

Identify Scribe

Other business

JF: We need to get back to the poster issue.

janina: I thought we were going to handle that with ARIA.

JF: It isn't in ARIA 1.1

janina: No one will make a proposal if you don't, John.

JF: The only thing we could do is aria-poster-description or something. Let me talk to Rich and see what he thinks.
... it has never slipped from my brain, but it doesn't get look at very often.

janina: on "transcript" we were going to have Sylvia revive her proposal.

JF: we had two proposals.

janina: we have waited a while for this to sort out, and we do need a formal solution.

JF: the simple solution would be to add transcript as a type of 'kind'.
... anyway, those are the two other issues we need to return to. Poster and Transcript. We had talked about having an extension spec.

janina: we were explicitly empowered to do a transcript extension in plan 2014

<Zakim> ShaneM, you wanted to talk about after 5

<MarkS> SM: While there are people who have said things like that, I think the context is that there is an extension, and I'm not going to use it.

<MarkS> ...we don't need them to.

<MarkS> ...I don't think we need to worry about this.

janina: we can still do transcript as an extension if we find it important.
... we have a next step for poster - JF will talk to Rich.
... we do not have a next step for transcript yet. other than possibly asking Sylvia if she wants to bring up her proposal again.

JF: we need implementor support
... maybe have some conversations at the end of the month (at TPAC). Grab some people and ask them from an Engineering perspective what we think about connecting transcripts to video.
... let's think about it and discuss it again next week. Find out if Sylvia is coming to TPAC and if she has any interest in revising that old proposal.

<JF> [media]

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Cyns/Sylvia/
Found ScribeNick: ShaneM
Inferring Scribes: ShaneM
Default Present: janina, ShaneM, JF, MarkS
Present: janina ShaneM JF MarkS
Found Date: 29 Sep 2014
Guessing minutes URL: http://www.w3.org/2014/09/29-html-a11y-media-minutes.html
People with action items: