+1 to revert. This breaks accessibility. Authors use <span> and apply ARIA
to it, in the sub DOM, to produce custom accessible content. This change
breaks it. It is safe to say that ANYTHING drawn on canvas is custom.
Why is a change of this magnitude being made without a formal process being
adhered to?
I would add that the person who made this change should not be making
statement about what it takes to make something accessible.
Sorry for the slow response. I am supposed to be on vacation.
Rich
Rich Schwerdtfeger
CTO Accessibility Software Group
From: Steve Faulkner <faulkner.steve@gmail.com>
To: Maciej Stachowiak <mjs@apple.com>, Sam Ruby
<rubys@intertwingly.net>, Paul Cotton
<Paul.Cotton@microsoft.com>, HTMLWG WG <public-html@w3.org>
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, chuck@jumis.com
Date: 06/04/2011 11:28 AM
Subject: revert request for change made to the HTML5 spec 23/05/2011
dear chairs,
I request that the following change be reverted:
http://html5.org/tools/web-apps-tracker?from=6144&to=6145
It substantially changes the content model of the canvas element, it is
claimed that the change is to
"Further discourage misuse of <canvas> that cannot be made accessible or
usable."
The change does no such thing, it does not stop any author creating
inaccessible canvas content, it only discourages authors from attempting to
provide accessible alternatives within the canvas sub-dom to inaccessible
user interface elements they may create using canvas.
--
with regards
Steve Faulkner
Technical Director - TPG
www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar -
www.paciellogroup.com/resources/wat-ie-about.html
