Idle speech thoughts - Githubissues

I would like to have the idle loop working for version 1.0. I envision the idle 
speech having three components:

1. The string to be spoken.
2. loop {boolean} whether the speech continually loops or is just spoken once.
3. A delay (in ms) before the string is spoken (this delay happens between 
loops).

On an initial screen, it might, for example, loop the following text, "If you 
have difficulty using the touchscreen, press the blue, diamond-shaped EZ Help 
button" indefinitely with a 5000ms delay between readings. (Obviously this 
would only play over headphones, otherwise someone would beat the poor kiosk 
after 5 min.)

On later screens, it might say just once, "For more choices, press the EZ Down 
Arrow." This behavior is part of the airline demo because we found that some 
people just needed a little "nudge" to use the arrow keys sometimes.

The idle loop/speech would not be presented when EZ Access mode was on. For 
looping speech, it would be presented on that page whenever EZ Access is off. 
For non-looping speech, it would not be presented if the user landed on the 
page with EZ Access on (i.e., turning EZ Access off while on the page would not 
then read the non-looping idle speech.)

Because there may be more than one message over the course of an application, 
it seems like it would be better to have specialized <body> attributes rather 
than a JSON settings file.

Perhaps something like:
<body data-ez
 data-ez-idlespeech="The idle loop text."
 data-ez-idlespeech-delay="5000"
 data-ez-idlespeech-loop="true">

If there is no data-ez-idlespeech attribute, then there would be no idle 
speech/loop on that page. There could be default values for *-delay and *-loop.
Original issue reported on code.google.com by jbjor...@gmail.com on 5 Sep 2013 at 8:01
cloudbearings / ez-access-web

Idle speech thoughts #100
