<scribe> scribe: Harper_Simon

<scribe> ScribeNick: sharper

Confirming schedule for remainder of 3Q, Sept 12 and Sept 26

Updates on mobile accessibility

<shawn> http://www.w3.org/WAI/EO/wiki/Mobile_Accessibility

Shawn starts to explain mobile accessibility

SLH: asking for comments
... nows the time to speak up.

ALL: No comment

<shadi> "This may be WCAG Techniques" -> "This may include ..."?

<shadi> "be" sounds limiting

<scribe> ACTION: Janina to review list of all w3c specs current and under development for additional specs relevant to mobile platforms [recorded in http://www.w3.org/2012/08/29-cg-minutes.html#action01]

<trackbot> Created ACTION-110 - Review list of all w3c specs current and under development for additional specs relevant to mobile platforms [on Janina Sajka - due 2012-09-05].

<shawn> ACTION: Janina review Standards for Web Applications on Mobile and see which ones we might want to highlight in the last bullet under http://www.w3.org/WAI/EO/wiki/Mobile_Accessibility#W3C_WAI_Addresses_Mobile_Accessibility [recorded in http://www.w3.org/2012/08/29-cg-minutes.html#action02]

<trackbot> Created ACTION-111 - Review Standards for Web Applications on Mobile and see which ones we might want to highlight in the last bullet under http://www.w3.org/WAI/EO/wiki/Mobile_Accessibility#W3C_WAI_Addresses_Mobile_Accessibility [on Janina Sajka - due 2012-09-05].

JB: Within staff having a series of discussions, as mobile is critical for WAI, redefining itself in - lots of work being done overall in W3C - already some guidance relevant to mobile accessibility. WAI CG needs to do more coordination and packaging - SLH is doing the packaging.
... making sure resource consumers have a good coordinated landing page.
... More focused on mobile for coordination - at next few cg meetings
... any other input for SLH on the page to date

<shawn> SH: coordinatation group wanted to contribute to the Note

<shawn> ... Is there anything specific the CG wanted us to include wrt the roadmap.

JB: think possible confusion re - road map
... one issue in-terms of research road map - and one re roadmap for coordination.

<shadi> http://www.w3.org/WAI/RD/2012/mobile/

<shadi> [[This symposium brought together researchers and practitioners to discuss these challenges and possible solutions, to help develop a roadmap for future research and development in the field.]]

<shawn> SH: concerned with the R&D aspects. roadmap comes from research from the syposium. research topics, e.g., accessibility & security...

<shawn> ... necessary for R&D commnuity to focus on in the future

<shawn> ... Research Roamap is fine - might even call it Future Directions

<shawn> .. asking for contributions or any text that the CG would want to include in the Note

<shawn> ... trying to get at that now. we're working on the Note now. want to include it from the start, rather than afterward

SAZ: suggest we invite chairs to comment on the RDWG Mobile note to help develop the draft
... bring people into the RDWG discussion.

JB: sees what gets lost when people don't talk together across groups. Could be effective - may end up with RDWG participants explaining and checking etc

<shadi> [[agrees - comments are passive while discussion implies that editors have pre-prepared questions for their peers]]

JB: bring people in to explain technical bits - keep feeding WAI-CG - RDWG needs to figure this out - what is the most efficient work model, with regard to group-to-group coordination, and getting outcomes from the symposia topics

<Zakim> jeanne, you wanted to ask that there be an emphasis on existing mobile work in WAI

JS: remembering from symposium day - number of speakers operating from a context of 'no accessibility standards' - JR presented existing work - we should include this.

JB: in terms of workflow from RDWG - JB: in there as a pre-publication check - also with CG is critical for workflow of note publication.

<Judy> ...in order that CG understands all the issues that RDWG is seeing, and either agrees, and takes on board the conclusions; or pushes back, and sorts things out.

<shawn> SH: afaik, we normally put things through CG, e.g., the Call for Papers. The Metrics note is the first one. Expect CG would read it. Not sure how W3C flow works?

SAZ: likes the scout analogy; we have a very tight time schedule trying to be affective and productive - trying to breakthrough to more challenging topics - don't want to be bogged down. We have had delays due to it being anew group. GC required as long as not impacting neg. on the group

<Judy> (Judy: RDWG may want to think of itself as scouts, out in the field ahead of other groups; and needing to say when you have the *results* of a session, "hey CG, this is what we found")

JB: thinking about what happens with the results of the outcomes
... what RDWG chooses to do with results is a critical question - want impact in the form of chances to the 'landscape'
... want to ID a follow up - or post it up so people can stumble across it
... Maybe worth a CG side pre-check - to avoid missed topics - run it through CG while polishing.

SAZ: able to get editors drafts out quickly - maybe best to get comments when we have something to get comments on
... for instance, TC maybe with the user agent groups and WCAG

SAZ each note is unique and will have a different tone.

JB: for w3c which has 300 or so member organisations - not just a question of having w3c groups as audience, or rest of the world - but also the w3c membership.
... good to think how we get to them - how are getting them interested in the next symposium.
... maybe come back to this in the next few months regarding very specific points - what relates to your group etc , can you take up the things we point out.

RESOLUTION: Updates on mobile accessibility approved

html & accessibility & formal objection

JB: ongoing series of challenging issues being negotiated between the accessibility and html WGs
... formal objections from PF since html trying to redefine ARIA
... important due to how expertise are acknowledge and horizontal dependancies are handled

<janina> https://lists.w3.org/Archives/Member/w3c-wai-pf/2012JulSep/0130.html

<Judy> the link from Janina is to the formal objection that is under expedited appeal at the moment

JS: seems to be a catalyst to get other objections heard

JB: questions and comments?

guidance for accessibility in contracts https://lists.w3.org/Archives/Member/w3c-wai-cg/2012JulSep/0013.html

<Judy> BSI 8878

<Judy> or EOWG docs, or EOWG docs-in-dev

JS: ran into people and organisations, making new website - seems that it is common to get contractors - maybe useful to put out guidance on contracting an accessible site

SLH: we had talked about this in EO - not made a priority - consider this via WAI-Engage - people happy to share language - open up as a topic so we get a crowd-sourcing approach.

JB: the concept of commissioning BSI 8878 - http://en.wikipedia.org/wiki/PAS_78

<shawn> [ we also had on EOWG's wishlist guidance on selecting accessibility specialists]

http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030129227

JB: maybe better for EO instead of WAI-Engage as there are some subtleties, not sure

<jeanne> it also needs to have an international orientation

JB: may want this to be authoritative via EO

SAZ - may not have to be either / or - could be both - community group could do a lot of pre-work

<janina> Burger King Delivers: http://bkdelivers.com

<Zakim> shawn, you wanted to say cannot be priority for EOWG. agree can use WAI-Engage as gathering ideas. and might polish as WAI Resource in the future

SAZ: info could flow into EO from community group

SLH: can't be a priority for EO right now - use engage first - polish and publish in the future

<Judy> actually the replacement link should be http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030180388

replacement link for latest version: http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030180388

]

<shawn> SH: worried if North American centric

<shadi> +1

<shawn> +1

<Zakim> shawn, you wanted to say will actively get broader

SH: need an international perspective regarding legal

<shawn> SLH: Will actively get broad international input

SAZ: agrees on international perspective - BSI attached to UK legal system - we want international

JS: hopeful international issues dealt best with in w3c

RESOLUTION: next meeting in 2 weeks

<scribe> topic : publications check

<shawn> https://www.w3.org/WAI/CG/Group/announcements

SAZ: WAI-ACT mid September / RDWG - Metrics published tomorrow

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/inlude wrt the roadmap/include wrt the roadmap/
Succeeded: s/work model/work model, with regard to group-to-group coordination, and getting outcomes from the symposia topics/
Succeeded: s/through CG./through CG, e.g., the Call for Papers./
Succeeded: s/teh/the/
Succeeded: s/with/while/
Found Scribe: Harper_Simon
Found ScribeNick: sharper
Default Present: Shadi, Judy, Janina, Jeanne, Shawn, sharper
Present: Shadi Judy Janina Jeanne Shawn sharper

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 29 Aug 2012
Guessing minutes URL: http://www.w3.org/2012/08/29-cg-minutes.html
People with action items: janina

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.