See also: IRC log
<trackbot> Date: 24 November 2014
<janina> We could do ad hoc?
<MarkS> lets do that.
<JF> dialing in momentarily
<JF> no, can y9ou join us?
<ShaneM> 2 mins
<JF> KK
<janina> OK
<ShaneM_> what is the code?
<MarkS> Chair+ Janina Sajka
<MarkS> scribe: MarkS
take up next item
SM: I agreed with JF on that, but
didn't make any edits because we didn't have consensus
... first comment is "Cognitive and neurological
disabilities..." Just cognitive, they are the same.
[everyone] agrees
SM: RE: Calling out memory as a
disability. Its common to everything in cog and not just
cognitive.
... like what time a telecon is ;)
JS: The more complicated you make
a requirement, the more people will make mistakes.
... whether its memory, or a long string, or case sensitivity,
etc.
... anything here we need to capture?
... willing to let it go and drop it. Not sure there is much
there.
JF: The only place we mention memory is in the preamble
JS: I think we want to
specifically call out memory. This is how other disabilities
share aspects with challenges everyone faces
... if you have none of the others, you might have that
one.
SM: "Individuals with... information presented as text" should have audio descriptions for everything. JF disagreed with that.
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.
... their suggested change contradicts this
JS: Another answer is to say we support transcript for media.
JF: We have this problem for video descriptions, because they're available as audio or text, they both fundamentally meet the req of WCAG
JS: could they be suggesting that aural based AD should be available via text?
JF: no, they want the inverse
<JF> 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 …”.
JS: we should say this is already addressed.
JF: so we are not making this change?
JS: no
... we already address this
SM: multi-system affects,
comments says its confusing and we need to clarify
... a web search reveals that this is not hyphenated, and means
when a disorder affects multiple cognitive systems
JS: so its well defined, and should not be hyphenated
SM: we should say that its well
defined in the Autism spectrum disorder community
... there is another comment about a run-on sentence, I can fix
that
... accommodation, accommodations...
... another comment about not reading well. its in passive
voice which we don't usually use.
... "necessary accessibility supports widely...
... should be something like " accessibility support for these
..."
JS: had one from the ARIA call today. requirement to keep controls on screen, related to cognitive.
<JF> [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.
SM: we changed KA to IC because it was Interactive Controls, not Keyboard a11y
<JF> http://www.w3.org/TR/media-a11y-reqs/
SM: need to fix that link
<ShaneM_> http://w3c.github.io/pfwg/media-accessibility-reqs/
SM: add sentence: "note this may
include requirement that controls have the ability to remain on
screen at all times"
... the Checklist still says KA, If its OK, I'll change that to
IC
<JF> scribe: JF
<MarkS> JS: Atypical color perception, from michael, link to WCAG
JS: we have some related links from M. Cooper for cross-reference purposes
<MarkS> ...i sent on list
<MarkS> [agreement]
SM: add these links where appropriate?
[agreement]
SM will add those as well
<MarkS> JS: next week at 10:00AM for ONE WEEK ONLY
<MarkS> ...would like to get Nigel to attend, so we may move this meeting time again
JS: next week we meet at 10:00 AM Boston, after which we will look to find a different time
one that can accomodate Nigel as well
JS: we're done
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/K. Cooper/M. Cooper/ Found Scribe: MarkS Inferring ScribeNick: MarkS Found Scribe: JF Inferring ScribeNick: JF Scribes: MarkS, JF ScribeNicks: MarkS, JF WARNING: No "Present: ... " found! Possibly Present: JF JS MarkS P1 SM ShaneM ShaneM_ aaaa html-a11y-media inserted janina joined trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 24 Nov 2014 Guessing minutes URL: http://www.w3.org/2014/11/24-html-a11y-media-minutes.html People with action items:[End of scribe.perl diagnostic output]