- From: Mark Sadecki <mark@w3.org>
- Date: Mon, 27 Jan 2014 18:41:57 -0500
- To: HTML A11Y TF Public <public-html-a11y@w3.org>, public-canvas-api@w3.org
Hello,
The minutes for the Canvas Accessibility Sub Group Teleconference 27 January 2014 are available in HTML and plain text below. Supporting information for this Sub Group can be found on the wiki: http://www.w3.org/WAI/PF/HTML/wiki/Canvas
HTML: http://www.w3.org/2014/01/27-html-a11y-minutes.html
TEXT:
[1]W3C
[1] http://www.w3.org/
Canvas Accessibility Sub-Group Teleconference
27 Jan 2014
See also: [2]IRC log
[2] http://www.w3.org/2014/01/27-html-a11y-irc
Attendees
Present
Mark Sadecki, Jay Munro, Jatinder Mann, Rich
Schwerdtfeger, Rik Cabanier
Regrets
Chair
Mark Sadecki
Scribe
Mark Sadecki
Contents
* [3]Topics
1. [4]Review, verify and close remaining bugs for L1 (see
below)
2. [5]23982 Focus Ring out of canvas
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23982
3. [6]23983 Scrolling the focus into view
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983
4. [7]24340 Change reference to the phrases "focus ring"
and "focus region" to "focus outline"
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24340
5. [8]Code Example
6. [9]Testing
* [10]Summary of Action Items
__________________________________________________________
<trackbot> Date: 27 January 2014
<scribe> Meeting: Canvas Accessibility Sub-Group Teleconference
<scribe> scribe: MarkS
Review, verify and close remaining bugs for L1 (see below)
23982 Focus Ring out of canvas
[11]https://www.w3.org/Bugs/Public/show_bug.cgi?id=23982
[11] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23982
JMunro: Seemed pretty straightforward. I made the changes
<JatinderMann>
[12]http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/
#dom-context-2d-drawfocusifneeded
[12] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-drawfocusifneeded
RS: not every platform may support an AAPI. We can say "if". Do
you think we need that?
JMunro: how about if supported?
<JatinderMann> Revision: "The full location of the
corresponding fallback element is passed to the accessibility
API is supported."
<JatinderMann> Sorry, revision: "The full location of the
corresponding fallback element is passed to the accessibility
API if supported."
RS: does the clipping region include the bounds of the canvas
element?
RC: is that a problem?
... by default the clipping region is infinite
RS: somewhere we should say that its clipped to the canvas
element
RC: It's implied. shouldn't be necessary
... this should answer Apple's question
23983 Scrolling the focus into view
[13]https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983
[13] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983
RS: looks good to me
24340 Change reference to the phrases "focus ring" and "focus region"
to "focus outline"
[14]https://www.w3.org/Bugs/Public/show_bug.cgi?id=24340
[14] https://www.w3.org/Bugs/Public/show_bug.cgi?id=24340
MS: looks like there are no more references to rings or regions
RS: is there a reason we have current path and event loop
underlined?
JMunro: its underlined throughout the entire section. I
copy/pasted it from another reference
<richardschwerdtfeger> The context always has a current default
path. There is only one current path, it is not part of the
drawing state. The current path is a path, as described above.
MS: they all have a span element
JMunro: that is a holdover from when Path object was still in
there
... I can take all of those out.
Code Example
MS: there is a code example at the bottom of this spec. should
we add an example of using drawFocusIfNeeded?
JMann: The old example wasn't working in any browser.
... could benefit from a simpler example.
MS: Jay, if you send me the old example, I can slim it down and
update it.
Testing
MS: I will list all of the testable statements this week and
get started on writing tests. will update you if I need any
help.
RS: how are we doing with implementations?
RC: Mozilla expressed some concerns that hit regions should be
used for this. Don't like updating AAPI with regions. Seem like
they can be convinced though.
... another concern was if there would be a conflict when we do
add hit regions.
JM: we should also ping other implementers to let them know the
spec has been updated
RC: I will try to do that this week
... Step 4 says that "Inform the user that the focus is at the
location given by the path." I think that is still a little
unclear
... there is no focus at that point.
... maybe focus should go away there.
JMann: " inform the user of the location given by the path"
<JatinderMann> 4.Inform the user of the location given by the
path.
JMunro: yeah sure, that makes sense
JMann: just want to add an action item to share this with
everyone that should be reviewing it.
Summary of Action Items
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [15]scribe.perl version
1.138 ([16]CVS log)
$Date: 2014-01-27 23:40:20 $
[15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[16] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 27 January 2014 23:42:04 UTC