E-mail List Archives
From: John Foliot
Date: Mar 26, 2011 1:51PM
- Next message: paniz alipour: "Re: Html5 canvas accessibility"
- Previous message: Steve Faulkner: "Re: IE9"
- Next message in Thread: None
- Previous message in Thread: Steve Faulkner: "Re: IE9"
- View all messages in this Thread
And we must not forget implementation in other browsers. While IE today deserves mention for being "on it", there *are* other browsers that need to at least catch up to IE, not to mention also supporting the solutions currently being sought for the issues Steve described.
Sent from my Samsung Epic™ 4G
Steve Faulkner < <EMAIL REMOVED> > wrote:
>As was pointed out previously, a navigable canvas sub-DOM is only a partial solution.
>Provision of a focus ring on the canvas whose co-ordinates are programmatically exposed so that AT such as screen magnifiers can correctly convey current focus on areas of a canvas.
>Ditto for caret
>Also provision of a native method to pass events fired on areas of the canvas to elements in the sub-DOM.
>Sent from my iPhone
>On 26 Mar 2011, at 18:44, paniz alipour < <EMAIL REMOVED> > wrote:
>> Hi All,
>> As I read this link,It seems that the problem of canvas
>> accessibility(fallback content) has been solved:
>> The recently released Internet Explorer 9 beta implements the HTML5
>> specification’scanvas element fallback concept. This means that the content
>> inside a canvas elements start and end tags is exposed to assistive
>> technology users even when the browser supports canvas. It also means that
>> any interactive elements, inside a canvas elements start and end tags such
>> as links or form controls will be included in a documents default tab order
>> even when the browser supports canvas.
>> Also the problem of focusing on elements,
>> Now which problem exists and not solved?
>> Paniz Alipour