Google, sounds like you should hire Eric to help you get this right :)
On Monday, April 7, 2014 8:15:21 PM UTC-5, Eric wrote: > > As a disabled person using speech recognition for the past 20 years, I > see absolutely nothing in your project addressing my needs and I'm > feeling left out. in fact, you are reinventing the same old > accessibility framework that was first published in roughly the early > 1990s. gluing accessibility to a GUI which at best is a horrible mismatch. > > Here's what I need as speech recognition user. > > 1) read the state of anything that can be displayed or changed via a > GUI. this is a getter function > 2) change the state of anything that can be changed by a GUI. This is a > putter function. > 3) do something. This is usually the action associated with a link or > button but can also drive mouse over or any other event causing an action. > 4) tell me when something changes. These event notifications allow you > to use hand/mouse at the same time as speech and it lets the speech > system stay in sync with what's being displayed. > > By these four simple interfaces, you eliminate the mismatch between a > GUI and a speech interface. No longer do you have to navigate through > menus and clicks and links to get to a data element which you can't even > speak because it has no name. Your grammar can short-circuit all that > and go change the data element in question. > > Remember, a GUI navigation is tall and narrow, speech navigation is wide > and shallow. Don't try to force one to be the other. > > If you look at the other accessibility requirements, you will see > similar mismatches and this API set or something very similar to it > would make it possible to address the needs of the new accessibility > interface and provide a simpler, more direct interface. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/b412a599-3e59-4024-b5cf-47dffd2b3ac7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
