Skip to content
Interface language: English
Design / Signal

Website microinteractions: motion that helps people

Design useful motion for menus, forms and carousels, with visible focus, reduced-motion options and feedback that reflects real system states.

Article language: English

A woman holding a fan beneath red fabric beside a stream of water.
In this article

A button responds, a panel shows its new state, and a form explains that a message is being sent. These small responses are microinteractions. They help people understand what they can do and what has already happened. Motion should be a good host: show the way, then get out of it. If a visitor has to wait for an animation to finish before reading your offer, the choreography has taken over customer service.

On a service website, design the states first and the transitions between them second. An open or closed panel, an active button, an error and a success message must make sense without animation, too. The guidance below distinguishes practical design recommendations from specific accessibility criteria and browser behavior.

Give every effect a job

For each planned movement, ask what information it gives the visitor. A subtle underline can identify a link. A change in a button's state can confirm that an operation has started. A transition in an expanding panel can help people keep their bearings. If the only reason for an effect is to fill silence on the screen, reconsider its cost.

Keep a short record: the element, the event, the starting state, the end state, what happens without motion and how to test it. You can keep these entries alongside the design decision log. See also the article on a project decision log (in Polish). That way, a developer does not have to guess whether a card should open details or merely change appearance on hover.

Not every change of state needs movement. A border color, a clear label and a static icon are often enough. Consistency contributes to a sense of quality, too: similar actions get similar responses, and important errors are not communicated more weakly than decorative photo animations.

Separate decoration from operation

A section's entrance effect can add interest, but a script failure should not leave the section hidden indefinitely. As a design principle, we recommend making content visible by default. Once the mechanism is working, it can add a brief entrance animation. This is a resilient way to build a page, not a separate formula for WCAG conformance.

Important links and buttons should work without waiting for an effect to finish. If a visitor clicks a service, watches a transition and only then starts navigating, the delay serves no purpose. Scrolling should not be taken over by a sequence of scenes that holds up the route to information, either.

Information architecture establishes the reader's path. For context, see the article on B2B website information architecture (in Polish). Animation can explain that path, but it should not change it without warning. Decorative elements should not take up places in the keyboard order simply because they respond to a pointer. First decide which elements actually perform an action.

Design hover, focus and activation separately

Hover is the state triggered when a pointer rests over an element. Focus identifies where keyboard interaction currently is. They are not the same. A phone may have no useful equivalent of hover, while a keyboard user needs a consistently visible indication of the current element. Do not hide important content behind hover alone.

WCAG success criterion 2.4.7 addresses visible focus. A focus outline should not disappear after a brief effect or be removed without a replacement. If the menu has a gold underline, check that someone using Tab can identify the current element as confidently as someone using a mouse.

Use the element that matches the function: a link for navigation, a button for an action. Making a clickable fragment look like a button is not enough. The full keyboard journey is covered in the article on business website accessibility (in Polish). Test the keyboard journey before refining motion, so animation does not conceal missing basic operation.

Define the full panel and menu cycle

An expandable answer has closed and open states, but it also needs a defined response to another quick click. The new action should lead to the state the visitor now wants, not queue up old animations. People should not have to wait while an interface plays back every accidental click.

A hidden panel must not leave active links in the keyboard path. Check the control's label and its expanded state, too. For a menu that covers the whole page, decide how it closes, where focus returns and how the content beneath can be reached. Not every small panel needs modal-dialog behavior; the right choice depends on what it actually does.

A height animation has to accommodate changes in content length and enlarged text. If an answer works only when it is exactly three lines long, it is not ready to be maintained by an editorial team. Try a long heading, several paragraphs and another interface language. Sometimes opening immediately is a better choice than an elaborate transition.

Keep people in control of carousels and continuous motion

An image carousel, also called a slider, needs clear controls when its slides change automatically. W3C explains carousel functionality, including slide controls and information about slides. Buttons should fit within the actual viewport and have names that describe what they do. Dots without meaningful labels are not enough.

Aeneia conceptual photography

WCAG success criterion 2.2.2 covers, among other things, moving, blinking or scrolling information that starts automatically, lasts more than five seconds and appears alongside other content. In that case, there must be a way to pause, stop or hide it, unless that moving, blinking or scrolling is part of an activity in which it is essential. It does not mean that every brief effect needs its own switch.

For a slider, we also recommend pausing when it has focus, when the pointer is over it and when the browser tab is hidden. After someone manually selects a slide, do not immediately take it away with an automatic advance. People need time to look at brand photography (in Polish) and read the text at their own pace.

Provide a reduced-motion version

MDN describes `prefers-reduced-motion` as a way to detect a preference for less non-essential motion. It is not an instruction to remove every visual change. A shift across the screen can become a calmer change of state while retaining all the information and functionality.

With reduced motion, turn off large scaling effects, moving backgrounds and automatically scrolling decorations. An important message should appear straight away, without a journey across the screen. If you use autoplay, plan to disable it in this version as a deliberate design choice. Visitors should still be able to choose slides manually. If the page also includes a spatial scene, design a complete path without 3D (in Polish), retaining the essential information and a way to continue when the scene is turned off.

Test both a preference enabled before the page opens and a change made while viewing it. You do not have to change the settings on every device in the team: developer tools can test the relevant version under controlled conditions. Record what you checked instead of declaring a page accessible because it contains one CSS rule.

Sending feedback must reflect the real state

A form button can change to “Sending”, but a success message should appear only after the relevant operation has been confirmed. An animated green checkmark after a timer expires does not prove that a message was delivered. Error and retry states belong in the same design, not on a list of afterthoughts once the site has launched. If an operation takes longer, plan for progress, interruption and a return to the task (in Polish), so the status still reflects what is happening to the work.

In a B2B contact form, distinguish sending the request, acceptance by the server and subsequent delivery to the place where it will be handled. Further guidance appears in the article on B2B website contact forms (in Polish). The message should match what the system has actually confirmed. When there is a problem, keep the information entered and show a possible next step instead of resetting the entire form.

Do not make motion the only carrier of a state. A spinning icon without text can remain unclear. Color alone should not indicate an error, either. A short, specific sentence still communicates when motion is reduced or a visitor cannot distinguish the shades.

Measure the cost before adding another layer

On a less powerful device, open the menu, scroll through a long text and expand several answers. If the response is delayed, compare the view with the effect disabled. Look for a specific cause: a heavy library, repeated layout calculations or too many animations running at once. Do not judge smoothness only on the computer used to build the project.

Page speed and Core Web Vitals (in Polish) covers measurements and the browser's performance trace. Record the cost of the interaction you chose and the change it needs, rather than replacing the whole motion layer based on a feeling alone.

A useful acceptance task is a service-content accordion (in Polish). Test opening and closing, keyboard operation, and behavior when text is enlarged. Only once those actions are clear should you judge the smoothness of the transition between them.

Test behavior under ordinary mistakes

Try rapid clicks, navigating to another page during an animation, using the browser's Back button and loading resources slowly. Check that an invisible layer does not remain over the screen and block it after navigation. Watch the menu and slider states after a language change, when text takes up a different amount of space.

Choose an effect's duration for its purpose. A short transition can help people see a relationship, but a longer one is not automatically more elegant. Instead of imposing one number of milliseconds on every element, show the developer an acceptable example and the conditions for interrupting it. Acceptance should cover behavior, not just a video of the ideal path.

  • Content remains available when the effect is absent.
  • Keyboard focus is visible and the path through the interface is predictable.
  • Hidden elements do not intercept actions.
  • The reduced-motion version retains all information.
  • Slider controls and pause work in the actual viewport.
  • Form success follows confirmation, not a timer.

Keep an example of the behavior without motion as part of the handover. The person developing the site should see that the calmer version is an equal way to use it, not a fallback to polish later. For a new component, first compare its states with the existing rules; only then add its own timing, transition curve and another dependency on scripts.

Include these scenarios in the website acceptance review. The topic is discussed in the article on website acceptance checks (in Polish). If you want to bring order to motion on an existing site, explore Aeneia Design.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear