RE: Minutes: Canvas Accessibility Sub Group Teleconference, 20 January 2014

We're almost there on the CR. The edits from the bugs are in (for both CR & L2). I believe those are the only bugs brought up for the CR. I'd like to see the A11y/canvas task force take one last look at the edits from the bugs, and we'll be ready to go on the CR. 

If the team has any changes on the CR, they'd need to be replicated to the Level 2 spec, but that shouldn't take any time. 

I'd say we should be ready by mid next week if everyone agrees. 

-Jay 

-----Original Message-----
From: Paul Cotton 
Sent: Tuesday, January 21, 2014 6:14 PM
To: Rik Cabanier (cabanier@adobe.com); Jay Munro; Jatinder Mann; Eliot Graff; wiltzius@google.com
Cc: Mark Sadecki; HTML A11Y TF Public; public-canvas-api@w3.org; Sam Ruby (rubys@intertwingly.net)
Subject: RE: Minutes: Canvas Accessibility Sub Group Teleconference, 20 January 2014

Given that all the Canvas 2D CR bugs now appear to be resolved [1], when will the Sub Group and the Canvas Editors be ready to provide a revised Canvas Last Call working Draft and a Canvas L2 heartbeat Working Draft for a publication CfC by the HTML WG?

/paulc
HTML WG co-chair

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

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

-----Original Message-----
From: Mark Sadecki [mailto:mark@w3.org] 
Sent: Monday, January 20, 2014 7:06 PM
To: HTML A11Y TF Public; public-canvas-api@w3.org
Subject: Minutes: Canvas Accessibility Sub Group Teleconference, 20 January 2014

Hello,

The minutes for the Canvas Accessibility Sub Group Teleconference 20 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/20-html-a11y-minutes.html

TEXT:

    [1]W3C

      [1] http://www.w3.org/

             Canvas Accessibility Sub-Group Teleconference

20 Jan 2014

   See also: [2]IRC log

      [2] http://www.w3.org/2014/01/20-html-a11y-irc

Attendees

   Present
          Mark Sadecki, Rich Schwerdtfeger, Jatinder Mann

   Regrets
   Chair
          Mark Sadecki

   Scribe
          Mark Sadecki

Contents

     * [3]Topics
         1. [4]Review, verify and close all open bugs for L1
         2. [5]23978
         3. [6]23980
         4. [7]23981
         5. [8]23982
         6. [9]23983
         7. [10]23986
         8. [11]23987
         9. [12]Testing
        10. [13]Next Meeting
     * [14]Summary of Action Items
     __________________________________________________________

   <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

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

     [15] http://j.mp/1hGWiDK

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

     [16] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-drawfocusifneeded

23978

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

     [17] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23978

   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>
   [18]http://www.w3.org/html/wg/drafts/2dcontext/master/

     [18] 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>
   [19]https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983

     [19] 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

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

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

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

     [21] 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

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

     [22] 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>
   [23]http://www.w3.org/2014/01/13-html-a11y-minutes.html

     [23] http://www.w3.org/2014/01/13-html-a11y-minutes.html

23982

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

     [24] 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?

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

     [25] https://www.w3.org/Bugs/Public/show_bug.cgi?id=24340

   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

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

     [26] 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

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

     [27] 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

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

     [28] 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 [29]scribe.perl version
    1.138 ([30]CVS log)
    $Date: 2014-01-20 23:57:24 $

     [29] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [30] http://dev.w3.org/cvsweb/2002/scribe/

Received on Wednesday, 22 January 2014 22:06:01 UTC