- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 24 Feb 2010 02:17:15 +0000 (UTC)
- To: Steven Faulkner <faulkner.steve@gmail.com>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, public-canvas-api@w3.org
On Tue, 23 Feb 2010, Steven Faulkner wrote: > > if the content of the canvas sub tree is exposed to AT and focusable > elements are included in the tab order, by default, then regardless of > what browser an AT user has they will get get this content. Regardless > of what relationship any interactive content has to the canvas content, > keyboard only users will be able to tab into and interact with focusable > elements. > > So for example if I am a keyboard only user and encounter a canvas > element that includes a link or 2 links or many that are not associated > with the displayed canvas, because they are "fallback" then focus will > be lost to the users, end result= confusion This is the case regardless of whether an AT is involved or not. > or I am an AT user accessing the page *using* Firefox, I encounter the > message "your browser does not support canvas get Firefox" end > result=confusion. Indeed. Pages that do this are non-conforming. Authors are required to provide accessible alternatives. If author are going to ignore the spec on this, why would they not equally ignore the spec for "adom" and include it when it is not appropriate, causing the same problem? I don't understand why you think it's possible for authors to follow the spec on the one hand, while using the fact that authors _can't_ follow the spec on the other as evidence that the feature is needed. Either authors are going to care about what the spec says, or they're not. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 24 February 2010 02:17:43 UTC