<trackbot> Date: 25 June 2015

clear agenda

clear agenda

Having Webex issues again!

Improperly setup Webex

Won't start without a host

<chaals> url for webex meeting…

Still no joy on Webex

Did you succeed getting on Webex? I'm still failing

Code I'm trying to use is: 643 822 343

I can't use the URI approach

<paulc> only on IRC for now - in a noisy airport lounge

Folks, we're on Webex, not Zakim!

<scribe> scribe: janina

any other items for the agenda?

cn: Any additions?

transcript: <http://chaals.github.io/html-transcript/html-transcript-src.html> CfC <https://lists.w3.org/Archives/Public/public-html-a11y/2015Jun/0077.html>

<chaals> JS: He has them done, Chrome is failing.

<chaals> … he wanted to talk about it early, but isn't here.

<chaals> … Firefox is passing. Chrome isn't talking to the accessibility APIs

<chaals> RS: You have to turn on some flags for Chrome - may be that.

<chaals> JS: Yes, but this put hit regions at risk.

<chaals> RS: That's OK...

<paulc> Publication of the Canvas2D CR will probably be next week on Thu Jul 2

<chaals> MS: PLH sent us a personal email summarising this - fre-orwarded to you just now.

<chaals> ACTION: Rich to talk to PLH urgently in order to work out if Chrome really passes or fails on HitRegions [recorded in http://www.w3.org/2015/06/25-html-a11y-minutes.html#action01]

<trackbot> Created ACTION-326 - Talk to plh urgently in order to work out if chrome really passes or fails on hitregions [on Richard Schwerdtfeger - due 2015-07-02].

any other items for the agenda?

transcript: <http://chaals.github.io/html-transcript/html-transcript-src.html> CfC <https://lists.w3.org/Archives/Public/public-html-a11y/2015Jun/0077.html>

cn: Open CfC to have the TF accept the draft as a TF endeavor
... Silvia says we can't make this a WD yet,
... Clarified that we expect to choose one of the two options
... CfC through Friday
... How to proceed? I'd prefer github and the TF or github issue tracker
... Any preference?
... If no preference voiced, we'll take the decision at executive level

bug triage

cn: All filed bugs through last Friday reviewed
... about 25 left
... Fall into three groups
... Things we agree to do -- Once the HTML docs approach is settled
... Second group is Alt Guidance issues
... Third is bugs related to kybd and focus work -- We don't yet have these answers
... No Bug Triage mtg this week

are we on track for canvas

<paulc> WG Decision to move Canvas2D to CR: https://lists.w3.org/Archives/Public/public-html-admin/2015Jun/0022.html

plh: Have put HIt Region AtRisk
... Realized Chrome not properly implementing hit region, because not reporting to a11y apis

rs: Did you turn the mapping features required?

plh: I did turn one on, are there more?
... Rich, Did you get the reporting working?

rs: I did not test yet
... Chrome tends to not turn on api mappings unless AT running
... With JFW running, ... did you use insepct tool?

<plh> http://plehegar.github.io/wpt-canvas/2dcontext/hit-regions/addHitRegion.IDNotNullPreviousInList-manual.html

<MarkS> chrome://accessibility/

ms: Put the above in, may give better results. It turns a11y mode globally

<Judy> [JB: So then the test should be modified to clarify everything that needs to be turned on when testing the feature, right?]

jb: Let's at least agree what we need to update ... Test expectations?

cn: Chrome has particular behaviors

plh: Can someone else run the test?

<Judy> jb: then we should also document how to ensure that the tests work for those particular behaviors

cn: If Chrome passes then hit regions is no longer at risk? Yes?

plh: Yes

pc: WG decision was to mark hit regions at risk
... Don't want to reconsider the CfC

cn: We agreed to "at risk"
... Our concern is how to satisfy the concern

<paulc> We expect the CR to be published on Thu July 2.

<chaals> ACTION: Marks to check if chrome hitregion implementation actually works [recorded in http://www.w3.org/2015/06/25-html-a11y-minutes.html#action02]

<trackbot> Created ACTION-327 - Check if chrome hitregion implementation actually works [on Mark Sadecki - due 2015-07-02].

plh: No impact on publication

lq: An updated version available ...
... Expect reviewable doc next week
... So far, added new intro text
... Inst3ead of many examples, I'm explaining principals, then examples

cn: Soujnds an improvement to have the intro
... Examples very helpful

<liam> http://rawgit.com/w3c/alt-techniques/master/index.html

jf: Don't think multiple examples isn't important
... Question was how many examples do we need
... Decision was for more examples

<MarkS> +1

jb: Concerned that we're using the spec for examples
... What's the eventual intent? All of this for the spec doc?

lq: My next step is to ask which examples should stay in the spec, and which go to the resources page

<Zakim> liam, you wanted to respond and thank for the fedback

<Zakim> chaals, you wanted to ask if we should file pull requests

cn: Current working resolution is that we work on this until material is technically correct, then figure out where it needs to be

nc: Spec currently says Bugzilla ... Continue that? Or go github?

lq: Currently not looking either place, and have no preference. Will monitor
... We don't yet know where HTML is going on that

<Zakim> liam, you wanted to note things like ARIA described-by are an issue

lq: Think it very good that we have the reference out of the spec to external resources
... ARIA Describedby and Describedat not mentioned yet.
... I'm adding. But external is important just for this kind of maturing markup

<paulc_> HTML 5.1 at http://www.w3.org/TR/html51/semantics.html#alt mentions "Additional guidance and techniques are available in Resources on Alternative Text for Images." which links to http://www.w3.org/WAI/alt/

pc: Asking where we intend updated material will go ...

cn: Reiterates that we will decide what goes where

jb: Believe PC is pretty much correct -- Examples mostly external

<paulc_> Thanks, judy

Action item review: https://www.w3.org/WAI/PF/HTML/track/actions/open

<chaals> action-326?

<trackbot> action-326 -- Richard Schwerdtfeger to Talk to plh urgently in order to work out if chrome really passes or fails on hitregions -- due 2015-07-02 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/HTML/track/actions/326

rs: Looking at hit regions ...
... Getting x coordinates correct, but y wrong
... So two bugs to file
... Mark, can you follow up with Dominec

<plh> Prsent+ PLH

rs: We're getting two buttons with same ID. Believe fist of those was to have been deleted

plh: A blocking bug?

rs: Yes

<plh> https://code.google.com/p/chromium/issues/list?can=2&q=addHitRegion&colspec=ID+Pri+M+Week+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&cells=tiles

rs: FYI I'm on vacation first weeks of July
... Believe Dominec thinks bugs are fixed
... Mark agreed to follow up.

ms: Yes. Will verify and follow up

<chaals> close action-326

<trackbot> Closed action-326.

<chaals> close action-325

<trackbot> Closed action-325.

<paulc_> Charles: When the transcript CfC closes in the TF is there anything you need done at the WG level at this time?

<paulc_> Thanks

<chaals> CMN: No, we just make an editor's draft for the TF.

<chaals> [adjourned]

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/Chaals, PLH asked to take up Canvas early in the call. Can we switch agenda 2 and 3?//
Found Scribe: janina
Inferring ScribeNick: janina
Default Present: [from_janina]
Present: JF Janina Joanmarie_Diggs RichS [from_janina] paulc Liam PLH Judy MarkS
Regrets: Léonie

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

Found Date: 25 Jun 2015
Guessing minutes URL: http://www.w3.org/2015/06/25-html-a11y-minutes.html
People with action items: marks rich

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