A text field that looks grey or unavailable does not reveal its exact browser state. Check the declared native HTML state before deciding whether the field is intended for review or is unavailable. The example below separates those possibilities without submitting a form or entering personal information.
What each state means
A native read-only text control keeps its value visible and cannot be changed by the user, but it can still receive keyboard focus. This allows someone navigating controls to reach and inspect it. A native disabled control cannot receive normal keyboard focus. It is also excluded from form submission. These distinctions are described in MDN’s reference on the readonly attribute.
Hypothetical reading-preferences example
Hypothetical example: Imagine a public reading-preferences page with three declared controls. The reference code is native read-only, the optional note is native disabled, and the comment box is editable. The expected result is:
| Field | Declared state | Expected editing | Expected focus |
|---|---|---|---|
| Reference code | Read-only | Not editable | Focusable |
| Optional note | Disabled | Not editable | Not focusable |
| Comment | Editable | Editable | Focusable |
Observation: pressing Tab could move to the reference code, skip the disabled note, and then reach the comment. Outcome: the first field is available for review but not correction; the second is unavailable; the third accepts input. The disabled note would not be included if this hypothetical page submitted its form.
Practical limit
Do not infer these states from colour, contrast, or a dimmed appearance alone. A custom widget may imitate a native field while using different focus and submission rules. For a support note, identify the field by its label and describe the observed focus behaviour. Do not include its private value. If the implementation is unknown, record that uncertainty instead of submitting personal data to test it. This example is not evidence about a real Daman account.