See also: IRC log
<trackbot> Date: 27 January 2014
<scribe> Meeting: Canvas Accessibility Sub-Group Teleconference
<scribe> scribe: MarkS
JMunro: Seemed pretty straightforward. I made the changes
<JatinderMann> 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
RS: looks good to me
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.
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.
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.