Operations & Systems

Session Timeouts in B2B Portals: Give Users a Defined Way to Keep Working

A buyer reads a proposal while the portal waits for another click. The buyer is working. The portal's inactivity clock keeps running.

Start a timeout review with the task a person needs to finish. Record which event starts the clock, what the warning offers, and what happens after the person responds. Follow the task through expiry as a separate attempt.

The worksheet below turns those observations into decisions a product owner can inspect. Its examples are invented. They describe a review process, not a tested vendor or a promise that a draft will survive.

Inventory the Limits Around the Task

Write the task as an observable destination: review a proposal, add a comment, and submit a recommendation. Identify every screen used along the way.

Create separate inventory rows for the session limit, any timed confirmation, and any other content-imposed deadline encountered during that route. Mark unknown durations as unknown until the owner supplies configuration evidence or a repeatable test establishes them.

W3C's Understanding Timing Adjustable guidance explains that content-imposed limits include organization-controlled server limits, including those introduced for security. Limits outside the author's control have a different boundary. The Understanding document is informative guidance.

Ask what “activity” means in the tested configuration. Does selecting text reset the timer? Does typing in a comment? Record the configured rule beside the observed behavior. Reading and inactivity are different descriptions of the same interval.

Do not infer the rule from a label in an administration screen. The field may describe one limit while another screen introduces a separate deadline. Assign each observed interruption to an owner who can explain it.

Keep unrelated machine scheduling outside this inventory. The relevant question is what constrains the person completing the business task.

Choose a Defined Route Through SC 2.2.1

WCAG 2.2 SC 2.2.1, Level A gives alternatives for each content-set limit:

  • Turn it off before encountering it.
  • Adjust it beforehand over a wide range reaching at least ten times the default.
  • Receive warning with at least twenty seconds for a simple extension action, available at least ten times.
  • Establish a required real-time event with no possible timing alternative.
  • Establish that extension invalidates an essential activity.
  • Use the exception for a limit longer than twenty hours.

These are alternative provisions. Choose the applicable one for the row. Do not require every portal to implement all three user controls.

Separate this criterion review from a guarantee about draft recovery. The worksheet records expiry outcomes because the owner needs them. One successful extension does not establish preservation under every failure condition.

Keep the chosen provision beside the evidence. A screenshot of a warning does not by itself establish how long the action remains available or how many extensions work.

Define the Proposal Review Fixture

Use a synthetic environment containing an invented proposal and an existing test identity. Give the proposal dummy comments that are safe to discard. Keep customer documents out of the run.

Record the product build, browser version, account configuration, and timer settings. Define the starting state and the last action that resets the clock. Use the same start condition for comparison runs.

Suppose the fictional fixture uses a fifteen-minute inactivity limit. The ordinary task is to read a proposal, write a comment, review it, and submit a recommendation. Reading alone does not reset this fixture's timer.

A warning appears after fourteen minutes and thirty seconds. It offers a control labeled Keep working. Expiry remains scheduled for fifteen minutes unless the reviewer acts. All values and labels in this example are invented.

Write the expected result before running the fixture. For the extension attempt, specify which action should restart the timer and where the person should remain. For expiry, specify what the product owner expects to happen to the comment.

Those expectations are acceptance conditions for this fixture. They are not evidence that the behavior occurred.

For a proposed adjustment check, use this fictional fifteen-minute default. A maximum of sixty minutes reaches four times the default. A range reaching 150 minutes reaches ten times it. Record the available range, then start a fresh task with the selected setting. Keep the arithmetic separate from evidence that the setting takes effect.

For a proposed turn-off check, select that option before starting the timed task. Follow the same route beyond the former expiry point. Record whether the task remains available. Leave other limits in separate rows even when this option removes the session clock.

Measure Warning and Extension Separately

Start the fictional clock at 10:00:00. The warning appears at 10:14:30. The stated expiry is 10:15:00. The available response window is thirty seconds.

In this invented run, the reviewer activates Keep working at 10:14:40. The portal displays a new expiry of 10:29:40. That result supports one successful fifteen-minute restart in the fixture.

Record the warning time, action time, and resulting expiry separately. A disappearance of the warning alone would leave the extension outcome uncertain. Ask the owner what observable state confirms the new limit.

Repeat the extension attempt across the configured allowance. In the first fictional build, the control works nine times. At the tenth warning, the control is unavailable. No turn-off or adjustment option exists in this fixture, and no exception has been established.

The worksheet therefore leaves the extension provision unresolved. Nine successful actions cannot establish an allowance of at least ten. The product owner has a concrete boundary to revise or explain.

Keep an expiry attempt separate from an extension attempt. In the fictional expiry run, the portal returns to login and the unsubmitted dummy comment is absent after return. Record that outcome. Do not silently turn the missing comment into an assurance about other saved content.

Copy the Timeout Worksheet

Add an environment header with the run identifier, reviewer, date, build, browser, and starting state. The worksheet is a proposed working method.

Field What to record
Task Business action and intended destination
Limit Duration and source of the value
Trigger Event starting or resetting the clock
Warning Appearance time, expiry time, and available action
Adjustment option Turn-off or adjustment behavior before the limit, or none found
Extension observations Action, response window, resulting expiry, and allowed repetitions
Expiry outcome Destination and observed state of the synthetic draft
Exception evidence Chosen provision, supporting reason, and unresolved questions
Owner Person responsible for the next decision and retest

Use one row per limit. A comment confirmation and a session clock can share a task while requiring different rows.

The fictional proposal run produces this compact record:

Task Limit and trigger Warning Adjustment option Extension observations Expiry outcome Exception evidence Owner
Read and comment Fifteen minutes from last recognized action Thirty seconds before expiry None found Nine work; tenth unavailable Login; dummy comment absent on return None established Portal product owner

Attach the run log showing the individual extensions. A summary row should point to the detail that supports its count.

If a limit is configurable but the reviewer lacks access to the setting, mark it unverified. An administrator's intended value and an observed value belong in separate fields.

Review Security and Essential Claims With Evidence

Ask for the exact activity the limit protects. Then ask why extending that activity would invalidate it. Record the answer and its source rather than entering “security” as a complete explanation.

The informative W3C guidance notes that certain time-limited authentication tokens may be essential. That observation does not classify every portal session as essential.

For the fictional proposal, the owner supplies a design note saying sessions expire for security. The note does not explain why additional reading time invalidates proposal review. Leave the exception unestablished.

Assign the missing explanation to the relevant owner. Ask whether another user control can satisfy the timing provision while preserving the intended protection. Keep token design and regulatory analysis with their designated specialists.

If the owner later supplies an exception rationale, review its scope. A rationale for one confirmation step does not automatically cover the document reader, comment editor, and every future workflow.

Do not change a security setting during the review. Return the evidence and the decision required. This worksheet establishes neither an authentication architecture nor a regulatory timeout rule.

Retest the Whole Business Path

Suppose the fictional owner revises the extension allowance. A later test build permits ten successive extensions. Retest from the agreed initial state and retain evidence for all ten attempts.

Check the reading screen, comment editor, preview, and final review in the same task path. Record whether moving between them changes which limit applies. Avoid closing the task because only the first screen now behaves as expected.

Test the warning control through the relevant interaction methods within the agreed scope. Use the keyboard-navigation review for reaching, activating, and leaving controls. Record that work beside the timing result.

Use the accessible-form review for comment instructions and repair messages. A timing worksheet should not absorb every other accessibility question on the screen.

For the fictional revision, retain the missing-comment expiry observation until a separate retest addresses it. Passing extension evidence and an unresolved expiry outcome can coexist in the same report.

If a test cannot run long enough to observe every repetition, say which repetitions were exercised. A configuration value can support the investigation, but the report should distinguish that value from observed execution.

Hand Over a Bounded Decision

Return the inventory, worksheet, run records, and open questions together. Give each unresolved row an owner and a specific next action.

For the first fictional build, the next action is to address the extension allowance or establish another applicable provision. The draft outcome needs its own product decision. Avoid combining those issues into “increase the timeout.”

Use deliverable acceptance criteria to specify the evidence the owner will review. Name the test build, route, timing window, repetition count, and observed destination.

Keep proposed behavior in a different column from observed behavior. If the owner accepts a future change, the row remains awaiting retest until the new build supplies evidence.

Close the review with an explicit boundary: the named task, configuration, criterion, and runs examined. List untested branches and outstanding exception claims. Make no whole-site or legal compliance statement from this worksheet.

Give the person a defined way to continue.

Sources

Topic map: Accessible B2B websites

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Accessible B2B websites

Neighbor: Technical SEO, crawling, and migrations

Neighbor: Customer and usability research

Neighbor: Topical authority and keyword strategy