Reading Distance-Time Graphs

Help 10–13 year-olds read distance-time graphs by treating the LINE as an abstract record of a distance–time relationship, not a picture of terrain. The decisive goal is overcoming the graph-as-picture misconception (upward slope = 'walking up a hill') and slope-height confusion (judging speed by how high the line is rather than how steep). Learners should map each line segment to a motion (moving away, stopped, returning, fast vs slow), read speed from the gradient (flat = stationary, steeper = faster; when the vertical axis shows distance from the start, a downward slope = returning), translate both directions between a written journey and a graph, and compute a segment's average speed as distance ÷ time. A live motion-and-graph coupling is the primary vehicle; card-matching, annotated reference graphs, and embodied walk-the-graph activities are complementary.

• Graph-as-picture (iconic confusion): reading the line as a literal picture of terrain — e.g. an upward slope means 'walking up a hill' (Clement 1985; IOP Spark; persists to college level).
• Slope-height confusion: judging speed from a point's height on the axis instead of the line's gradient (McDermott et al.; ~half of science students err).
• Reading a distance or time value off the graph and calling it the speed — forgetting speed needs BOTH distance and time (Oak National Academy).
• Assuming the line must start at the origin (0,0) even when the object begins at a distance from the reference point.
• Drawing physically impossible graphs — vertical lines (infinite speed) or lines going 'backwards' in time.
• Confusing a distance-time graph with a speed-time/velocity-time graph and interpreting features accordingly.

• The distance-time graph itself (axes labelled, origin discussed)
• Real-time motion-sensor / data-logger trace (movement generates the line live)
• Embodied 'graph walker' — a marked distance line on the floor walked against a timer
• Journey narration cards matched to graph segments (verbal description ↔ line feature)
• Annotated segments: flat = stationary, steep = fast, opposite slope = returning

• Use real-time motion sensors / data-loggers so pupils see the graph draw itself as an object (or the pupil) moves — directly coupling movement to line and breaking the 'picture' reading (IOP Spark 'Speedy graphs').
• Use embodied 'walk-the-graph' activities: pupils physically walk a journey along a marked line while the class predicts the shape, grounding the abstraction in lived motion.
• Draw attention to the axes and units FIRST ('What does the vertical axis tell us? What does the origin represent?') before interpreting any feature.
• Go through interpretation step-by-step, linking each line segment to a specific motion, and repeat this mapping many times across varied journeys (Oak National Academy).
• Explicitly teach gradient = speed and contrast it with reading a single height value; use predict-observe-explain so pupils commit to a reading before checking.
• Use story/journey narration ('describe what is happening at each stage — moving, stopped, returning') and the reverse task: sketch the graph from a written journey.