Track vote input method (hotkey vs mouse) in user_info.json

[Copilot]

Median vote times range 2-15 seconds across users. This adds tracking to determine if hotkey usage explains the variance.

Implementation

JavaScript (hotkeys.js)

• Detects input method on vote selection (hotkey keys 1-4/a/s/d/f vs mouse click)
• Validates context to prevent tracking clicks outside voting area
• Sends input$last_input_method to Shiny server via setInputValue()

R Server

• main_server.R: Initializes vote_input_methods structure in user_info.json on login
• mod_voting.R: Increments counters (hotkey/mouse/unknown) on each new vote cast

Data Structure

{
  "user_id": "User1",
  "voting_institute": "InstituteA",
  "images_randomisation_seed": 12345,
  "vote_input_methods": {
    "hotkey_count": 45,
    "mouse_count": 15,
    "unknown_count": 0
  }
}

Notes:

• Only tracks initial votes, not vote changes
• Uses "unknown" when method indeterminate (with warning logged)
• unknown_count > 0 indicates tracking issues requiring investigation

Analysis: Correlate hotkey usage percentage with time_till_vote_casted_in_seconds from user_annotations.tsv to quantify speed impact.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Log for every vote if the user has clicked a radio button/checkbox or used the hotkeys</issue_title>
<issue_description>We realised that the current median time to vote ranges from 2 - 15sec
So we want to see how much of this difference is explained by the usage of hot keys

Store the hotkey/mouse usage inside the user_info.json of each user</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Log for every vote if the user has clicked a radio button/checkbox or used the hotkeys #73

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.