These are good suggestions. We need some filling in a couple of blanks though.
If it is a “DEMONSTRATION” button, what ballot does the voter get? Does it matter that they get their actual ballot, or can we just pick the first ballot? If the requirement is for their ballot, what is the interface? Do we list all ballots on another screen? Is that really practical?
Similar question for the “DEMO” card. Does the demo card just pick a random ballot, or does the poll worker program the ballot onto the card? We could of course put a flag on the card to put it in “demo” mode, but that will mean a new checkbox on the card creation screen and a new magic key on the Card Manager (aka Spyrus). That is not necessarily a big deal programmatically, but can users handle these flags? I have visions of 1% of real voters being given demo cards by accident, and then ignoring the red blinking light on the cast vote screen telling them they aren’t really voting.
How about a DEMONSTRATION button right on the front page of the first
display? That would allow all machines to be used and allow pollworkers to
assist voters in a demonstration environment. If that seems too accessible,
then perhaps a "demo" voter card? for the precinct.
Anyway, some way to give a demo to the voter is a great idea and needed.
----- Original Message -----
From: "Lesley Thompson" <email@example.com>
Sent: Friday, May 10, 2002 2:15 PM
Subject: AVTS-R6 Demonstration Module
> Johnson County has requested a separate Demonstration Module outside the
> Testing Module. In the April election, demonstration units were deployed
> every vote center and we had an enormous amount of trouble keeping them in
> the proper mode to act as a demo unit. Is there a way to have a
> "demonstration loop" that does not allow a user to "go back too far" and
> up outside the demonstration area? Something really simple and