-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UI improvement] Better "required" highlighting in pre-post reservation questions #256
Comments
I am think 1 and 2 and also make the asterisk bold. |
PS: Not sure why, but it seems PR and issues are not automatically linked anymore on the right column "Development". |
* Improved required question star contrast. * Improved required question highlighting. Fixes #256 * Moving invalid form input style to new `dynamic_form` class. * Fixing required question line height. * Port required form improvements to admin preview. * Update NEMO/static/admin/dynamic_form_preview/dynamic_form_preview.css --------- Co-authored-by: Mathieu Rampant <[email protected]>
Hi,
I would like to propose a small UI improvement on forms (e.g. pre-post usage).
We had been experiencing users not understanding from the UI that some questions are mandatory and reaching out to report an issue (kiosk not working).
It tends to happen to users on their first usage which includes mandatory question or users who had not been using the facility in a while after receiving the initial Induction.
While I agree this is something we can improve in our Induction Sessions, I think making it more explicit in the UI might also help and give a better UX.
Considering the following example:
I would suggest one (or a combination) of the following options:
Increasing border size from 1px to at least 2px
Adding light red background
Changing the "*" to something more visible and explicit:
Please let me know which option would make more sense and to which view scope it shall be applied (I would say kiosk at least); I can work on a PR.
Thanks,
r-xyz
The text was updated successfully, but these errors were encountered: