W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Canvas and ARIA alternatives

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Tue, 31 Jul 2012 13:11:51 -0400
Message-ID: <dfa97a166e116ad0f6651d157090c779@mail.gmail.com>
To: WAI Interest Group <w3c-wai-ig@w3.org>
The proper way to provide an equivalent to canvas content is to use
fallback content that is a descendant of the canvas element.  Lately I have
seen authors applying ARIA markup including roles, aria-labels, title
attributes, and alt attributes directly to canvas elements.  In particular
these are canvas elements that represent a single user interface element
such as a button.  Looking at the two HTML5 specifications  alt is not
called out for the canvas element and while title is a global attribute it
should only be used for supplemental information (except on input and
iframe elements).



I have not found much on the use of ARIA on canvas elements  except for a
mention in the WHATWG regarding hit regions.  Although the WHATWG
specification also indicates that input element such as checkboxes and
radio buttons cannot be descendants of canvas elements.



What are peoples thoughts on the canvas element and ARIA.



Jonathan



-- 
Jonathan Avila

Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com

703.637.8957 (o)
Follow us: Facebook <http://www.facebook.com/#!/ssbbartgroup> |
Twitter<http://twitter.com/#!/SSBBARTGroup>
 | LinkedIn <http://www.linkedin.com/company/355266?trk=tyah> |
Blog<http://www.ssbbartgroup.com/blog>
 | Newsletter <http://eepurl.com/O5DP>
Received on Tuesday, 31 July 2012 17:12:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:30 UTC