
A Destructive Button Needs to Name the Thing That Will Be Deleted
Make destructive actions understandable by naming the item, scope and recovery consequence, then test the confirmation flow with keyboard and assistive technology.

Make destructive actions understandable by naming the item, scope and recovery consequence, then test the confirmation flow with keyboard and assistive technology.

Connect form error summaries to the fields that need correction, keep the wording consistent, and test keyboard focus instead of checking red styling alone.

A useful loading state explains what is happening, preserves the user’s place and offers a clear result or recovery path when a request finishes.

Mark required form fields clearly in visible labels and programmatic information, then keep optional questions genuinely optional.

Put password requirements beside the field before submission, and make validation messages explain the specific correction without erasing useful input.

Make links that open a new tab predictable with a clear advance cue, then test the behaviour with keyboard and assistive-technology users in mind.

Set the HTML page language to match the published text, check translated pages individually and distinguish language metadata from automatic translation.
A favicon must remain recognisable when it becomes tiny. Simplify the artwork, test light and dark browser chrome and verify the actual icon file is loading.

Design a breadcrumb trail that explains a page’s place in the site, with meaningful labels and usable parent links on desktop and mobile.