21:07:20 RRSAgent has joined #html-a11y-media 21:07:20 logging to http://www.w3.org/2014/11/24-html-a11y-media-irc 21:07:22 RRSAgent, make logs world 21:07:22 Zakim has joined #html-a11y-media 21:07:24 Zakim, this will be 2119 21:07:24 I do not see a conference matching that name scheduled within the next hour, trackbot 21:07:25 Meeting: HTML Accessibility Task Force Teleconference 21:07:25 Date: 24 November 2014 21:10:34 We could do ad hoc? 21:10:42 lets do that. 21:10:49 zakim, room for 5? 21:10:51 ok, janina; conference Team_(html-a11y-media)21:10Z scheduled with code 26631 (CONF1) for 60 minutes until 2210Z 21:11:17 Team_(html-a11y-media)21:10Z has now started 21:11:23 +??P1 21:11:30 zakim, ??P1 is me 21:11:30 +janina; got it 21:11:31 + +1.617.319.aaaa 21:11:38 zakim, aaaa is me 21:11:38 +MarkS; got it 21:28:38 JF has joined #html-a11y-media 21:28:49 dialing in momentarily 21:32:01 +JF 21:42:38 ShaneM has joined #html-a11y-media 21:43:48 no, can y9ou join us? 21:43:50 zakim, code? 21:43:50 the conference code is 26631 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), janina 21:44:04 2 mins 21:44:33 KK 21:44:44 OK 21:45:04 ShaneM_ has joined #html-a11y-media 21:45:17 what is the code? 21:45:23 zakim, what is the code? 21:45:23 the conference code is 26631 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), ShaneM_ 21:45:25 agenda? 21:47:25 Chair+ Janina Sajka 21:47:25 agenda+ Identify Scribe 21:47:25 agenda+ Media Accessibility User Requirements Comment Responses 21:47:32 zakim, take up item 1 21:47:32 agendum 1. "Identify Scribe" taken up [from MarkS] 21:47:37 scribe: MarkS 21:47:47 zakim, close item 1 21:47:47 agendum 1, Identify Scribe, closed 21:47:48 I see 1 item remaining on the agenda: 21:47:48 2. Media Accessibility User Requirements Comment Responses [from MarkS] 21:47:50 take up next item 21:48:36 SM: I agreed with JF on that, but didn't make any edits because we didn't have consensus 21:49:03 ...first comment is "Cognitive and neurological disabilities..." Just cognitive, they are the same. 21:49:13 [everyone] agrees 21:50:22 SM: RE: Calling out memory as a disability. Its common to everything in cog and not just cognitive. 21:50:35 ...like what time a telecon is ;) 21:51:09 JS: The more complicated you make a requirement, the more people will make mistakes. 21:51:23 ...whether its memory, or a long string, or case sensitivity, etc. 21:52:06 ...anything here we need to capture? 21:52:07 ...willing to let it go and drop it. Not sure there is much there. 21:52:52 JF: The only place we mention memory is in the preamble 21:53:49 JS: I think we want to specifically call out memory. This is how other disabilities share aspects with challenges everyone faces 21:54:16 ...if you have none of the others, you might have that one. 21:55:23 SM: "Individuals with... information presented as text" should have audio descriptions for everything. JF disagreed with that. 21:56:21 JF: The proposed change that came forward wanted to change it to text should be presented aurally. It puts the emphasis on the content producer to produce that. I don't want to say that. All things equal, if you give it to them in text, it can be converted to another format. 21:56:36 ...their suggested change contradicts this 21:56:53 JS: Another answer is to say we support transcript for media. 21:57:22 JF: We have this problem for video descriptions, because they're available as audio or text, they both fundamentally meet the req of WCAG 21:58:01 JS: could they be suggesting that aural based AD should be available via text? 21:58:08 JF: no, they want the inverse 21:58:22 Sentence beginning with “Individuals with …” a. It is not just that “…information that is presented as text embedded in a video should also be available as audio descriptions …”. Text anywhere, such as in web pages, should be available aurally. b. Suggestion: Change to “… information presented as text should be available aurally, including audio descriptions embedded in videos …”. 21:59:54 JS: we should say this is already addressed. 22:00:58 JF: so we are not making this change? 22:01:01 JS: no 22:01:06 ...we already address this 22:01:23 SM: multi-system affects, comments says its confusing and we need to clarify 22:02:46 ...a web search reveals that this is not hyphenated, and means when a disorder affects multiple cognitive systems 22:03:12 JS: so its well defined, and should not be hyphenated 22:03:30 SM: we should say that its well defined in the Autism spectrum disorder community 22:03:42 ...there is another comment about a run-on sentence, I can fix that 22:04:02 ...accommodation, accommodations... 22:05:32 ...another comment about not reading well. its in passive voice which we don't usually use. 22:05:52 ..."necessary accessibility supports widely... 22:06:23 ...should be something like " accessibility support for these ..." 22:06:52 JS: had one from the ARIA call today. requirement to keep controls on screen, related to cognitive. 22:08:22 [KA-4] It must always be possible to enable native controls regardless of the author preference to guarantee that such functionality is available and essentially override author settings through user control. This is also a particularly important requirement on mobile devices or devices without a keyboard. 22:09:00 SM: we changed KA to IC because it was Interactive Controls, not Keyboard a11y 22:09:11 http://www.w3.org/WAI/PF/media-accessibility-reqs/#requirements-on-the-parallel-use-of-alternate-content-on-potentially-------multiple-devices-in-parallel 22:09:22 http://www.w3.org/TR/media-a11y-reqs/ 22:10:16 ... need to fix that link 22:10:40 http://w3c.github.io/pfwg/media-accessibility-reqs/ 22:12:07 SM: add sentence: "note this may include requirement that controls have the ability to remain on screen at all times" 22:12:29 ...the Checklist still says KA, If its OK, I'll change that to IC 22:12:52 scribe: JF 22:13:09 JS: Atypical color perception, from michael, link to WCAG 22:13:11 JS: we have some related links from K. Cooper for cross-reference purposes 22:13:29 s/K. Cooper/M. Cooper 22:13:29 ...i sent on list 22:13:42 [agreement] 22:14:17 SM: add these links where appropriate? 22:14:25 [agreement] 22:14:33 SM will add those as well 22:14:47 JS: next week at 10:00AM for ONE WEEK ONLY 22:15:05 ...would like to get Nigel to attend, so we may move this meeting time again 22:15:27 JS: next week we meet at 10:00 AM Boston, after which we will look to find a different time 22:15:34 one that can accomodate Nigel as well 22:15:54 JS: we're done 22:16:17 rrsagent, make logs public 22:16:24 rrsagent, draft minutes 22:16:24 I have made the request to generate http://www.w3.org/2014/11/24-html-a11y-media-minutes.html JF 22:16:32 zakim, please part 22:16:32 leaving. As of this point the attendees were janina, +1.617.319.aaaa, MarkS, JF 22:16:32 Zakim has left #html-a11y-media 22:16:54 rrsagent, please part 22:16:54 I see no action items