Fields in "Send Correction" should have input constraints

[itserindean]

Problem: All the fields in the "Send Correction" do not have input constraints. Input constraints help both organizations and users as it prevents organizations from reading an extremely long message and users from spending long time writing a long message.

Step to repro: goto foodoasis.la goto map view by entering an address or using current location Click on "details" for any listing Click "send correction"

Severity 2 - Minor usability problem: fixing this should be given low priority

Heuristics Violated: 5 Error prevention 9 Help users recognize, diagnose, and recover from errors

Recommendations: It would be helpful to add input constraints (eg., 200 words) under the field especially for "Corrections".

Action Items

• [ ] detail exact constraints desired
• [ ] make change as designed

Note: the issue in the heuristics spreadsheet (item no. 31) asks to link this to #1131

This is issue was created from a list of food seeker issues identified by a heuristic evaluation completed by @Gigi P & @ryu-jieun at the end of last year.

[itserindean]

I created this with severity 2, as described in the heuristics spreadsheet but I think the severity should be: 0 = I don’t agree that this is a usability problem at all

Do we have any evidence this is a real problem for organizations? As a user on other sites I"ve ben frustrated when trying to provided detailed information to hit an arbitrary character limit. This feels arbitrary to me.

[entrotech]

Can anyone describe what kind of constraint would be at all helpful? About all you can do with a single-field free-form text entry is put a minimum and/or maximum number of characters constraint, which strikes me as pretty arbitrary and not helpful.

[staceyrebekahscott]

@GigiUxR As per the comments above from @itserindean and @entrotech , can you advise on the reasoning for the constraints given the concerns they expressed?

Moving to Question/ In Review.

[staceyrebekahscott]

@GigiUxR Following up on John and Erin's comments- please advise if this is still a usability issue that should be addressed. If no response by this week's meeting, we will go with their assessment and close this issue.

[itserindean]

Noting for posterity that it was @ryu-jieun rather than @GigiUxR who identified this as an issue in the Heuristics exercises, but as Gigi is our only active researcher at the moment, it will have to be her who weighs in...

[staceyrebekahscott]

Going with assessment given by @itserindean and closing this issue.