Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Note: This page presents options for how button navigation will work on the DIA kiosk.

Background

On the Web, it is an accessibility best practice to make all the functionality of a Web page operable from the keyboard. Similarly with the Engage kiosk, we want to ensure that the kiosk is operable by a set of buttons. Button navigation could helps people who can't use the touch screen component of the kiosk (e.g. because they have a limited range of physical motion) operate the kiosk. Down the road, we need to make a design decision about what kind of screen reader option is required for the kiosk (e.g. do we use a commercial screen reader or canned MP3's? another option?) A current design assumption is that buttons will be a component that the kiosk's audio user will require and that they will use the buttons in concert with the screen reader feature to operate the kiosk.

Options for button placement, look, and feel on the kiosk

Buttons need to be placed on a location of the kiosk to provide a usable experience for a wheelchair user or someone with a limited range of motion. An option for this is to

  • No labels