W3C home > Mailing lists > Public > public-canvas-api@w3.org > January to March 2011

Re: Test Case: Option Role - Canvas Accessibility Working Group

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 01 Feb 2011 15:08:51 -0800
Message-ID: <4D489283.4040209@jumis.com>
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
CC: public-canvas-api@w3.org, Richard Schwerdtfeger <schwer@us.ibm.com>, franko@microsoft.com, david.bolter@gmail.com, public-html-a11y@w3.org, swarren@aisquared.com, tlalor@aisquared.com, dmazzoni@google.com
On 1/30/2011 5:08 AM, Benjamin Hawkes-Lewis wrote:
> On Fri, Jan 28, 2011 at 7:05 PM, Charles Pritchard<chuck@jumis.com>  wrote:
>> http://dl.dropbox.com/u/17337752/text-legibility-crop.png
>>
>> Attached is a screenshot from the text-legibility script; demonstrating
>> issues described in the Canvas Accessibility agenda that Richard has been
>> maintaining.
> Sorry, which issues does this demonstrate and how?
Had some difficulty with the screen cap, will try again later.

The first line shows HTML spans, the second shows the same rendered in 
Canvas,
and the third shows it in canvas without 'help' from a nicer API.

I'll put in some more work on the example, to show caret positioning.


I'm trying to show the 'usefulness' of addressing these defects in the 
current APIs:
css pixel scaling (thus the blurriness in the third example),
exposing the baseline (thus the strange vertical offsets of the third 
example),
setting a focus ring in various manners, and the usefulness of having caret
positioning as well.

This was my first draft. I'll highlight these points better, in the next 
draft I produce.

-Charles
Received on Tuesday, 1 February 2011 23:09:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 February 2011 23:09:26 GMT