Core structure
The minimum useful task includes an instruction screen, a practice block, a formal block, feedback or completion, and fields that mark every row with phase and condition.
- Instruction
- Practice
- Formal trials
- Completion
- Export fields
Reaction-time tests for web experiments
Reaction-time tests need clear stimuli, stable response mapping, and export fields that make later analysis easy to trace.
Data fields
The data table should make every trial readable without opening the source code. Clear field names reduce analysis errors and help reviewers audit the task.
- rt
- response_key
- correct
- condition
- stimulus_id
- phase
Run checks before sharing
Quality checks should catch empty screens, missing keys, unreachable branches, low trial count, and missing completion events before publication.
FAQ
What is a reaction-time task?
A reaction-time task records response speed and accuracy while a participant reacts to a stimulus, key, or decision prompt.
Can browser tasks collect useful timing data?
Browser timing can support lightweight studies and product experiments. High-stakes lab protocols still need device control and calibration.
Which fields should be exported?
Record stimulus id, condition, response key, correctness, reaction time, block label, exclusion flags, and session id.