There are several things I would like to see changed about the entry form. The first and second items were brought up by several of the testers I used for usability testing of my contest:
- The message at the bottom of the form that says you won't see the images until it's approved by an administrator. Why is this here? It isn't true, you see the photos right after they are saved. https://snipboard.io/mlLqXQ.jpg
- The 'Image title' field is auto-populated with the file name of the uploaded file, and it is the only field that can be used to display a title on the photo. The submitter has to change the file name to something appropriate for a title, so I have to explain this to them. I would like to have a field that will be used for the title that is blank instead. Then what goes in the field would not require instructions - the name on the label would explain it. It would help to be able to change the label name too.
- The 'Phone' custom question does not apply any data validation. You can put any number of characters, numbers, or symbols in it. Not sure why this field was created without data validation. It works exactly the same as a text field.
Hi Jane,
Thank you for the feedback!
- It means the photo becomes visible to everyone. We are going to change the wording.
- We think for the most users it is convenient to have this field being filled automatically. It would require quite some modifications to make this label configurable. We are thinking of allowing our users to provide their own translation sets, so that they can name things as they like.
- That's right. We might remove this field type or add validation.
Oh say, what do you mean by 'translation set'? For changing label names?
A lot of users want to rename things to their needs and it is hard to find a common ground so that the translations fit for every use case.
We want to develop a feature, where users can provide translations for most of the texts in PollUnit basically to override our translations with their own. But as I said this first needs to be developed.
It sounds like you are talking about language translations, but I don't know what that has to do with this topic.
If you can provide your own texts for English language for instance, you can customize the texts to your needs.
I just want to point out that using a field of type Phone makes sense because it is semantically correct, opens the appropriate keyboard on mobile devices, and improves accessibility as well as integration. However, phone numbers are difficult to validate since there are different formats worldwide, optional notations, and special cases.
Well, this is the only form I have encountered where the maker did not have at least some simple validation on a phone field. So apparently that nut has been cracked before by others.