# Submit Button Loading States: Designing the Moment After the Click

> When someone presses submit, the button should react immediately, show that work is happening, prevent a second press, and then clearly show success or failure. Keep the button's size stable while it changes, announce the state to screen readers, and move focus to errors if the request fails.

Updated November 2026. Source: https://www.exodeui.com/learn/submit-button-loading-state/

## Key takeaways

- React within 0.1 seconds of the press
- Show loading, block double submits, then success or error
- Keep the button size stable
- Announce states to assistive technology and focus errors

## Respond within a tenth of a second

Nielsen Norman Group's response-time limits still apply: about 0.1 seconds feels instant, about 1 second keeps the flow of thought, and after that people need feedback. The pressed state should show instantly, and the loading state should appear before people wonder whether the tap registered.

## The states

A submit button has more states than default and hover:

- Pressed: instant visual response
- Loading: label replaced or joined by a spinner or progress
- Disabled while loading, to prevent double submissions
- Success: a brief check mark or message, then the next screen
- Error: button returns to normal, with a clear message near the form

## Keep the layout stable

If the label is replaced by a small spinner, keep the button the same width so the layout does not jump. Morphing the button into a circle is popular but can confuse people if it looks like a different control; keep the change subtle.

## Accessibility

Set aria-busy or update a live region so screen reader users hear "Sending" and then the result. Prefer aria-disabled with an explanation over removing the button from focus order. If submission fails, move focus to the first error and keep what the user entered.

## Building this in ExodeUI

In ExodeUI, which we make, a submit button is a component with pressed, loading, success and error states. Your form sets the inputs as the request progresses, and the component reports when the success animation has finished so you can move on. Keep a real button element for focus and screen readers.

## Frequently asked questions

### Should a button show a spinner while loading?

Yes, or another clear progress indicator, as soon as the request takes more than a moment.

### How do I prevent double form submissions?

Disable or ignore the button while the request is in flight, and make the server tolerate duplicates.

### Should the button change width while loading?

No. Keep its size stable to avoid layout shifts.

### How do screen readers know the button is loading?

Use aria-busy or a live region that announces the loading and result states.

## Related

- [Button press animation](https://www.exodeui.com/learn/button-press-animation/)
- [Checkmark animation](https://www.exodeui.com/learn/checkmark-animation/)
- [Animated login screen](https://www.exodeui.com/learn/animated-login-screen/)
- [Rocket launch button](https://www.exodeui.com/components/rocket-launch-button/)
