WorldconVotingSystems / WorldconVotingSystems/nomnom

[advise] The notification when votes are recorded is possibly easy to miss

Open
#176 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
17
Forks
15
Avg merge
11m
Merged PRs (30d)
1

Description

Original issue

Recorded from file 770:

Minor quibble: I found the voting site’s method of indicating that one’s vote has been registered and recorded to be a bit awkward. Upon selecting either the yes or no button, a brief, easy-to-miss small pop-up window appears in the upper left corner of the screen, remaining visible for barely long enough to read before disappearing. If you’re not looking at the correct portion of the screen, you can miss it entirely. There is a note on the page stating that if the pop-up appears and the selected button remains highlighted then one’s vote has been registered, none of which is nearly as reassuring as the standard online voting method of a separate “submit” button which then leads to a confirmation page showing the vote that has been registered. Barring that sort of two-part vote registration system, at least moving the on-screen location of the pop-up confirmation window to nearer the actual vote button would give voters a fighting chance of actually seeing the confirmation message.

Commentary

I'm not sure I'm going to change to a separate submission flow in full barring handling disabled JS, but it's worth looking into moving the confirmation alerts closer to the submission, or persisting them longer, or duplicating the notification in the form itself. I think that last is the best way, tbh; the form should directly indicate success even though it's duplicative of the toast popup.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a file or test. Start by locating the voting form and its toast or alert confirmation behavior, then assess the proposed in-form success indication, longer persistence, or repositioning. Done means voters can clearly see confirmation after selecting either yes or no.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.