Grades 3–6 · STEM & Computer Science

How do you teach accessible game design in Scratch in Grades 3–6?

Short answer: Start with a draft game that only works one way, such as advancing on a mouse click with success shown only by a sound. Have students test it as a keyboard-only player and as a player with the sound off. They then add an equivalent key input and a visible success cue, and record each test in a two-column grid.

  • Grades3–6
  • ToolsScratch if available, paper test grids otherwise
  • Lessons4 double lessons, 90 minutes each
  • Includes42-page PDF, 16 slides, 5 worksheets with keys
Get Accessible Game Design in Scratch – $24.99

Students in Grades 3–6 build games quickly. What they rarely do is test whether someone else can play them. A game that needs a mouse click shuts out a player who uses the keyboard, and a game that signals success with a beep tells a muted player nothing.

The Accessible Game Design in Scratch unit turns those problems into test cases. Students play a draft game under specific conditions, write down what happens, and make one change at a time. The aim is a game that gives every player at least two ways in and at least two ways to know what happened. Scratch is used if available, and every task can also be planned on paper.

Units for this topic

The draft game and two testers

The starting case is a draft game that advances only when a sprite is clicked. A sound announces success, but the stage looks unchanged. One tester uses the keyboard only. Another plays with the game muted. Neither tester can complete the game or tell that they succeeded.

Students plan two changes: an equivalent keyboard event that does the same thing as the click, and a visible success cue such as a costume change, a text message or a backdrop switch. They create a two-column test grid, one column for the input and one for the feedback, and implement both behaviors in Scratch if it is available.

  • Input: can the player act with mouse and with keyboard
  • Feedback: can the player see and hear the result
  • Record: what happened in each test
  • Change: one feature at a time, then test again

Variations that reveal design thinking

The second context flips the problem. A game accepts key input but shows feedback only as a beep. Students design another observable cue. In a third case, a click changes the game state but pressing Enter only moves focus. Students decide what the second event should do so both inputs are truly equivalent.

A worksheet task adds a subtle bug: pressing both inputs once advances the game twice. Students propose and test a design change, which introduces the idea that adding an input can create a new problem that also needs testing.

Timers and ambiguous icons

The transfer challenge is a game with a timer and no warning when it ends. Students design and test a visible countdown. The learning check item describes a game that shows a new icon for success with no text, and the icon is ambiguous. Students explain what visible change would make success clearer.

These cases connect to how players actually experience games. A player who misses a cue does not know the rules, and a player who cannot use an input cannot play at all.

Testing habits, not just features

The unit's prerequisites set out a testing routine: describe the input and expected behavior, run the test, record what happened, and change one feature at a time. The formative note adds a caution students need to hear: a successful run under one condition does not prove the game works under others. Testing as a muted player does not tell you how a keyboard-only player experiences the same screen.

Students who finish early can test a partner's game and log issues using the same grid. This builds the habit of reporting problems clearly enough for someone else to fix them.

Pacing across four double lessons

The first double lesson moves from the draft game to a model of input and feedback. The second applies the model to the key-only and beep-only cases. The third tests the double-advance bug and the timer challenge. The fourth is the independent learning check, with a 20-point task, model responses and a 100-point scoring sheet, followed by peer review and a revision round. Entry diagnosis, differentiation notes, teacher background, five learner inputs with mini-checks, support and extension cards, and 16 slides with teacher notes are all included.

A five-step sequence

  1. Play the draft game

    Let students play the click-only, sound-only draft. Then ask them to try it with the keyboard only and with the sound off.

  2. Build the test grid

    Students draw two columns for input and feedback and record what each tester could and could not do.

  3. Add one input

    Program an equivalent key event that does exactly what the click does. Test it and record the result.

  4. Add one visible cue

    Add a costume change, message or backdrop switch for success. Test it muted and record the result.

  5. Check and peer test

    Run the learning check, then swap games so each student tests a partner's game with the grid.

Common mix-ups and what to try

Instead of

Adding a sound effect makes a game accessible.

Try

A sound alone fails for a muted player. Success needs at least one visible cue as well.

Instead of

If the game works with a mouse, it works.

Try

A keyboard-only player cannot click. An equivalent key event gives them the same action.

Instead of

Adding a second input cannot break anything.

Try

The double-advance case shows two inputs can trigger the same event twice. Every change needs a test.

More STEM & Computer Science units

Related teaching guides

Frequently asked questions

Do students need Scratch accounts?

No. Students can plan and test on paper using the grid, and implement in Scratch only if your school uses it.

Is this suitable for Grade 3?

Yes, with support cards. Younger students can focus on one input and one cue, while older students tackle the timer and double-advance cases.

Does it teach Scratch from scratch?

It assumes students can make a sprite respond to an event. The focus is testing and improving a game, not learning the interface.

How does this fit with digital citizenship?

Designing for players with different needs is a concrete way to discuss inclusion and responsibility in technology.

What if our CS standards are different?

Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.

What does the teacher background cover?

It explains the input and feedback model, common student errors, and how to run peer testing in a mixed-device classroom.

Ready for your next lesson?

Teach students to test their games for every player with Accessible Game Design in Scratch.

View Accessible Game Design in Scratch

Instant digital download. Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.