<trackbot> Date: 25 July 2012

<Judy> IndieUI Update

<scribe> scribe: Loretta

JB: W3C rotates the location of its meetings (Advisory, TPAC). Looking for input on holding TPAC in China in 2013.
... Looking for informal input on which groups might be interested in holding meetings at a TPAC in 2013, whether there would be special travel issues, etc.

JR: ATAG doesn't seem to be able to travel much. We tend to do best in the US.

JB: No invited experts are in China, so that is an issue. But even for companies that have travel resources, accessibility doesn't seem to be able to get them.

JS: +1, and adds that scheduling over the Halloween weekend is an additional problem/burden for people.
... The Halloween schedule is costing us attendance this year.
... Also, why China rather than Korea or other Asian locations?

JB: Because of new members from China, and trying to engage new companies in China.

JS: Maybe this makes it a good recruiting opportunity for WAI.

JB: With focus on mobile in IndieUI, , maybe this is a good opportunity to pull in partiicpation from phone companies.

LGR: WCAG isn't meeting these days at all, so probably wouldn't meet there.

Possible China TPAC

<Zakim> shawn, you wanted to say we talked about this among WAI staff - including outreach opportunities, etc.

SH: We did discuss outreach opportunites at the WAI staff meeting.

JB: WAI does some small amount of participant support for travel by invited experts. I've put in an inquiry about availability of such resources.

<Judy> ...but no idea whether there will be resources from W3C.

PFWG's proposed approach with CSS Flex Box

JS: CSS has a module proposing to go to CR. PF asked to review it. We see good news and bad news.
... We wanted to keep the rest of WAI informed, and seek feedback.
... Flex Box will allow relayout possibilities on a page.
... If this had appropriate support in browsers, this could be a bit accessibility benefit.
... But it isn't clear browsers are stepping up on this.
... PF isn't clear how to proceed. One option: add a note in the spec. Meanwhile, request support for taborder and reordered taborder.
... PF will ask WCAG to include techniques for this feature.

Jeanne: What does taborder have to do with Flex Box.

MC: Flex box allows you to position a number of items, e.g., a div element with 4 span elements inside . Flex Box lets you ay that spans should grow the same amount as each other, etc.
... Flex Box also lets you reorder the items, e.g., display these in reverse order as the source code.
... That is where we get a taborder problem, since taborder will follow source code order. This means that focus will go backwards through the reversed items.

JS: Especially a problem if you are also looking at it..

MC: We think Flex Box is a good thing, but we think this problem should be solved. Right now, certain uses of Flex Box can create a usability problem for some people.

JB: Given that they are ready to go to CR, but this isn't yet solved, are we asking for a solution to be developed during CR?
... It is important that we be clear about what we are requesting.

JS: They know we have a serious concern about tab order. We haven't dropped the ball, but neither have they picked up the ball.
... Our relationship with CSS WG seems to be good and productive.

MC: They are away that we have a taborder issue, but I'm not sure how high it is on their radar that this affects Flex Box.

JB: This could affect their implementations for CR, since implementation might need to change to accommodate the solution. So we need to negotiate how to address this problem without throwing off their entire schedule.
... You need to have a discussion with the CSS folks directly.

take up next item

close item 1

close item 2

take up next

take up item 3

JB: WCAG2ICT is be going out, probably Friday.
... The original date was tomorrow, but that is the anniversary of the ADA, and publishing on that date is often interpreted as relating to ADA.
... We don't want to give that message about this document. This is only intended to be an information note.
... We are not the appropriate organization to be publishing guidelines for non-Web content. This is just meant to be informative guidance about how WCAG might be interpreted inthis context.

<MichaelC> http://www.w3.org/TR/2012/WD-wcag2ict-20120726/

JR: Is there an editor's draft, or will this be the first draft?

JB: This is the first TR draft. There is an editor's draft, but it is just a few days old. There is also a Google Docs site for working materials.

SH: I can't imagine that the Task Force would object to moving the date.to Friday.

JB: Michael, please change the staging to publish Friday.

MC: Do we also need to change the date on the Understanding document?

JB: I don't think that is necessary to change.

SH: We have no plans to announce the updated Understanding document.

LGR: I think we should.

JB: Just to clarify: the drop dead date is this week. We thought that we needed to publish Thursday to make this week.

<Judy> ...because we thought we could not publish on a Friday. But we negotiated a one-time way to do that.

(Much discussion about ICT document, Understanding document, public reviews, ...)

<shawn> ftr, /me was not aware of the updates to Understanding until now

JB: Review requests probably need to go to different audiences. The updates to Understanding are explicitly in regard to web, although they relate to the ICT comments.
... The people who track just the Web should be looking at these changes, but may not want to be reviewing the ICT document.

SH: If it weren't for the ICT, we wouldn't be doing an update to Understanding?

JB: This is leading me more towards Friday, since we uncovered unexpected work here.

Next meeting sched

JB: I will put out a questionaire for the remaining quarter dates.

<shawn> no regrets from me

<Judy> === please note availability yes/no first for Aug 1==========

<janina> +yes

<jeanne> jeanne is available on 1 August, but not on 8 August (vacation)

<Judy> +yes

<shawn> yes

<Jan> yes to both

<MichaelC> at the moment my calendar shows availability for 1 Aug

<Judy> === please note availability yes/no first for Aug 8==========

<MichaelC> at the moment my calendar shows availability for 8 Aug

<Jan> yes

<janina> yes to Aug 8

<Judy> maybe

<shawn> yes

JB: Tentative date for next CG meeting; Aug 1

<Judy> Tentative for AUG 1st as next meeting, to be confirmed

<Judy> s/Tentative for AUG 8th as next meeting, to be confirmed//

HTML 5 in TR specs

MC: I started using HTML5 Respec for the 2ICT document. But during the task force review, Kiran says that JAWS has a bug and does't handle handings properly for HTML5.

MV: I converted to HTML1 and it works better for him.

MC: Is this an issue we need to raise?

JB: I asked some questions about Respec, and it sounds like they are abandoning it.

MC: Probably Respec isn't totally abandoned, but abandoned for W3C-wide publications.

<jeanne> It will not be required, but it will continue to be supported. That was my understanding from the meeting.

JB: I suggest you touch base with the systems team for more information.

JS: Should this be a JAWS fix?

MC: HTML5 is an exception to the W3C rule that specs can only be published in published W3C formats.
... The user agents issues demonstrate the value of this rule.
... But it is considered appropriate for HTML5 to publish using HTML5.

JS: Are there other accessibility support issues? I'd be more comfortable if this were more than just a JAWS problem.

MC: There is a complicated algorithm that applies to header elements in sections. I doubt that user agents are yet supporting this.

JB: What is the most efficient way to move forward?

MC: The problem isn't in HTML5. It is a problem in implementation, and W3C Pub Rules.

JB; We could also take it to the vendor. They need to fix it ASAP.

JB: I don't think we'll get HTML5 deauthorized as a spec to publish in.

JS: If it shows up in multiple user agents and multiple ATs, then this is a wider issue with publishing in HTML5. We need more information.

<Judy> JB: thinks that there may actually be an HTML5 bug in terms of lack of graceful degredation violating their own design principles

JB: How can we get more data?

Jeanne; Is this asking people with different screen readers to test?

JB: yes

<shawn> [ Shawn could do on EOWG, too ]

JS: maybe we can do this at Friday's meeting.

SH: I can also ask EO to test.
... Are we comfortable sending this request to a mailing list?

JB: Yes, finding out support for Header does not seem like a sensitive question.

Jeanne: Is there a test page to use?

JB: Any W3C spec published in HTML5. Can anyone identify one?

MC: It would need to use the section element.

<jeanne> Recent CSS specs use Respec.

JB: asks SH and MC to take this offline (identifying suitable test page)

q

<Zakim> jeanne, you wanted to ask the JAWS version?

Publications timing & automation

JB: Trying to make the publication process more flexible, so publication can take place more days a week.
... WAI pushing back on accessibility exceptions.

MC: One thing we gained with restricted publication dates was a shorter notice requirement, which has helped me. If expanding the dates changes that, it would not be a win.

JB: They would be tryign to go the other way, with a shorter notice requirement.

JR; Are there potential downsides/

<jeanne> What they are talking about is not requiring notification, just a form to say publish, and then insta-publish

JB: The changes are around making the system team's work easier. It may come at a cost of less accessibility of published documents.

<jeanne> All the ATAG and UAAG specs refer to Apple accessibility docs, which have an invalid URI, therefore it would require manual publishing.

JR: On day of the week, I'm fine either way.

MC: Restricted dates helps focus the WG on finalizing. More flexibility may tempt groups to slip deadlines.

JB: Groups that meet on Wed often can't publish until the following Tues. That is one problem they are trying to address.

MC: I always tell groups I need a final draft a week in advance.

JB: zakim, close current item

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/2012/2013/
Succeeded: s/IndyUI/IndieUI/
Succeeded: s/benegit/benefit/
Succeeded: s/update?/update to Understanding?/
Succeeded: s/Tentative for AUG 8th as next meeting, to be confirmed//
FAILED: s/Tentative for AUG 8th as next meeting, to be confirmed//
Succeeded: s/Kieran/Kiran/
Found Scribe: Loretta
Inferring ScribeNick: Loretta
Default Present: Shawn, Jeanne, Michael_Cooper, Judy, Janina, Jan, [Google]
Present: Shawn Jeanne Michael_Cooper Judy Janina Jan [Google]
Regrets: Jim_Allan

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

Found Date: 25 Jul 2012
Guessing minutes URL: http://www.w3.org/2012/07/25-cg-minutes.html
People with action items: 

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