See also: IRC log
JS: any revisions, ommissions, etc.?
RESOLUTION: publish minutes as submitted
JS: nothing specific, but some interesting rumors brewing
requested to use the designated hotel, helps to off-set costs
JF: I reached out to the CSS WG about coordinating with CSS WG - wonder if we should try and connect with them there
MC: a request should go from chair to chair. we might need to spend some time preparing for that first, requiring a deeper dive over the next while
JS: this is related to an older action item on me
MC: could also try another of the
co-chairs
... Peter Lintz (sp), Liam Quinn, Doug Sheppers, Bert Boss ,
Chris Lilley (sp)
JF to re-copy all of the list of the request
MC: James has looked at Content Securty Policy
as understood, the user agent has the option to ignore it, although acripts exempted could still run
possible...potentially... there is a method where the User Agent delivers an audit if meets/fails
can forsee some using that to lock out some users - does not appear to have an option to disable that
If a user is using something that causes a security fail... then they *might* be locked out. Need more review. Unable to better document this at this time due to other commitments
MC: any value in noting this for the other reviewers?
LS: is this the one I commented on?
JS: I don't think it was this Lisa - you are welcome to read and review however
<MichaelC> Content security policy level 2
<MichaelC> close action-1481
<trackbot> Closed action-1481.
MC: action on JS to discuss DOM with Web Apps group
JS: not done yet. should continue however - discussed last week at HTML-a11y call
Shane is working on that... details TBC
<MichaelC> action-1376 due 1 week
<trackbot> Set action-1376 Review css grids http://www.w3.org/tr/css-grid-1/ due date to 2014-07-30.
<MichaelC> action-1377 due 1 week
<trackbot> Set action-1377 Review css fragmentation http://www.w3.org/tr/css3-break/ due date to 2014-07-30.
<MichaelC> Mixed Content
MC: first glance seems that there is no impact on a11y
JS: we looked and determined that
it was not an issue - we did have a question about DOM4
however, as previously discussed
... looking for/at events enumerator
zakimj, next item
JS: heartbeat doc is being held up due to paperwork
sitting with Judy at this time
likely will not publish in the next 2 weeks
JS: have been asked to meet with Digital Publishing IG
discussed this 2 weeks ago - looking to shift meeting time to 1:00 PM Boston Mondays
everyon who we need to bring to the table available at that time
looking at the 25th Aug @ 1:00 PM Boston
JS: questioning the time now
LS: recall noting it was 10 PM my time
MC: looks like you typed to
Monday (ARIA call)
... looks like the scheduling of this went awry, but we should
try and use that slot (ARIA time)
JS: will discuss with Rich, we
have a month
... apologies
JS & MC: logistics details
JS: wanted to bring this to everyone's attention
this is the second one, the original one was in San Francisco earlier this year
this event kicked off the discussion on the Web Apps work we are in discussion with now
JS: travle booster for BErlin - great city to visit
it would be great if we had representation there
JS: not sure if we have enough on the call to discuss this
first surfaced on the ARIA call - do we keep actions open until resolved, etc.
MC: did want to discuss this, but wanted others here as well. LIkely will send out an email proprosal
JS: think James had a good construct for a closing trigger - if we have a decided wording we can close, if it is "proposed" them we leave it open
MC: will send out a proposal for further discussion
JS: agreed that we need to document how we do this - a written record that can be reviewed
its about efficency
MC: had an action to word a comment to the CSS WG - but struggled what to say exactly WRT spec edit
seems it may be more of a WCAG proposal - not so much a spec item but a best practices/authoring guide item
JS: perhaps James can add this to the techniques group
JN: can add to wiki - work is
being done in the main group these days
... if someone can outline what techniques need to be created,
we can add it to the list
MC: something like using the speak-as property
JN: does that work?
MC: not yet... but it might be a
technique we document now
... ...when bullets convey meaning
JN: isn't speak-as more about punctuation, or spellout
MC: that is correct, can define
bullet styles...
... cannot speak to importance for this
CS: is there a section for future considerations? to track?
JN: not yet, but we can do so. seems like a punting exercise. Better to add to the main list with a note to watch
MC: would this go under CSS techniques?
JN: yes, but unclear on how to make this work
<jamesn> https://www.w3.org/WAI/GL/wiki/Techniques/ToDo
MC: adding to the wiki now
JS: assuming that we would like this supported. Do we have enough in the spec to do so?
MC: this might relate to the
Accessibility API comment from Lisa
... issue is that we really don't have such a thing for CSS
MS: propose that we start this discussion with the CSS WG - start a CSS mapping guide
group: possible TPAC item
JS: lets start that for this group then
MC: adding to my To Do list
<MichaelC> close action-1433
<trackbot> Closed action-1433.
discussion about other CSS Related items - now lookin at Borders
CS: sent out a note a long time ago, unsure of status
MC: I was supposed to send along the comment - appears that it didn't go out
CS: believe we were going to discuss with CSS where high-contrast media queries would/should live
MS: we have a media vendor prefix media query that does that now - works quite well
CS: can we add that to the WCAG list of potential techniques discussed earlier?
MC: yes
CS: something like using CSS borders to draw focus ring
MC: reviewed an email for feature request of this to CSS WG - will send email
<MichaelC> close action-1387
<trackbot> Closed action-1387.
<MichaelC> action-1387: https://lists.w3.org/Archives/Member/wai-liaison/2014Jul/0002.html
<trackbot> Notes added to action-1387 Review css 3 background and borders spec.
MichaelC having issues with rrsagent & zakim, cannot close meeting/ MichaelC having issues with rrsagent & zakim, cannot close meeting