In GR4, we implemented a broad but shallow version of our website. Below are some of the details.
Platform and Software:
The website was run on Chrome, on both Windows and Mac operating systems. It should be run in as close to full screen mode as possible.
Starting the Prototype:
- Visit: http://truevote.herokuapp.com/
- You can log in with any username and password that you choose
- From there, you can enter votes one by one until the entire audit is complete
- While auditing, you can correct one mistake if needed
- After auditing 5 ballots, you can see the projected election results
Incomplete Dimensions:
- The usernames and passwords are not linked to a database, so all combinations of entries (including empty strings) are accepted. This also means that the log-in page isn't personalized but will always welcome the user named "Amy" and her 5 ballots to audit.
- Progress is not saved: once an audit is completed, the data is not saved. This means if a user logs in multiple times, s/he will have to start a new auditing process each time.
- Editing the previous ballot is not yet possible. Editing the current ballot is possible, however, so by testing this feature, users will get a feel for editing the previous ballot.
- Results are static and do not reflect any entered information.
- After entering the last race on a ballot, if the "Fix Mistake" button is clicked and the user tries to correct a race, the button panel is updated, but the ballot count number is ahead one.
- If the user presses cancel when they finish and are prompted to submit or not, the error functionality does not work correctly. The users should be able to test the error functionality without entering this obscure mode.