W3C

Canvas Accessibility Sub-Group Teleconference

20 Jan 2014

See also: IRC log

Attendees

Present
Mark Sadecki, Rich Schwerdtfeger, Jatinder Mann
Regrets
Rik Cabanier
Chair
Mark Sadecki
Scribe
Mark Sadecki

Contents


<trackbot> Date: 20 January 2014

<scribe> Meeting: Canvas Accessibility Sub-Group Teleconference

<scribe> scribe: Mark Sadecki

<scribe> scribeNick: MarkS

Review, verify and close all open bugs for L1

-> http://j.mp/1hGWiDK Canvas 2d accessibility related CR bugs

<JatinderMann> http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-drawfocusifneeded

23978

-> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23978 23978 Informing the user shouldn't be optional

JMann: notice that we are still using the word "ring" a lot.

RS: We could use the word outline instead?

JMann: I like outline. Don't want to confuse the user by referencing ring (the old method name)

MS: I'll open a new bug on outline

RS: I don't see anything about this being optional, so that is good.
... want to check on the scrolling part of this

<JatinderMann> If the focus region is not on the screen, then scroll the region into view when it receives focus.

JMann: the last sentence of section 3

RS: do we want it to be similar to scrollPathIntoView?
... take a look at the L2 text

<JatinderMann> http://www.w3.org/html/wg/drafts/2dcontext/master/

<richardschwerdtfeger> Scroll notional child into view with the align to top flag set.

<richardschwerdtfeger> vertical-align:text-top;

JMann: scroll the region into view by aligning it to the top

<JatinderMann> If the focus region is not on the screen, then scroll the region into view by aligning it to the top when it receives focus.

<JatinderMann> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983

<JatinderMann> If the focus outline is not on the screen, then scroll the focus outline into view by aligning it to the top when it receives focus.

JMann: I'll add a comment to 23978 regarding this note
... I will close this but

23980

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23980

http://www.w3.org/2014/01/20-html-a11y-minutes.html

JMann, this one has been fixed, so I will leave a comment and close it out.

23981

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23981

JMann: We agreed to WONTFIX this one
... PLH agreed nothing needed to be done

RS: so lets close this one

<JatinderMann> http://www.w3.org/2014/01/13-html-a11y-minutes.html

23982

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23982

Focus Ring out of canvas

<JatinderMann> The focus ring should not be subject to the shadow effects, the global alpha, or the global composition operators, but should be subject to the clipping region. (The effect of transformations is described above and varies based on which path is being used.) When the focus area is clipped by the canvas element, only the visual representation of the focus area is clipped to the clipping region. The full location of the corresponding fallback el[CUT]

<JatinderMann> When the focus area is clipped by the canvas element, only the visual representation of the focus area is clipped to the clipping region. The full location of the corresponding fallback element is passed to the accessibility API.

JMann: if we change this to focus outline, will that close this one?

-> https://www.w3.org/Bugs/Public/show_bug.cgi?id=24340 Change reference to the phrases "focus ring" and "focus region" to "focus outline"

JMann: transformations will affect focus outlines. If I draw one rectangular path doing an hour hand, my focus path will continue rotate. Maybe we call it out, maybe not...
... I think this needs more work

RS: agreed

JMann: Should be a MUST, not a SHOULD requirment

RS: informing the user could mean calling the AAPI

JMann: lets keep the change out of the note so its normative

<richardschwerdtfeger> When informing the user of the of the fallback element involves passing the location to a platform accessibility api the location is not subject to clipping.

JMann: i think i agree. We can move the sentence from 3 and put it in 4
... we want to say inform the user and that the location is not subject to clipping
... I'll work with Jay to clean this one up a bit
... keep the first sentence in step 3 and the second sentence in step 4
... we'll figure something about the bracket section too

23983

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983

Scrolling the focus into view

JMann: I'll mark this one as assigned. I updated this one with the feedback. Still working on it. Just need to add new text

23986

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23986

Current default path

<JatinderMann> If the current path has zero subpaths, then abort these steps.

JMann: the first sentence.

RS: this one is fixed
... we can close this one

JMann: OK, I closed it and left a comment

23987

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23987

Empty path and drawSystemFocusRing

JMann: this one is tied to 23986. This one can also be closed.
... left a comment and closed.

JMann: after we make these two more spec changes, I'll circulate to the list.
... would like to get confirmation from dominic and apple that they are happy with the new changes

Testing

RS: one thing we can do for testing with the clipping one, take the test I have checkboxes and make the canvas really small.

MS: I'll write out all the testable statements so we at least know what needs to be tested.

MS: I can take a stab at writing some tests.

Next Meeting

RS: lets stay in touch to see what comes out of the TF meeting and any emails circulated to implementers to see if we need to have a meeting next week.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014-01-21 00:21:25 $