Running an accommodated test for a CTSO competition on general-purpose testing software usually means a manual workaround for every student who needs one - a separate timer, a side conversation with a proctor, a note taped to a monitor. It works, until it doesn't, and the student who needed the accommodation is the one who pays for it.
Accommodations that apply automatically, not manually
A student with extended time or read-aloud support on file should get it the moment their test opens - not because a proctor remembered to set a special timer, but because the system already knows. That single change removes the most common way accommodations get missed: a busy testing room and a human forgetting a manual step.
A dropped connection shouldn't end the attempt
Testing rooms have bad WiFi days. If a connection drops mid-test, the system should detect it, record exactly what happened, and let an event manager reopen the attempt - rather than the student losing their progress and having to argue their case after the fact with no record of what went wrong.
Idle and focus-loss handling that explains itself
Auto-submitting a test after idle time or a lost tab focus is a reasonable integrity safeguard, but only if the student understands why it happened. Surfacing the actual reason - not just an automatic zero - keeps a legitimate technical hiccup from looking indistinguishable from someone trying to cheat.
A reopen queue instead of an email chain
When something does go wrong, a student should have one clear way to ask for a reopen, and an event manager should have one queue to review those requests - not a scattered set of emails and hallway conversations that are impossible to track consistently across a whole conference.
Accommodated testing done right is invisible to the student who needs it - the extra time and support are just there, without them having to ask for it separately from everyone else in the room.