Examination of the Effects of Auditory and Textual Stimuli on Response Accuracy and Latency during a Math Task and Tangram Puzzle.

Kodak et al. (2018) asked adults to solve math problems and tangram puzzles while different sounds played. Some trials added beeps or voices. Other trials paired the noise with written words on the screen. The team tracked how fast and how accurately people answered.

Each person served as their own control. The order of sound and text conditions switched around so the researchers could see the pure effect of the stimuli.

Background noise hurt math performance. People made more errors and took longer to respond when beeps or voices were present. Written words on the screen protected accuracy. When text appeared with the noise, scores bounced back close to quiet levels.

The tangram puzzles stayed the same no matter what played. Auditory or textual cues did not change speed or correctness on the visual puzzle task.

McWilliams et al. (2025) later showed textual prompts also help children with autism talk about past events. Both studies reveal that a few written words can offset auditory load, whether the task is math or conversation.

The result seems to clash with Marcell et al. (1988). That team removed distractions for adults with Down syndrome yet saw no memory gain. The difference is population: Tiffany worked with neurotypical adults who could use text as a cue, while M et al. tested memory in people with intellectual disability where cueing alone was not enough.

Shearn et al. (1997) and Goodwin et al. (2012) already proved that starting with easy, high-preference math problems cuts the time kids take to begin harder ones. Tiffany adds a new layer: once the session starts, guard accuracy by controlling noise and offering textual anchors.

You cannot always silence a busy classroom or clinic. When noise is unavoidable, drop a textual prompt on the desk or tablet. A written question, number line, or keyword list can keep performance steady without calling for quiet. Test the setup during one session this week: run a short math probe with background talk, then repeat the same probe with a text sheet visible. Track latency with a stopwatch and count correct digits. If the client speeds up or makes fewer errors, you have an easy, low-cost support that travels anywhere.