Paul Resnick (web page; email)
Associate Professor
University of Michigan School of Information
Click here to check for newest version of this document
Document last modified 11/10/2000
This page is intended to document some of the controversy surrounding the Palm Beach County, FL ballots for the 2000 U.S. Presidential Elections, from the perspective of the field of HCI, or human-computer interaction. Thus far, the data is entirely assembled from secondary sources (news media coverage). Much of the analysis and interpretation is my own. I encourage people to send me additional information or analysis that you think might be helpful to include here, or links to other related analyses.
Here's an AP Photograph of the presidential portion of the ballot in Palm Beach County, FL.
Voters are supposed to punch the hole in the middle of the ballot corresponding to one President/Vice-President ticket.
From an HCI perspective, the first thing to point out is that the voter must establish a correspondence between candidate tickets and holes in the middle. Contrast this with a potential selection method where voters would directly manipulate the names. The need to establish a correspondence in the mind of the voter creates the potential for voters to establish an incorrect correspondence. It seems to me that there are at least three ways for a voter to establish a correspondence between candidate tickets and holes in the middle.
In the box for each ticket, near the center, there is an arrow. For example, for the Libertarian ticket there is an arrow at the right that seems to point pretty clearly to a particular punch hole. This method would establish a correct correspondence, so that voter intended for any candidate would actually be counted for that candidate.
In the box for each ticket, right next to the arrow, there is a number. For example, for the Libertarian ticket the number is 7. It's not obvious where to start counting the holes, but if the top hole is counted as 1, this would cause a voter who intended to vote for the Libertarian candidate to actually vote for the Green party candidate, and voter who intended to vote Democrat to have their vote counted for the Green party candidate.
A voter might count the candidate tickets and infer the ordinal position of their ticket, then count off the holes down the center. One possibility would be for voters to count the position only in the left column, so that Republican would be 1, Democrat 2, Libertarian 3, and so on. This correspondence would cause a voter intending to vote Republican to do so correctly, but a voter intending to vote Democrat to have the vote actually be counted for Reform.
One of the interesting things about Method 3 is that while it seems fairly natural for the first few tickets in the left column, it seems unlikely that a voter would construct a cognitive map based on ordinal position that included all the candidate tickets. Consideration of the right-hand column would probably cause a voter to reevaluate the tentative correspondence he or she had established for the left-hand side.
How could you tell if voters were in fact confused and cast ballots that did not reflect their intentions? There are several possible indicators:
I discuss each of these indicators below, together with the evidence I've been able to assemble so far on whether they happened or not.
The two-column ballot was unusual. In prior Florida elections, there have not been so many candidates, and hence two columns were not necessary. In other Florida counties, they either used smaller type and one column, or two separate pages. The two-column ballot was designed by the Palm Beach Supervisor of Elections, Theresa LePore, and was approved by the other two people on the canvassing board. The motivation was to provide larger typeface than would have been possible with a one-column, single page ballot.
No mention has been made of whether there was any user testing of the ballots prior to the election.
"I'll never use facing pages like that (again)," LePore said Wednesday morning, when the impact became clear. "I was trying to make the ballot more readable for our elderly voters in Palm Beach County. I was trying to do a good thing." (Sun-Sentinel report)
It would be nice, of course, to be able to go back to each of the voters who voted for Buchanan or who punched two holes and ask them who they really intended to vote for. Ballots are secret, however, and there is no way to tell at this point which ballot belonged to which voter.
How to resolve the current Presidential election is beyond the scope of this analysis.
One obvious suggestion for future improvements is user testing of all new ballot designs. Subjects could go through a mock voting process, then be debriefed orally about who they intended to vote for. Any pattern of mismatches would then be detected. Note, however, that somewhat large subject samples might be necessary to detect problems. It appears that only about 1 in 20 of the Palm Beach voters were disqualified or cast their ballots unintentionally, though others may have been initially confused but figured it out. This suggests that bringing in half a dozen voters as subjects to test a ballot may not be sufficient to detect the nature and severity of problems.
A number of other HCI evaluation techniques could also be used that involve expert evaluators instead of or in addition to a sample of voters. These techniques include scenario walk-throughs and development of cognitive models of the voter's voting process. For example, the three alternative methods described in the first section of how a user might establish a correspondence between tickets and holes to punch reflect (very) informal cognitive models.
Perhaps the most important principle that could be applied is that of direct manipulation. It really would make more sense for voters to directly punch or mark the candidate's name rather than a hole some distance away that corresponds to that name. The hole punches are an artifact of our vote counting machines. New techniques with scanners and OCR (or touch-screens) should enable a more direct-manipulation interface for voting.
Finally, there should be no need for disqualified ballots. Each voter should get immediate feedback from the voting machine if they have voted improperly, and should be given a chance to correct their ballot, or fill out a new one. In computer interfaces, there has been a general trend towards more and more immediate feedback to users about errors in data entry (even web forms now have embedded JavaScript code to validate data entry). In many cases, computer interfaces have gone one step further to simply not allow invalid data entry in the first place, by having all data entry through menus and buttons. For example, in a computer interface, after one candidate was selected, the other candidates would be "grayed out" so that it would not be possible to vote again.
In any case, it seems pretty clear that HCI professionals should be involved in these decisions in the future, rather than leaving it to the intuitions, however well-intentioned, of election officials. Perhaps universities that provide HCI training to students could band together to offer a free evaluation service to election ballot designers in the future.