Bumped by Community user
3 minor copy changes
source | link

Removing labels seems to offer a trade off between clarity and concision. For data entryeditable forms, labels are a must havenecessary, but when can we forgo them when displaying that data back to an end user?

For example, here's a simple form with labels:

mockup

download bmml source – Wireframes created with Balsamiq Mockups

If you had a read-only view with labels, you could just disable inputs like this:

mockup

download bmml source

IfBut if we present just the data and remove field labels altogether, weI don't think we lose much clarity, and most users familiar with american names and address could parse the fields back into their original buckets if need be:

mockup

download bmml source

Data with well defined structures that has a well defined mapping to a real world analog seems the least risky, but examples of unadorned read-only data exist all of good design.

Here are two examples of content that is immediately presented without the pretense of a label to suggest how the data must be understood. In both cases, it looks almost silly to try to explicitly name those fields in the path to clarity

Google Search Results

Ux Planet Article Title

Certainly the Content Management System being used to edit articles would provide separate input fields, but the rules feel different for presenting that content to end users. Are there any guidelines as to when we can safely remove field labels without introducing ambiguity?

Removing labels seems to offer a trade off between clarity and concision. For data entry, labels are a must have, but when can we forgo them when displaying data to an end user?

For example, here's a simple form with labels:

mockup

download bmml source – Wireframes created with Balsamiq Mockups

If you had a read-only view with labels, you could just disable inputs like this:

mockup

download bmml source

If we present just the data and remove field labels altogether, we don't lose much clarity:

mockup

download bmml source

Data with well defined structures that has a well defined mapping to a real world analog seems the least risky, but examples of unadorned read-only data exist all of good design.

Here are two examples of content that is immediately presented without the pretense of a label to suggest how the data must be understood. In both cases, it looks almost silly to try to explicitly name those fields in the path to clarity

Google Search Results

Ux Planet Article Title

Certainly the Content Management System being used to edit articles would provide separate input fields, but the rules feel different for presenting that content to end users. Are there any guidelines as to when we can safely remove field labels without introducing ambiguity?

Removing labels seems to offer a trade off between clarity and concision. For editable forms, labels are necessary, but when can we forgo them when displaying that data back to an end user?

For example, here's a simple form with labels:

mockup

download bmml source – Wireframes created with Balsamiq Mockups

If you had a read-only view with labels, you could just disable inputs like this:

mockup

download bmml source

But if we present just the data and remove field labels altogether, I don't think we lose much clarity, and most users familiar with american names and address could parse the fields back into their original buckets if need be:

mockup

download bmml source

Data with well defined structures that has a well defined mapping to a real world analog seems the least risky, but examples of unadorned read-only data exist all of good design.

Here are two examples of content that is immediately presented without the pretense of a label to suggest how the data must be understood. In both cases, it looks almost silly to try to explicitly name those fields in the path to clarity

Google Search Results

Ux Planet Article Title

Certainly the Content Management System being used to edit articles would provide separate input fields, but the rules feel different for presenting that content to end users. Are there any guidelines as to when we can safely remove field labels without introducing ambiguity?

2 updated title
| link

Do all read-only data fields need When to remove labels for data elements?

1
source | link

Do all read-only data fields need labels?

Removing labels seems to offer a trade off between clarity and concision. For data entry, labels are a must have, but when can we forgo them when displaying data to an end user?

For example, here's a simple form with labels:

mockup

download bmml source – Wireframes created with Balsamiq Mockups

If you had a read-only view with labels, you could just disable inputs like this:

mockup

download bmml source

If we present just the data and remove field labels altogether, we don't lose much clarity:

mockup

download bmml source

Data with well defined structures that has a well defined mapping to a real world analog seems the least risky, but examples of unadorned read-only data exist all of good design.

Here are two examples of content that is immediately presented without the pretense of a label to suggest how the data must be understood. In both cases, it looks almost silly to try to explicitly name those fields in the path to clarity

Google Search Results

Ux Planet Article Title

Certainly the Content Management System being used to edit articles would provide separate input fields, but the rules feel different for presenting that content to end users. Are there any guidelines as to when we can safely remove field labels without introducing ambiguity?