Screen Reader Guide

SCREEN READER FOUNDATIONS

0 of 20
Course progress: 0 / 20 lessons

PRACTICE 4 OF 6 · Dynamic updates

Timeout warning

Trigger a session warning and test whether users get enough notice and control.

  • Level: Intermediate
  • Time: 5-10 minutes
Objective

Verify that time limits are announced and include keyboard-operable controls to extend time.

PREPARE

Set up your test

  1. Turn on a screen reader you know how to operate.
  2. Navigate by controls or use Tab where the task asks you to.
  3. Listen for purpose and state, not one exact sequence of spoken words.

WORKING EXAMPLE

Establish the expected behavior

Trigger the warning. Listen for it and confirm the extend control is keyboard operable.

Expected behavior: the warning is announced and includes a keyboard-operable way to extend time.

INTENTIONAL DEFECT

Find the barrier

The example below deliberately contains one accessibility defect. Skip the defective example.

Trigger the warning. Determine whether it is announced and whether you can extend the session.

Hint

A warning that appears silently and has no action may not give users a fair chance to respond.

End of intentional defect.

DIAGNOSE

Choose the primary cause

What makes the defective timeout warning risky?

EXPLANATION

Understand and repair it

Reveal explanation

What happened

The defective warning appears visually but does not announce itself as important information and does not provide a way to extend the session.

Repair

Use an appropriate alert or dialog pattern for time-sensitive warnings and provide controls to extend or save work where possible.

<div role="alert">
  <h2>Session ending soon</h2>
  <button type="button">Extend session</button>
</div>

Retest

  • Trigger the warning and confirm it is announced.
  • Confirm the user can extend time with the keyboard.
  • Confirm timing is long enough for screen reader users to understand and act.

Report it

Example: The session timeout warning appears silently and offers no keyboard-operable extend option, risking unexpected data loss.

Standards and support

This exercise describes behavior rather than promising identical speech across screen reader and browser combinations.

Editorially reviewed 20 July 2026.