On Jul 29, 2011, at 16:04 , Richard Schwerdtfeger wrote: > 2. Now the we have these objects a screen reader or screen magnifier needs to know there location and bounds on the drawing surface. Unlike HTML, as a default, that information is not provided. > And you are assuming it always exists; I am not sure it does, particularly in the cases where people use canvas to do 'new' UIs. > - By mapping a path to a fallback element the browser can use the information to fill the bounds of the object to the accessibility API bounds. The browser has all the path transformation information to do the job > All true -- if the assumption holds. > With the basic plumbing in place now we can have the discussion on how you make something accessible and there are multiple strategies that apply. The solution depends on the problem and like in HTML content (this is not limited to canvas) the author may need to provide an alternative rendering based on the persons ability. So, spending our time defining different use cases is a bit of a red herring in that we can go through an exhaustive list of these and still come back to the basic plumbing problem we are trying to address here. > No, I disagree, I think. I think it quite possible you'll "miss", possibly by only a little. But a miss is as good as a mile, as they say. David Singer Multimedia and Software Standards, Apple Inc.
Received on Monday, 15 August 2011 16:41:53 UTC