Height Field

Considerations when designing a field for a Person's Height.

Mobile

Options for sighted users with sufficient motor capabilities - tend to be friendly with either a text input or a large scroller with visible options rolling by.

Example

Desktop

When working with desktop UX the interactions can be a bit different.

We need to consider:

• ease of input - including for users of various disabilities (esp. sight and motor control)

• types of components users prefer to use (text, scroll, slider, +/-, etc.)

• motor skill limitations

• sight limitations (screen readers and zoom)

• data-types (i.e. cm, inches, feet and inches)

  • what value type users prefer to use

  • which do we want stored in the Database

• conversion info between the types (e.g. 67" = 5' 7" = 170cm)

  • when we want users to have that conversion info

    • during selection

    • after selection

• etc.

Text entry serves the blind and some motor control challenged users a method of only having to press a handful of keys.

+ / - buttons are tedious when many presses are required

Scroll is viable for mouse scrolling or mobile scrolling.

Sliders are limited in length and so not ideal for such precise numbering.

Combobox and Scroll allow for multiple input types

• text

• scroll or cursor

Listboxes can be nice because they have many values visible by default, however they only offer scroll, and don't allow text entry alternative. A better alternative if wanting the list visible always is to use a Combobox with the dropdown pinned open like the listbox.

• scroll

Here are some design considerations: