liveBook · Manning

Consequential action

As explained in Architecting Accessibility

A consequential action is an operation that may have significant effects on a person's finances, legal status, data, or resources.

A consequential action can significantly affect a person’s finances, legal commitments, data, or resources. Passing technical validation does not prove that the action matches the user’s intent: a valid account number may still name the wrong recipient. section 6.3

Reduce the chance and cost of mistakes by giving users a meaningful choice before or after acting:

  • Let users review the relevant data or instructions before confirming, and clearly explain the consequences. section 6.3
  • Offer cancellation, or a way to reverse the action afterward; a confirmation dialog or checkbox can prompt users to pause. section 6.3

Deleting database rows

A database administrator who is tired and anxious may hesitate to delete rows when there is no deletion summary or easy recovery. A review of what will be deleted, a clear warning, and a way to cancel or undo can help them proceed with more confidence. section 6.3

How Architecting Accessibility covers it

How deep it goes
Distinguishes input validity from user intent, then recommends review, consequence explanations, confirmation, cancellation, or reversal.
Examples
Uses bank transfers, legal actions, resource deletion or transfer, exam submissions, and live-database row deletion.
What you can do after
Apply review, confirmation, cancellation, or undo safeguards to reduce errors and their consequences.
How it connects
Connects form validation with confirmation dialogs, review steps, cancellation, and undo mechanisms.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.