Speech input for Kiosk

[E.J. Zufelt]

On 2010-02-23, at 11:44 PM, Alison Benjamin wrote:

> Hi,
>
> I'm definitely interested in how detailing a VI interaction model  
> could assist with design work. Do you know of any examples?
>
* Short answer, no.

So, I think what we need to do is.

1. Look at how 1d, 2d and 3d interaction models are currently dealt  
with for the visually impaired VI.

2. Look at the limitations of the 3d model from:

a. Learning curve perspective

b. Limited number of input keys perspective.

3. Synthesize what we learn in 1 and 2 into what we believe to be the  
most usable interaction model for our navigation structure.

To clarify what I mean here by dimensions of navigation I will use  
Firefox Options page as an example.

I am using FF 3.6 (Windows)

Open Firefox and go to Tools > Options and select Advanced.

You will notice on this page that there are three primary regions of  
navigation.

1. the list of categories of configuration options (General, Tabs,  
Content, ... Advanced).

2. Tabs within the Advanced category (General, Network, Update,  
Encryption).

3. The options pane, where the configuration settings are presented.

We will ignore the Ok, Cancel, etc. buttons and assume that they are  
part of 3 above, although they really are a separate navigation region  
to themself.

As a user who can interact with the UI using a pointing device (mouse,  
finger on touchscreen, etc.) you can scan the UI and reasonably  
quickly make our choices from the three regions.  As a user that  
cannot use a pointing device you must interact with the UI in a serial  
fashion.

1. Make sure focus is in the list of categories

2. Navigate serially through the list of categories until you reach  
the desired category.

3. Move focus to the list of tabs.

4. Navigate serially through the list of tabs until you reach the  
desired tab.

5. Move focus to the configuration pane.

6. Navigate serially through the configuration options until you reach  
the desired configuration option.

(note: yes, I do miss being able to use a pointing device).

So, what we need to discuss is how to make this navigation as easy to  
use as possible with the buttons that we have available.  I imagine  
that in part the discussion will help us determine how many buttons we  
need to have available.

HTH,
Everett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100224/e74b1d9b/attachment.html>