or .. things are not always what they seem. Rich Schwerdtfeger CTO Accessibility Software Group "John Foliot" <jfoliot@stanford.edu> wrote on 06/28/2011 12:49:59 PM: > From: "John Foliot" <jfoliot@stanford.edu> > To: "'Silvia Pfeiffer'" <silviapfeiffer1@gmail.com>, Richard > Schwerdtfeger/Austin/IBM@IBMUS > Cc: <public-html-a11y@w3.org>, <public-html-a11y-request@w3.org> > Date: 06/28/2011 12:50 PM > Subject: OT (was RE: hit testing and retained graphics) > > Silvia Pfeiffer wrote: > > > > What about Adobe Flash in this area? Adobe Flash is used for many of > > the same use cases that canvas is used for. Is Flash more accessible? > > How do they do it? Is Flash prohibited because it's not accessible? > > http://www.adobe.com/accessibility/products/flash/ > > > > > > On a side not: I'm wondering if in the majority of cases we may be > > trying to achieve the impossible. For example, you may try as hard as > > you want, but you will not achieve it that a blind user will be able > > to drive a car with nothing but machine support. Even with the best > > technology that will communicate what is happening around them, it > > will be impossible to provide a description of the visible environment > > sufficiently timely to make it possible/safe to drive without seeing. > > What is our solution for the impossible situation? > > Never say never. Or as Ian Hickson is fond of reminding everyone, "Things > that are impossible just take longer"... > > JFReceived on Tuesday, 28 June 2011 17:51:50 UTC
This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:59:02 UTC