See also: IRC log
<trackbot> Date: 04 April 2011
<scribe> meeting: W3C HTML Canvas Accessibility Call
be right back
phone died atain
just a sec
getting a different phone
chuck: Think Ian might try to
make this a version 2.0
... if you look at the source code there is a lot of - save this for the next version
rich: we can't wait until a new version
chuck: I ran the font metrics by and although it is simple source code we need to wait for people to catch up.
rich: I think he is spread too thin
chuck: same as doug
rich: I understand
chuck: I have not seen any other
... no objections. just kicking it around
... Oliver did have an objection to a retained graphics API
... Oliver won't address me directly
... the 2 developers who did respond are not willing to have a communication with me.
rich: probably because of IP.
chuck: Oliver argued with me over text support in WhatWG
rich: was anything discussed on WhatWG?
chuck: no, not on the canvas api specifically for clickable regions
chuck: I started taking things to public web apps as is easier to work
rich: so, I need to poke Ian to
keep the discussion going.
... the "vizio like" example I provided showed how serious the problem is where the author had to create separate clickable drawing objects for each flow chart object
chuck: I thought up CSS pointers
to improve the practice.
... they are working find but more complex applications where this gets very expensive
rich: just an observation that when you have a complex widget that requires you to enter text you run into problems.
chuck: take for example a 7X7
grid of images and this is where canvas excels over
... you saw how Ian did not object to the caret API
rich: yes, as he established precedence for a caret himself
<Downchuck> css pointer-events
chuck: the css pointer event
attribute is such where we should enable this with canvas. This
came from SVG. CSS pointer events is such that the object is
over a specific area. ... this is without the stroke
... canvas has stroke text and stroke. it may be possible to track that. That could be useful in the long term
... it is actually practical to expose the current path.
<scribe> scribe: rich
chuck: it is possible to get the
path I just set.
... you get get this to a DOM string
<Downchuck> Looks like "M10 10 L10 20z"
chuck: this is good for any solution.
rich: are those coodinates relative to the object or screen?
chuck: svg object
Rich: Edward was upset that canDrawCustom
Chuck: this is more of an issue
for css than canvas
... frank responded
... we could force those issues on CSS
rich: the user will peaved if his settings are not honored.
chuck: we could address both of
those objections. They are something that should be solved in
... caret is not really addressed in CSS and neither is focus ring
... some have said that overspecification can be anti-competitive
rich: have any of these made any progress
chuck: I still need to get
something fixed on some of these bugs but nothing has happened
... I like using the SVG technique for grabbing the draw path into a DOMString and will continue to push that for development purpsoses.
rich: I want to wrap up canvas and start work on SVG accessibility
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: richardschwerdtfe Found Scribe: rich Default Present: Rich, +1.949.637.aaaa Present: Rich +1.949.637.aaaa WARNING: Fewer than 3 people found for Present list! Found Date: 04 Apr 2011 Guessing minutes URL: http://www.w3.org/2011/04/04-html-a11y-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]