- From: Charles Pritchard <chuck@jumis.com>
- Date: Sun, 16 Oct 2011 23:29:40 -0700
- To: public-comments-wcag20@w3.org
All, I've been working with the Canvas tag and the Canvas 2d Context since early 2007. Link to the Canvas Element: http://www.w3.org/TR/html5/the-canvas-element.html Link to the Canvas 2d Context: http://www.w3.org/TR/2dcontext/ I'm developing a supplemental document for WCAG relating to Canvas authors and outlining the practical cases I've been able to achieve for WCAG 2.0 compliance. That said, there are a lot of asterisks needed whenever I use the word compliance and Canvas in the same sentence. Notice the three asterisks following this sentence. ***. Canvas is a low level graphics API which requires of authors a level of skill and programmatic structure that is often regarded as "too difficult" by many developers representing browser vendors. When they're not excreting caution about difficulty they discount web developers as error-prone and inconsiderate, and our attention as inefficient and/or uneconomical. [Citations available]. I've thoroughly followed the WCAG principles this past year. Though I have not met every conformance criteria for AAA in my adventures, I feel that I have addressed sections in a manner which respect their intent. Link to Understanding WCAG 2.0: http://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html I will follow up in a month with early drafts of a Canvas tag supplemental to WCAG 2.0. The draft is mean to broach the issue and will be followed up with actual techniques, inclusive of code samples and additional discussion. If you have any questions, comments or concerns, post them to the list or send them to me. I will, to the best of my ability, address your correspondence. -Charles
Received on Monday, 17 October 2011 06:30:17 UTC