search

minutekey / ez-access-web

Automatically exported from code.google.com/p/ez-access-web
0 stars 0 forks source link

Enhanced auditory icons #44

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I would like to know if these ideas would be particularly difficult to 
implement or if there would be some negative consequences.

Currently, we have a relatively small set of auditory icons in ezsound.js. It 
would be nice to include some additional sounds that may relate to the status 
of particular elements.

Examples:
Different sounds for checked vs. unchecked radio buttons & checkboxes.
Different sounds for different types of interactive elements.
Particular sounds when an element is "clicked" or otherwise activated (e.g., a 
button making a click sound for all users).
Sound effect on page turn.

Some questions:
Auditory icons must be very fast--does this mean that they should be 
application-wide instead of referenced by data-ez-* code in a page?
--does it mean that there should be predefined auditory icons types that are 
"pre-loaded" in some sense?
--how fast is it if particular files are loaded on the fly and then played?

I can think of several potential custom attributes: 
  data-ez-sound="file.ext"
  data-ez-sound="predefinedEarconType"
  data-ez-sound-onaction="file.ext" or "predefinedEarconType"
  data-ez-sound-onclick="file.ext" or "predefinedEarconType"
<body data-ez-sound-pageturn> to override the default page turn sound.
<body data-ez-sound-pageback> to override the default page back sound.

Original issue reported on code.google.com by jbjor...@gmail.com on 22 Jul 2013 at 4:39

GoogleCodeExporter commented 8 years ago 
What would be the benefit of having it user/server-side? Why not have what is 
there now -- auditory icons installed with EZ Access? If really wanted, we can 
specify an attribute to allow an auditory icon from a list of possibilities.

I don't see a place where anyone would really want to use features like this, 
where they have to specify custom icons.

Original comment by aeharding on 22 Jul 2013 at 10:30

GoogleCodeExporter commented 8 years ago 
I think accessing a list of.possibilities.prepossessed by the code is probably 
the best idea. If authors really need a different sound effect, they can add it 
in the code.

Original comment by jbjor...@gmail.com on 24 Jul 2013 at 8:28

GoogleCodeExporter commented 8 years ago 
Suggested changes:

Earcons for EZ Action/Enter:
 - action.wav (rename select.wav):
     when an interactive element is "clicked"
 - action-none.wave (rename noaction.wav): 
     when a non-interactive element is "clicked"
 - action-check.wav:
     when an element is checked
 - action-uncheck.wav:
     when an element is unchecked

Earcons for navigation:
 - nav-interactive.wav (rename button.wav): 
     when navigating to an interactive element
 - nav-move.wav (rename move.wav)
     when navigating to a non-interactive element
 - nav-checked.wav (rename checked.wav)
     when navigating to a checked checkbox, etc.
 - nav-unchecked.wav (rename unchecked.wav)
     when navigating to a checked checkbox, etc.

Other sounds
 - pagechange.wav
     Sound effect when a new page is requested and loading.
 - alert.wav (copy of noaction.wav for now)
     Sound effect for alerts (top/bottom of page, no help available)

Original comment by jbjor...@gmail.com on 28 Aug 2013 at 5:46

GoogleCodeExporter commented 8 years ago 
I addressed the main issues here. There are still very minor things that would 
be nice to improve. Because I this, I'm reverting this issue to low priority.

The audiocons are set for v1.0, but the next milestone it might be nice to 
address basics.

Let me know if there's anything pressing to change otherwise.

Original comment by aeharding on 28 Aug 2013 at 7:48