Online Voting Session Timeouts: Accessibility Checklist

Online voting session timeouts should give voters a workable way to get more time, unless a specific WCAG exception applies. This checklist explains the timing requirements, how to test warnings and recovery, and why extending a login session is different from extending an election deadline.

Separate the session timer from the election deadline

A voting window can stay open for a week while a voter’s session expires after 10 minutes. Those are different clocks. A long election window does not solve a short, inaccessible session limit.

Consider a hypothetical association ballot with eight board candidates and two bylaw amendments. A member using a screen reader listens to candidate statements, compares the amendments, and returns to the ballot. The application registers no clicks during that reading time and logs the member out. The voter was participating. The software treated that participation as inactivity.

Before approving your election accessibility plan, inventory every timer: inactivity logout, absolute session expiration, credential expiry, warning countdowns, and the published closing time. Ask which system controls each one.

Record the closing time and time zone separately. Whether a fixed election cutoff qualifies for a WCAG exception requires an election-specific assessment, not a blanket assumption. Counsel and election officials should resolve that question before launch. An adjustable session must not silently authorize ballots after the approved cutoff.

Apply the right WCAG timing requirement

WCAG Success Criterion 2.2.1, Timing Adjustable, is Level A. It applies to content-controlled time limits, including ordinary server-side session timers. For a timer without an applicable exception, provide at least one of these options:

• Turn it off: Let the voter disable the limit before encountering it.


• Adjust it: Let the voter set the limit in advance across a range at least 10 times the default.


• Extend it: Warn before expiration, allow at least 20 seconds for a simple action, and permit at least 10 extensions.

These are alternatives, not three requirements that every ballot must implement together. WCAG does not prescribe one universal session duration. A 60-minute default is not an automatic compliance safe harbor.

The criterion includes real-time, essential, and longer-than-20-hour exceptions. A general statement that timeouts improve security does not establish an exception. Some time-limited authentication tokens may be essential, but that does not exempt every timer in the login journey.

Also distinguish SC 2.2.6, Timeouts. This Level AAA criterion addresses notice of inactivity that could cause data loss. It is not a blanket Level AA requirement to store unfinished ballots for 20 hours.

Run this session-timeout test before voting opens

Use a staging election with the final authentication settings and a realistic ballot. Test accounts and invented selections keep real voter credentials and choices out of your evidence. Follow the same path voters will use, including external sign-in services.

1. Establish the timers. Record configured limits and what resets them. Compare inactivity logout with any absolute session limit.


2. Trigger a warning. Pause while reading a candidate statement. Measure the actual warning period instead of relying on the vendor’s description.


3. Operate it without a mouse. Find and activate the extension control with a keyboard. Check visible focus and return to the ballot.


4. Listen with a screen reader. Confirm the warning and action are announced. A countdown should not interrupt ballot instructions every second.


5. Repeat extensions. If the system uses the extension option, verify at least 10 successful extensions and confirm the server honors them.


6. Let the session expire. Test reauthentication, selection handling, and confirmation. Repeat near closing time to check that session controls respect the election cutoff.

Capture the device, browser, assistive technology, build, observed result, and correction owner. Add this test to your election operations release checklist. A scan of the public homepage cannot establish how an authenticated timeout behaves.

Make recovery useful without exposing ballot choices

Recovery has two separate jobs: restore access and protect the secret ballot. A voter who signs back in needs clear information about whether an unfinished ballot remains available and whether a submitted ballot was accepted.

Do not assume the application should save every draft selection in browser storage. On a shared computer, that could expose choices to the next user. Ask your vendor how drafts are protected, who can access them, when they are deleted, and whether recovery creates any link between identity and selections. Review the answers against your election’s secrecy rules.

Support staff should troubleshoot access without asking a voter to read selections aloud or email a ballot screenshot. Use test ballots when reproducing defects. Keep operational timestamps and error details separate from ballot choices wherever possible.

Decide before launch what happens if a voter reports a timeout near closing. Publish an accessible support route and escalation owner. Staff should not promise a deadline extension or invent an alternative voting method during a call. Apply the approved election rules and document the decision without recording the voter’s preferences.

Frequently Asked Questions

Are session timeouts allowed under WCAG?

Yes. A content-controlled timer must meet an applicable option under SC 2.2.1 or qualify for a specific exception. WCAG does not require every voting system to eliminate all time limits.

How much warning must a timeout give?

Under SC 2.2.1’s extension option, give at least 20 seconds to extend the limit with a simple action and allow at least 10 extensions. Test whether the warning is usable, not just visible.

Does extending a session extend the election deadline?

No. Session duration and the election closing time are separate controls. Check the applicable election rules and have the cutoff’s accessibility treatment reviewed before opening the vote.

Must an online ballot save unfinished choices for 20 hours?

Not as a universal Level AA requirement. SC 2.2.6 is Level AAA and addresses inactivity notices or preservation beyond 20 hours. Any draft-saving design still needs a ballot-secrecy and privacy review.

The Bottom Line

A timeout review is finished only when a voter can understand the warning, get more time where required, and recover without losing privacy. Keep the technical timer, the ballot’s status, and the election cutoff distinct.

If you are preparing an online member election, ask Votem to review your timing, accessibility, and voter-support requirements before you approve the launch settings.