EZ Enter/Action function behavior

[GoogleCodeExporter]

The EZ Enter/Action function is tricky because there are a lot of different 
cases. Some elements are not interactive and thus repeat. Some elements take a 
"click" as input. Other elements require multiple "clicks" for operation--such 
as opening a dropdown menu with one click and choosing an option with the 
second click. Here are some of my thoughts...

= Programmatic behavior =
For v1, we only need to support full operation for: non-interactive elements, 
buttons, checkboxes, and radio buttons. These elements only take a single click.

We will want to support dropdowns and other elements pretty soon after v1, so 
we should anticipate those needs in designing the function.

= Audio behavior =
When EZ Action is pushed, a sound effect should be played. The system may also 
provide speech feedback depending on the element and any custom attributes.

Speech feedback for non-interactive elements: The system says "Repeating..." 
and repeats the content.

Speech feedback for buttons (all types, including ARIA): No speech feedback is 
provided by default.

Speech feedback for checkboxes & radio buttons (including ARIA): The system 
should say, "<name> is now <status>." I'm unsure if <name> needs to be repeated 
because people might remember what element they are interacting with. I will 
have a better sense after trying it, I think. <status> would be either 
"checked" or "unchecked." I think it would be wise to check the element's 
actual value (use getValueSubstring()?) when generating this string. In this 
way, you do not mislead the user if for some bizarre reason their click/EZ 
Action does not work (I could see this happening more with custom 
ARIA-marked-up controls).

Speech for single-click-to-activate elements should be overridden by a custom 
attribute. Maybe something like data-ez-sayonclick, data-ez-sayonaction, etc. 
This allows an author to provide better speech feedback for something like a 
switch where it could say: "The lights are now off" or "Video playback is 
paused."

Original issue reported on code.google.com by jbjor...@gmail.com on 27 Aug 2013 at 7:56

[GoogleCodeExporter]

A different sound effect should be used for checking vs. unchecking a 
checkbox/radio button.

Original comment by jbjor...@gmail.com on 27 Aug 2013 at 7:58

[GoogleCodeExporter]

Toggle buttons are a possibility with ARIA. See 
http://blog.paciellogroup.com/2008/04/aria-toggle-button-and-tri-state-checkbox-
examples/ for a discussion and examples.

Could be implemented after v1.
Default speech feedback could be:
"<name> is now pressed." or "<name> is now unpressed." similar to how radio and 
checkboxes work.

Original comment by jbjor...@gmail.com on 27 Aug 2013 at 8:00

• Changed state: New