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

[Bug 7011] [in off-bug discussion] canvas accessible fallback provision is under specified

From: <bugzilla@wiggum.w3.org>
Date: Sun, 28 Jun 2009 12:29:08 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MKtVM-0004NF-JS@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7011





--- Comment #20 from steve faulkner <faulkner.steve@gmail.com>  2009-06-28 12:29:08 ---
(In reply to comment #4)
> > It is suggested that to make it practical for developers to provide fallback
> > for disabled users who cannot access the image content directly a native method
> > that allows the addition of text alternatives and an output method that inserts
> > img elements as fallback content, is added to the canvas API.
> 
> It seems that a native method to add text alternative is equivalent to a method
> to add text, which already exists:
> 
>     canvas.appendChild(document.createTextNode(alt));
> 
> I don't think that there would be any benefit to appending images per se; the
> <img> elements would never be seen and the text alternative would be no better
> than an actual text node.
> 

again, what i meant was a method as part of the canvas api, to add text
alternatives that could be outputted as fallback. If a method is provided, it
is more likely it will be used to help make the content accessible, which is
the result we all want.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 28 June 2009 12:29:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 28 June 2009 12:29:20 GMT