Internet Explorer is not supported by Design Library

The last version of Internet Explorer, version 11, was released on October 17, 2013. This is a very long time ago when taking into account the rapid development of web technologies. These days it is often difficult and time consuming to get modern technologies to work well in this old browser. More and more frameworks are dropping support, and even Microsoft themselves has announced that they will fully drop support for IE in their own services in 2021.

Consequently, we have decided to not include support for IE in the Design Library website.

Luckily, there are modern options in active development. Please use Firefox, Edge or Chrome instead.

Take over wizard

The most complex and complete type of wizard we have, used mainly for complex tasks in logged in channels.


Short description

Wizards are a powerful design pattern that can be used to simplify complex processes. By showing less information at a time, they allow users to focus better on the content. The steps can vary depending on the user's input.

When and how to use it

Use a wizard when a user has to complete steps in a specific sequence, or when a complicated task needs to become simplified. Be specific on what information a user is required to supply at each step. Use the supporting content area to give hints on what is required or provide a short FAQ relevant to that step. Try to group related questions (i.e. personal information) in one step.


Each step in the wizard may have a state. The states are:

  • Normal, used for the subsequent steps in the wizard
  • Active, this is the current step the user is filling out
  • Disabled, a subsequent step that user may not access without completing steps before. These are used if you may not jump to steps further ahead.
  • Completed, these steps have already been visited and are filled to satisfaction
  • Error, visited steps that contain form errors, such as missing information.

For advanced cases a step may hold sub-steps. These are numbered as sub-chapters: i.e “2.1 Adress details”. Steps may occur based on user input. For example, if a user states she also own a company, a completely separate step may be needed to supply all information about this.


The take over wizard relies on the behaviour of a takeover modal, where it acts as an added layer on top and uses the whole width and height of the viewport.

Step buttons

The Previous and Next buttons should be placed in their direction (previous - back, next - forward). The buttons contain an arrow icon placed centred aligned with the text in the direction.

  • Since we want to lead the user to the next step, the Next button is the Primary button.
  • The Previous button is a Secondary button.
  • In some cases we also need a Cancel button which is a Button link.

Step buttons


Desktop step buttons can be sticky to the bottom of the browser (optional). The buttons are placed within the width of the main content area.


Mobile step buttons are not sticky and placed at the bottom of the main content area.


A grid is applied on the main and secondary content areas, whilst the step navigation is fixed at 320 px. The content is always left-aligned. Subtle animations are used to enhance actions in the step navigation.

The width of the main content area varies depending on screen size but it is not wider than 768 px. In some cases, for example when a wide table is needed, you have the possibility of using the whole content area. 

Grid for desktop

Grid for desktop

Grid for tablet

Grid for tablet

Grid for mobile

Grid for mobile

Do's and don'ts

  • Allow users to exit the wizard midway and save status when needed
  • Allow them to resume the process at a later time
  • Group related questions into one step
  • Don't show steps, information or questions that are irrelevant to the user, due to what we already know



Tutorial and demo:



Wizard - desktop

Wizard - desktop

Step navigation - mobile

Step navigation - mobile




Page last updated


Was this helpful?