I've stumbled upon the way Google Forms uses Likert scale for mobile devices. Is there any reason why horizontal axis isn't fixed when user is scrolling down the Likert scale? Looking from UX point of view I'd say that fixing the horizontal axis (making it visible at all time when user scrolls) would minimize the cognitive load and increase the usability. Is there any reasons why Google chose this way? Reference image is down below.

enter image description here

1 Answer 1


It's not a great design decision for usability, but I have to imagine this method is simpler, safer and easier than anything else. So likely a decision made so simplicity instead of usability.


  • If I had a Likert scale question above a Likert scale question in my survey, and could scroll to see both on-screen simultaneously, would both column header rows become sticky?
  • What happens when a form-creator user adds too much text to one of the column headers?
  • How would that sticky div compare in display and interaction between the other types of form fields and display types?

It's a form builder tool so the value of usability optimizing for each edge case diminishes quickly. If you're worried about cognitive load you should just breakup the questions into smaller pieces. It's not really a usability issue on Google Forms if I could just build my form with smaller Likert-style questions so the header is always visible. Even in the example you shared "Very Unlikely, Unlikely, Neutral, Likely, and Very Likely" are only suitable answers to 1/7 questions shown so smaller sections are already needed.

  • Regarding multiple Likert scales on screen I'd say yes - both rows would become sticky, would it be not UX friendly? I like your idea of creating multiple Likert scales for different questions so the headers would be visible at all time, although that way it would take way more vertical space...
    – fakermaker
    Apr 6 at 14:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.