See also: IRC log
<trackbot> Date: 07 January 2015
<janina> agenda: this
<fesch> zakim aaaa is me
<MichaelC> scribe: skeohane
michaelC: vacation Jan22
returning Feb 1
... later we will discuss which publication to focus on before
he leaves
janina: any addition or edits to last minutes meeting
RESOLUTION: publish minutes as submitted
<janina> next item
<janina> next item
michaelC, what was the action #?
JamesN: Action 1522 was to investigate overriding user stylesheet
MichaelC: user styles sheets may not be supported in all browsers
JamesN: chrome removed support for user stylesheets
<MichaelC> close action-1522
<trackbot> Closed action-1522.
MicahelC to send a note to WAI coordination group regarding this new information
MichaelC: working drafts CSS inline layout module level 3 and CSS box alignment module 3
<MichaelC> CSS Box Alignment Module Level 3
RichS: CSS is stepping on item beyond styling that's impacting accessibility
<MichaelC> CSS Inline Layout Module Level 3
MichaelC: read the abstract of the 2 working draft
Janina: it sounds like Alignment appears to have more impact to a11y
RichS: Bo Campbell has joined CSS WG
Janina: would love someone to join this call on behalf CSS
Cynthia: volunteer to review with a due date in late Feb
RichS: maybe Bo can work with Cynthia on this review
Janina: the problem is that there are so many specs, which one do we focus on
Fred: reviewed the spec, the ones of concern were with interactivity
<MichaelC> CSS Current Work
Cynthia: if CSS meets at the same time maybe we should have a quarterly joint meeting
RichS; trying to develop responsive design and they do not want to restructure their DOm for a11y
RichS: we may need to put in a formal objection
MichaelC: we need to collect use cases where it is not reasonable to restructure the DOM along with biz cases
RichS: Bo is representing a11y in the CSS WG
<janina> ACTION: Cyns to review http://www.w3.org/TR/css-align-3/ and http://www.w3.org/TR/css-inline-3/ due 20150222 [recorded in http://www.w3.org/2015/01/07-pf-minutes.html#action01]
<trackbot> Created ACTION-1549 - Review http://www.w3.org/tr/css-align-3/ and http://www.w3.org/tr/css-inline-3/ due 20150222 [on Cynthia Shelly - due 2015-01-14].
<janina> action-1549 due feb 22
<trackbot> Set action-1549 Review http://www.w3.org/tr/css-align-3/ and http://www.w3.org/tr/css-inline-3/ due 20150222 due date to 2015-02-22.
<lseeman> are we going to get to approving working drafts ?
<lseeman> like coga?
MichaelC: CSS usually argument is that it makes it easier for developers so if we assembly an argument to show that it actually not easier for developers
<richardschwerdtfeger> https://wiki.csswg.org/spec/css3-flexbox/accessibility
Janina: its worth thinking about a join call
Janina: Media Accessibility User
Requirements (MAUR) - can we prioritize it for Feb
publication
... check with Nigel regarding his comments
<ShaneM> I pinged Nigel again.
MichaelC: the soonest targeting
date is Feb 5
... has started drafting announcements
Janina: discussion will continue on Mondays call
Lisa: separated out the user
research for first working draft
... coga is cognitive accessibility task force
... pulling together different needs of the cognitive
disability user groups
... looking for feedback on the different challenges we
identified
... or possible research we missed
... looking for approval to publish as a first working
draft
<richardschwerdtfeger> ship it
RESOLUTION: teleconf approves publication of first public working draft of Cognitive Accessibility User Research
thanks!
MichaelC: we sent a comment
stating the indication should be available to ATs and user
agent need to make controls available to Ats
... last message where we ask a may to a must. they said they
would if they understood how to test it
<MichaelC> https://lists.w3.org/Archives/Member/wai-liaison/2014Dec/0010.html
MichaelC: we need to provide guidance on how to test or back off on the request
Janina: icon appears that notifies the user the content is mixed and we wanted the AT to be aware of it
Cynthia: manual testing, launch the browser, open the a11y inspector, tab through all the items. Its manual and platform dependent
<MichaelC> ACTION: cynthia to write up how to test a11y notifications of mixed content in response to https://lists.w3.org/Archives/Member/wai-liaison/2014Dec/0010.html [recorded in http://www.w3.org/2015/01/07-pf-minutes.html#action02]
<trackbot> Created ACTION-1550 - Write up how to test a11y notifications of mixed content in response to https://lists.w3.org/archives/member/wai-liaison/2014dec/0010.html [on Cynthia Shelly - due 2015-01-14].
MichaelC: in current browsers is that information available to ATs
Cynthia: security icon should be in IE and Firefox not sure about chrome
MicahelC: documentation how to do it and which browsers
Janina: only need to show that is
can be done
... top of hour, any items to address?