...
Page Properties | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||
|
Background
...
p.s. We should also decide on whether are going to use placeholder text. Usability recommendation is not to use placeholders - see https://www.nngroup.com/articles/form-design-placeholders/. SemanticUI's placeholder deals with a few of these issues and doesn't break the accessibility but doesn't overcome the main issue of more text to read and process when placeholders are used (we can't use only placeholders and no labels). If we don't have placeholder text there will be less to translate if we localise the interface and its just less for users to read (I am a less is more person...).
Decision
Following input from Ali Khalili it was decided that we would use the standard form layout for now. If later in the project we have time, we can attempt to address the sizing or location of the UI label or inline fields then we can change the layout. In addition, the structure form layout will allow us to place errors after the field labels.
Inline forms can be used when space is limited. Semantic UI required field attribute should be used.