← Back to Catalog

Readonly vs disabled

readonly-vs-disabled

Disabled = field exists but is unavailable. If the value must still be shown and copied, use read-only, not disabled.

Description

Spectrum separates disabled from read-only: disabled means the field exists but is unavailable, while read-only keeps a value on screen so users can still read and copy it. Putting a must-copy value in a disabled field blocks selection and fails the split. Use disabled for unavailable inputs; switch to read-only whenever the content still matters after interaction is locked.

When to use

Deciding whether a shown value must stay copyable or the field is unavailable.

Not when

Truly unavailable fields with no value users need to read or copy.

Agent hint

Use read-only when the value must stay visible and copyable; disable only if unavailable.

Pass

Unavailable fields are disabled. Values that must remain visible and copyable are read-only.

Fail

A value that must be copied is in a disabled field.

Citations

Open UX · cited UX rules agents audit against

Privacy · Sources ·