W3C home > Mailing lists > Public > public-html@w3.org > February 2009

another example canvas use- cufon - another accessibility concern and spec contradiction

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Tue, 24 Feb 2009 15:06:30 +0000
Message-ID: <55687cf80902240706t756baba7h750604d61a4e876e@mail.gmail.com>
To: HTMLWG <public-html@w3.org>
embedded font thingy

good to see that they have included fallback content for the canvas
text, but seems that the bit in the spec:

"Authors should not use the canvas element in a document when a more
suitable element is available. For example, it is inappropriate to use
a canvas element to render a page heading: if the desired presentation
of the heading is graphically intense, it should be marked up using
appropriate elements (typically h1) and then styled using CSS and
supporting technologies such as XBL."

Is going to be ignored, so should be rewritten to take this use into account.

It also seems that this
" Text that has been rendered to a graphic for typographical effect
Sometimes, an image just consists of text, and the purpose of the
image is not to highlight the actual typographic effects used to
render the text, but just to convey the text itself.

In such cases, the alt attribute must be present but must consist of
the same text as written in the image itself."

becomes contradictory as it's a "should" for image of text in canvas,
but "must" if the exact same text is  jpeg,png etc  image.

[1] http://www.w3.org/TR/html5/the-canvas-element.html#the-canvas-element
[2] http://www.w3.org/TR/html5/embedded-content-0.html#text-that-has-been-rendered-to-a-graphic-for-typographical-effect
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
Received on Tuesday, 24 February 2009 15:18:30 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:43 UTC