2 minute read

WCAG 2.2.5: Re-authenticating (Level AAA)

You’ve logged into the site to apply for a job, but when you hit the button to submit, it’s logged you out and you have to start over!

It’s frustrating for anyone, but for users who need more time to complete tasks, having to log back in can feel like hitting a wall.

Re-authenticating makes sure that if users get logged out, they can easily pick up where they left off—without losing any of their progress.

Who this impacts

  • People with cognitive impairments: Those who take longer to complete tasks or fill out forms need the ability to log back in without starting over.
  • People with motor impairments: Re-entering credentials can be a burden for users who find typing or navigating difficult, so preserving progress is key.
  • Everyone: Any user, whether interrupted or dealing with technical issues, benefits from being able to resume where they left off after re-authenticating.

How to meet Re-authenticating

  • Preserve progress after re-authentication: Ensure that users don’t lose their work or progress after re-authenticating—whether it’s filling out a form or making a purchase.
  • Simplify re-authentication: Provide users with an easy way to log back in when needed, without losing their place or having to restart their task.
  • Test with timed logouts: Test your website or app by logging out after a period of inactivity and ensure users can resume their tasks seamlessly after re-authenticating.

Practical example

A healthcare portal logs users out after 15 minutes of inactivity for security reasons. However, when users re-authenticate, they are taken back to where they left off in their appointment scheduling process, ensuring no progress is lost.

Exceptions

In rare cases, where re-authentication without resetting progress would introduce a security risk or compromise the integrity of the process, an exception may apply, but only when fully justified.

Top tips

  • Focus on preserving progress: Make sure users don’t lose any work or progress when they log back in, especially for time-sensitive tasks.
  • Streamline re-authentication: Provide a clear, simple process for re-authenticating to avoid user frustration.
  • Test for seamless re-authentication: Test your site with timed logouts to ensure users can continue their tasks without losing progress.
  • Ensure security without disruption: Balance security protocols with usability to offer a smooth, secure re-authentication experience.

Further reading

Previous articleNext article
Back to top