Testing session timeout in a community-support application

Objectives

• Measure when the warning appears and how much usable time remains.
• Test the warning and its actions with a keyboard and screen reader.
• Evaluate countdown announcements and focus after the interruption closes.
• Check whether entered information and task position survive expiry and simulated reauthentication.
• Record six findings, useful passing checks, and limitations of accelerated timing.

Instructions

This is a fictional practice application. Nothing you enter is submitted, stored, or retained. Reloading or resetting the workspace removes all entered information. Use fictional sample information only.

Use Testing time limits and interruptions while completing the Exercise. The Testing controls accelerate otherwise slow states for practice; they do not reproduce production timing or establish whether a real duration is usable.

1. Record your browser, operating system, screen reader and versions, viewport, input method, and initial application state.
2. Review the privacy notice and initial form, then enter only fictional sample information and move to the second step.
3. Start the short automatic demonstration. Record when the warning appears, the time remaining, what is announced, and what happens at expiry.
4. Reset, use Show session warning, and test every warning action with a pointer, keyboard, and screen reader. Follow focus after each action.
5. Reset, re-enter sample information, and use Expire session. Compare the entered information and current step before and after expiry.
6. Continue through the credential-free simulated sign-in and record the step and information to which you return.
7. Reset and test Save and finish later with a keyboard. Read its confirmation and verify the stated storage boundary.
8. Identify exactly six findings. For each, record the state, timing, steps, expected and actual behavior, user impact, evidence, remediation direction, and follow-up testing.

Record the correctly named modal, visible remaining time, ordinary native form controls, and keyboard-operable save-later action as passing checks. Keep conclusions about production timing and screen-reader output limited to the environment and accelerated conditions you actually tested.