W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2010

Minutes: HTML 5 Canvas Accessibility Meeting March 1, 2010

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Mon, 1 Mar 2010 15:15:08 -0600
To: David Bolter <david.bolter@gmail.com>, cooper@w3.org, janina@rednote.net, Charles McCathieNevile <chaals@opera.com>, cyns@exchange.microsoft.com, Steven Faulkner <faulkner.steve@gmail.com>, Frank Olivier <franko@microsoft.com>, jcraig@apple.com, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, cyns@exchange.microsoft.com, public-html-a11y@w3.org
Cc: surkov.alexander@gmail.com
Message-ID: <OFA0875B0C.F8E1E32D-ON862576D9.00742A2D-862576D9.0074BE37@us.ibm.com>


http://www.w3.org/2010/03/01-html-a11y-minutes.html

IRC log: http://www.w3.org/2010/03/01-html-a11y-irc

Text minutes of meeting:

IRC log of html-a11y on 2010-03-01

Timestamps are in UTC.

19:56:44 [RRSAgent]
    RRSAgent has joined #html-a11y
19:56:44 [RRSAgent]
    logging to http://www.w3.org/2010/03/01-html-a11y-irc
19:56:46 [trackbot]:
    RRSAgent, make logs world
19:56:46 [Zakim]
    Zakim has joined #html-a11y
19:56:48 [trackbot]
    Zakim, this will be 2119
19:56:48 [Zakim]
    I do not see a conference matching that name scheduled within the next
hour, trackbot
19:56:49 [trackbot]
    Meeting: HTML Accessibility Task Force Teleconference
19:56:49 [trackbot]
    Date: 01 March 2010
19:57:26 [Stevef]
    Stevef has joined #html-a11y
19:58:43 [richardschwerdtfe]
    Zakim, this will bee 92473
19:58:43 [Zakim]
    I don't understand 'this will bee 92473', richardschwerdtfe
19:58:57 [richardschwerdtfe]
    Zakim, this is 2119
19:58:57 [Zakim]
    sorry, richardschwerdtfe, I do not see a conference named '2119' in
progress or scheduled at this time
19:59:12 [richardschwerdtfe],
    zakim, this is 92473
19:59:12 [Zakim]
    ok, richardschwerdtfe; that matches WAI_PFWG(CANVAS)3:00PM
19:59:43 [Zakim]
    +??P2
20:00:13 [Stevef]
    zakim, ??P2 is me
20:00:13 [Zakim]
    +Stevef; got it
20:00:13 [richardschwerdtfe]
    zakim, ??P2 is Stevef
20:00:15 [Zakim]
    I already had ??P2 as Stevef, richardschwerdtfe
20:00:24 [Zakim]
    +[Mozilla]
20:00:55 [davidb]
    Zakim, Mozilla has David_Bolter
20:00:55 [Zakim]
    +David_Bolter; got it
20:01:07 [davidb];
    davidb has changed the topic to: canvas (davidb)
20:01:31 [Zakim]
    +[Microsoft]
20:01:55 [richardschwerdtfe]

http://lists.w3.org/Archives/Public/public-canvas-api/2010JanMar/0256.html
20:01:58 [Zakim].
    +[Microsoft.a]
20:02:00 [cyns].
    cyns has joined #html-a11y
20:02:57 [Zakim]
    -[Microsoft.a]
20:03:11 [richardschwerdtfe]

http://lists.w3.org/Archives/Public/public-canvas-api/2010JanMar/att-0255/canvaselement-issue74-feedback1.html
20:03:37 [Zakim].
    +[Microsoft.a]
20:04:31 [Stevef]]
    q+
20:05:08 [richardschwerdtfe]
    scribe: Rich
20:05:19 [richardschwerdtfe]
    Topic: navsubtree proposal
20:05:29 [richardschwerdtfe]

http://lists.w3.org/Archives/Public/public-canvas-api/2010JanMar/att-0255/canvaselement-issue74-feedback1.html
20:06:37 [frankolivier]
    frankolivier has joined #html-a11y
20:06:50 [richardschwerdtfe]
    Rich: this make it much confusing as a "accessibility compliance"
statement
20:08:48 [richardschwerdtfe]
    s/much confusing/much less confusing/
20:08:58 [Stevef]
    the use of an attribute to control access to the canvas subtree was
that the canvas subtree content was not avilable by default
20:11:09 [Stevef]
    this would mean that the many uses it would be put to that were not
accessible would be hidden from users
20:11:46 [Stevef]
    what is the use of the subtree switch if it does not have the positive
benefit of hiding crap from users
20:12:10 [Zakim]
    -[Microsoft.a]
20:12:48 [Zakim]
    +[Microsoft.a]
20:14:47 [davidb]]
    (discussion of usemap)
20:18:13 [richardschwerdtfe]
    Stevef: if you want to use an areamap then you do not need to map the
subtree to AT users.
20:18:44 [davidb]
    do we want a 4th attr for canvas, 'usemap'?
20:20:58 [richardschwerdtfe]
    Rich: I think we can support both this and image map
20:24:36 [richardschwerdtfe]
    Cynthia: will there be questions of confusion?
20:29:41 [MichaelC]
    MichaelC has joined #html-a11y
20:32:02 [richardschwerdtfe]
    Frank: I think that over time canvas will become adopted so we would
not need the attribute
20:34:21 [richardschwerdtfe]
    Steve: I feel more comfortable with this because over time it will
become the norm to support Canvas
20:34:21 [frankolivier]
    Frank: Today's usage of canvas is probably not indicative of the future
(Today, a lot on content inside <canvas> is just 'upgrade your browser'; in
the future, when all browsers support canvas, one can assume that
high-traffic/mainstream/etc sites will display the same content in the
actual canvas rendering, and the fallback (for older browsers and AT
tools))
20:34:49 [davidb]

http://lists.w3.org/Archives/Public/public-canvas-api/2010JanMar/0256.html
20:34:53 [davidb]
    has zzz tags around it
20:35:13 [richardschwerdtfe]

http://lists.w3.org/Archives/Public/public-canvas-api/2010JanMar/att-0255/canvaselement-issue74-feedback1.html
20:45:09 [richardschwerdtfe]
    When navsubtree is "true" the canvas the must be synchronized with the
canvas rendering. A value for navsubtree of false indicates that the canvas
subtree MUST NOT be included in focus navigation. Authors MUST set
navsubtree to false when the content within canvas is not intended to
represt the focus navigation for the visible elements drawn on canvas. To
support accessibility in the navigable sub-tree the author MUST:
20:45:25 [davidb]
    "the canvas the" (nit)
20:45:52 [cyns]
    represt s/b represent)
20:51:14 [richardschwerdtfe]
    Resolution: submit rich's navsubtree proposal with revised wording
regarding a value of false for navsubtree
20:51:50 [Stevef]
    RESOLUTION: submit rich's navsubtree proposal with revised wording
regarding a value of false for navsubtree
21:00:45 [richardschwerdtfe]
    Rich: Unlike HTML there is a true separation of content and
presentation when HTML DOM element is rendered as a canvas object
21:01:10 [Zakim]
    -[Mozilla]
21:01:56 [richardschwerdtfe]
    Rich: For browsers that support platform accessibility API the
drawFocusRect MUST change the location and bounding rectangle for the
element with focus in order for a magnifier to track the focus position for
the HTML element rendered using canvas drawing APIs
21:04:42 [Stevef]
    can i just point out that area element cannot be overidden by aria
roles in HTML5
21:05:36 [Zakim]
    -[Microsoft]
21:05:59 [richardschwerdtfe]
    http://www.w3.org/html/wg/wiki/ChangeProposals/Map4NotAdom
21:06:19 [Zakim]
    -Rich
21:06:22 [richardschwerdtfe]
    zakim, bye
21:06:22 [Zakim]
    leaving. As of this point the attendees were Rich, Stevef,
David_Bolter, [Microsoft]
21:06:22 [Zakim]
    Zakim has left #html-a11y
21:06:31 [richardschwerdtfe]
    RRSAgent, make log member
21:06:39 [richardschwerdtfe]
    RRSAgent, draft minutes]
21:06:39 [RRSAgent]
    I have made the request to generate
http://www.w3.org/2010/03/01-html-a11y-minutes.html richardschwerdtfe

Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Received on Monday, 1 March 2010 21:15:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:03 GMT