Skip to main content
Perceivly: Perceivly home

2.2.5 Re-authenticating

Level AAA · added in WCAG 2.0

When a signed-in session expires, users must be able to sign in again and carry on where they left off. Nothing they entered should be lost.

Who it helps

People with motor, cognitive or vision disabilities often take longer to fill in forms. That makes them more likely to hit a session timeout. Re-entering everything after signing in again is slow, tiring and sometimes impossible.

How to meet it

Examples

Fails:After the session expires, sign-in sends users to the home page and their form data is gone
<form action="/login" method="post">
  <label for="email">Email</label>
  <input id="email" name="email" type="email" autocomplete="email">
  <label for="password">Password</label>
  <input id="password" name="password" type="password" autocomplete="current-password">
  <button type="submit">Sign in</button>
</form>
Passes:The sign-in form returns users to their step with their saved answers
<form action="/login" method="post">
  <input type="hidden" name="return_to" value="/apply/step-3">
  <input type="hidden" name="draft_id" value="d_8f2c1">
  <label for="email">Email</label>
  <input id="email" name="email" type="email" autocomplete="email">
  <label for="password">Password</label>
  <input id="password" name="password" type="password" autocomplete="current-password">
  <button type="submit">Sign in and continue</button>
</form>

Can a scanner detect this?

No

axe-core has no rule for this criterion, because it depends on how your server handles expired sessions. Fill in a form, let the session expire or clear the session cookie, submit, sign in again and check that your data is still there.

No automated rule tests this criterion. Check it by hand.

Common mistakes

Official W3C explanation of 2.2.5

Check your own page

See which automated WCAG checks your page fails, with the failing elements and how to fix them.

Enter a page address, for example example.com/shop.

Reviewed November 2, 2026