Read-only Field
A read-only field can receive focus and its value can be copied. The person cannot edit the value.
readonly: focus + copy + submit, no edit; disabled: no normal focus or submit- 1Display name · editable
value="Maya" - 2Account ID · read-only
readonly - 3Invite code · disabled
disabled
<input readonly>readonly: focus + copy + submit, no edit; disabled: no normal focus or submitA11YAnother example
An account ID is read-only. A person can focus and copy it. The supported native field still submits its value.
Main parts
- 01Field label
- 02Current value
- 03Read-only attribute
- 04Focus behavior
- 05Copy behavior
- 06Form submission behavior
Use it when
Use it when a value must stay visible and available for copying. The current task must not allow editing.
Do not use it when
Do not use aria-readonly alone to block editing. Native readonly only applies to supported text controls.
Name used in code
readonly: focus + copy + submit, no edit; disabled: no normal focus or submit Before you ship
Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages.
Outcome: Use Read-only Field to solve this user need without losing the current context. User context: An account ID is read-only. A person can focus and copy it. The supported native field still submits its value. Recommended pattern: Read-only Field. Why it fits: Use it when a value must stay visible and available for copying. The current task must not allow editing. Do not use it when: Do not use aria-readonly alone to block editing. Native readonly only applies to supported text controls. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Read-only Field. Definition: A read-only field can receive focus and its value can be copied. The person cannot edit the value. Release checks: Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.