- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 25 Feb 2010 13:25:06 +1100
- To: Ian Hickson <ian@hixie.ch>
- Cc: public-canvas-api@w3.org, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
On Thu, Feb 25, 2010 at 1:13 PM, Ian Hickson <ian@hixie.ch> wrote: > On Thu, 25 Feb 2010, Silvia Pfeiffer wrote: >> >> However, where the accessibility information doesn't make sense to be >> also fallback - namely when drawFocusRing is used, which only makes >> sense when the <cavas> is actually displayed - there is no means to >> decide for a legacy browser if this should be displayed or not. > > This should never be an issue -- the script typically would create this > "accessible canvas" markup when it runs, only if it detects <canvas>, in > which case it would just remove the fallback markup. OK, you got me confused. I was thinking of a situation where there is markup inside the canvas that is coupled with the drawFocusRing function and thus linked with the display. Is that not practically possible? Silvia.
Received on Thursday, 25 February 2010 02:25:59 UTC