A disabled reason must be discoverable; read-only must say when editing returns

What it is

Once something cannot be changed, the next questions are “why” and “when.” Disabled without a discoverable reason is taken as breakage; read-only without saying when edit rights return (or that they never will) produces empty waiting or repeated requests. Reason and return-to-edit writes both sentences beside the state. The issue is explanation, not whether the looks collide, and not whether read-only can be copied.

Why it happens

Cannot-edit is a refusal. Without a reason, people fill in a breakage model: refresh, switch browser, tap again. The real reason for disabled is usually a precondition (agreement unchecked, no permission, outside a window). Putting that reason where it can be found swaps the breakage model for a task model (check that box, find an admin). The reason for read-only is a lifecycle: submitted and pending review, archived, locked by someone else. “Uneditable until review passes” or “permanently read-only after archive” gives waiting an end. Screen-reader users cannot hover; the reason must be focusable or standing text.

Where it stops holding

When the reason is security (“you are restricted by risk controls”) it cannot be too specific, but it still needs an actionable next sentence (who to contact). A brief system disable (saving) is progress, not a permission story. Permanent read-only’s honest answer to “when can I edit” is “you can’t,” which is better than a pretend date. When many fields share one reason, do not repeat a paragraph on every slot; say it once on the group and short-cite it in the slot.

Applying it

• Put a reason and a next action beside every disabled control; do not rely on hover alone.
• Beside read-only, write the condition for edit rights or “permanently read-only,” so waiting is not open-ended.
• Make the reason readable from the keyboard and a screen reader.
• Verify by pointing at disabled and at read-only and asking “why” and “how do I change this.” No answer, or an answer that requires a lucky hover, means explanation is not yet a queryable object. Come back a day later: if read-only still has no horizon, the copy should already have said permanent.

Related

• Within the group: E2.21.1 Read-only means not editable now, but still selectable and copyable · E2.21.2 Disabled means the capability is off and usually not interactive · E2.21.3 Similar looks hide whether unlock can even be asked for
• Adjacent: E6.03 Inline validation · E5.18 Permission visibility of navigation
• Search terms: reason and return-to-edit · disabled reason · read-only until