Open richardolsson opened 7 years ago
Too tall meaning that they have to scroll to complete the report?
If so, could auto scrolling when interacting at the bottom of the screen be a possible solution?
Exactly. There are two issues with this:
The reason one wants to overview the whole report at once is partly to review it as a whole before submitting. We added the "effect" paragraph to help them understand what their response will result in. I think this feature is still relevant when reviewing the report and not just as a feedback when responding. If a user miss or skips to read the effect, one should be able to go back when reviewing.
Downsizing the text could result in less readability. This could be partly compensated by increasing the contrast, but then we would loose the shading in comparison to the active field, helping user to find visual focus.
There is also little room in decreasing margins. Tighten it would limit readability and make the UI too heavy.
If one would like to help the user to notice that there is content above but outside the viewing area, one could perhaps add a gradient in the top when scrolled down.
I have implemented automatic scrolling. I still think we need to condense the interface though. It's unreasonable that so little information can't be viewed on common laptop screens without scrolling.
A user who's an experienced caller says that they find the report flow form too tall, because it does not fit on their screen. This is a valid point, but a compromise must be struck between readability, displaying all the information necessary (as per findings in #69, #70, #71, #72, #73, #74) and making the UI efficient for experienced callers.
What would be a good way forward?