aeharding/easy-acs-web-demos

Automatically exported from code.google.com/p/ez-access-web-demos

easy-acs-web-demos's Issues

Add button for making a purchase

On the review and purchase screen, you have it so that it advances if you wait 
or press the spacebar.

For people with disabilities, having something happen automatically can be 
problematic, especially if it takes them a while to read the page. The 
countdown time does add some interesting issue which we may wish to address in 
the EZ Access extension after v1...

It would be best to remove the timed option and just include an extra button on 
the screen--something like: "Demo: Purchase ticket" so people know that it 
wouldn't be a regular part of a fare machine application.

Original issue reported on code.google.com by [email protected] on 19 Sep 2013 at 3:04

More contrast between button states

When touching a button, the visual difference between the button-up and 
button-down states is very minimal. My coworker said that it was particularly 
hard to see and didn't know that I had touched something when I demoed it to 
her.

In the Toolbook demo, the buttons undergo a much more drastic color change 
(almost a reverse) in the button-down state. Blue-when-up buttons turn yellow 
when down. The font changes from white to black as well. This exact color 
scheme does not have to be followed, but the buttons should look obviously 
different when somebody is touching one.

Original issue reported on code.google.com by [email protected] on 20 Aug 2013 at 4:57

Screen resolutions & aspect ratio

The original fare/ticketing demo was created for a 1024x768 resolution. 
The airline check-in kiosk was designed to fit a 1280x1024 screen. (This 
unfortunately does not fit on modern, but low res laptops--esp. those with 
touchscreens.)

Because the demos are supposed to represent kiosk applications (which run in 
the full screen), it would not be appropriate to use Bootstrap's 940px (or 
whatever it happens to be) standard width. We may wish to include a note 
somewhere on a splash screen or readme to tell people how to activate the 
browsers full-screen mode (F11).

I think that it would be best to design to a particular aspect ratio (probably 
4:3 as it is common on kiosks) and allow sidebars to show up on wider screens.

If the layout could expand and contract to fit different screen heights, that 
would be best. Otherwise, you will probably wish to set some target 
resolution/s (like those above).

Original issue reported on code.google.com by [email protected] on 25 Jun 2013 at 4:26

Make idle speech loop optional

The idle speech loop tends to drive people nuts if it is always running over 
speakers. On our demo, we include a checkbox to turn the idle speech on or off. 
I think it would be good to add a similar checkbox/option to our page.

Original issue reported on code.google.com by [email protected] on 18 Sep 2013 at 4:24

Alt-text for the graphic

On the review and purchase screen, there is a graphic of a credit card. The 
graphic isn't just decorative. It conveys a little bit of information.

Check the demo for what ours says (which has a little different graphic). It 
says something along the lines that the raised text on the credit card should 
be facing upwards and on the left, if I remember correctly. It might also say 
where the slot would be located.

This information should come after the text that is displayed/read, so this 
might be a good place to use data-ez-sayafter instead of actual alt-text on the 
image.

Original issue reported on code.google.com by [email protected] on 19 Sep 2013 at 3:12

Include speech loop content visibly on the first page

I have added help and a speech loop to the demo. We need to have the 
information available in the speech loop also displayed on the screen.

I have included the content in the index.php in a comment block.

Look at the Airline Demo to see a way of styling the content. I have also added 
an SVG icon that can be used.

Original issue reported on code.google.com by [email protected] on 18 Sep 2013 at 4:21