Timeout to reset session variables

[GoogleCodeExporter]

As discussed... On a page without a system timeout (data-ez-timeout* 
attributes), a user could potentially activate the highlight and then leave the 
kiosk. This (1) may look bad and (2) prevents the idle loop speech from 
speaking when the next user plugs in headphones. In another case, a user could 
also turn up the volume on the splash screen, which would affect the next user 
if the volume was not reset.

We should implement a reset timeout (in addition to the others) that resets the 
page (highlight and volume and any other session variables).

The presence of the data-ez-reset attribute should:
 1. Reset all session variables on page load
 2. Reset all session variables after a default length of time (let's say 5 min. = 300000 ms)

In order to override the continuously resetting part (part 2), the author can 
add the data-ez-reset-delay attribute with a value in ms. A value <0 could 
signify that the author does not want the session to reset itself after any 
delay.

If the data-ez-reset-delay attribute is present and valid and the data-ez-reset 
attribute is not, the system should NOT reset the session variables on page 
load, but should reset the variables on a continuous loop.

Important thing to watch for...
This could potentially conflict with the idle speech loop. I would like the 
idle speech loop to finish speaking before the reset, so that the speech 
doesn't suddenly change volume or suddenly stop and restart when the session 
variables are reset. In this sense, the reset should be "polite."

Original issue reported on code.google.com by jbjor...@gmail.com on 8 Oct 2013 at 5:34

[GoogleCodeExporter]

The only other timer-related function that I can think of is delayed help, 
which has two flavors:
 1. Delayed spoken help--happens after a delay of a few seconds after the element's text is read. This is only for people who are using the audio.
 2. Delayed pop-up help--a pop up with a helpful message for all EZ Access user. The pop up is both read and displayed after a delay.

There are a few examples of these in the demo that I could show you.

Neither of these are for v1. Just keep them in mind when working on the 
timer-related functions.

Original comment by jbjor...@gmail.com on 8 Oct 2013 at 5:55

[GoogleCodeExporter]

Is this necessary? Won't it just reset after it forwards the user to the start 
page (which already has the data-ez-reset for when it loads?

Original comment by aeharding on 29 Oct 2013 at 5:28

[GoogleCodeExporter]

Yes, this is necessary for the splash/first page of a kiosk app. Somebody could 
turn up the volume on the first screen and walk away. Without a reset of some 
sort on the first page, then the next person who plugs in headphones may be 
blasted.

Also, a person could press the down arrow and walk away. The next person, 
whenever they would show up would see the highlight and would not hear the 
speech loop.

The occurrence of these problems in actual usage is probably low, so I would be 
fine if you want to push this after v1.

Original comment by jbjor...@gmail.com on 29 Oct 2013 at 5:58