Grades 6–9 · STEM & Computer Science

How do you teach students to design and test an accessible emergency alert in Grades 6–9?

Short answer: Give students two alert prototypes, a user profile and a set of test conditions. They predict where each prototype fails, compare them against a measurable test, and propose a multi-channel redesign. Students also design how the alert signals that a drill has ended and report where their model does and does not work.

  • Grades6–9
  • FocusUser profiles, multi-channel cues, test design
  • Lessons4 × 90-minute double lessons
  • Format42-page PDF and 16 slides with teacher notes
Get Design an Accessible Emergency Alert – $24.99

An alert that nobody notices is not an alert. Students understand this quickly when they imagine someone wearing hearing protection, or sitting with their back to a flashing light. The design problem is clear, and it gives middle school engineering a real reason to test against users rather than against the designer's own experience.

The Design an Accessible Emergency Alert unit is a classroom model, not a real safety procedure. Students compare prototypes on paper and in simple tests, using a user profile and conditions stated in each case. The emphasis is on measurable tests and honest reporting: what the model shows, and what it does not.

Units for this topic

Two prototypes, two tests

Prototype A uses a siren alone. Prototype B pairs a visible flashing icon with a vibration puck. The tests include a learner wearing hearing protection and a learner facing away from the board. Students select a prototype, predict its limits in both tests, and propose a way to signal when a drill ends.

Prototype A fails the hearing protection test. Prototype B handles that case, but the flashing icon may be missed by someone facing away, so the vibration has to carry the message. Students who reason through both tests see why redundancy matters.

  • Who is the user and what do they need
  • Which channels does each prototype use
  • Which test condition could block each channel
  • How is the end of the alert signaled

Adding and testing a second channel

In the second context, a prototype uses flashing only while a student faces away. Students add a second channel and test it. A worksheet task describes a user who cannot reliably feel vibrations, and students explain what a multi-channel redesign adds for that person.

The learning check item raises a subtle problem: a visual alert and a vibration both use identical start and end cues. Students identify what should be tested, which is whether a user can tell the start from the end.

Conflicting cues and limits of the model

One case has two cues that occur at the same time but mean opposite things to different learners. Students decide what changes first, which leads into a discussion of consistent signals. Another case describes a class model that works from the front row but fails behind a divider. Students practice reporting this accurately rather than claiming the design works.

The formative note in the unit is important here: a successful run under one condition does not establish reliability outside the tested cases. Students write that sentence into their reports in their own words.

Engineering design without real alarms

All prototypes are classroom models. Students can build simple versions with paper icons, a phone vibration or a desk buzzer, or work entirely from case descriptions. The unit does not ask students to design or change real school emergency procedures, and the teacher background explains how to keep that line clear when students make connections to their own building.

The prerequisite routine keeps tests fair: describe the input and expected behavior, run the test, record what happened, and change one feature at a time.

What comes in the unit

The 42-page Teaching Unit PDF sets out four 90-minute double lessons: a first reading of the prototypes and a model of channels and users, a revised case in a new context, a round of testing and transfer, and an independent learning check with feedback. It includes an entry diagnosis, differentiation notes, teacher background, five learner inputs with mini-checks, five ready-to-copy worksheets with answer keys, and support and extension cards. The 20-point learning check comes with model responses and a 100-point scoring sheet, and peer review pages let students test each other's redesigns. Sixteen slides with teacher notes are included.

A five-step sequence

  1. Introduce the user profile

    Read the profile and the test conditions aloud. Ask students what an alert must do for this person.

  2. Predict before testing

    Students predict where prototype A and prototype B fail in each test and record predictions.

  3. Run fair tests

    Test each prototype under the same conditions. Record what happened, not what was expected.

  4. Redesign with another channel

    Add or change one channel at a time and retest. Include a distinct end-of-drill signal.

  5. Report honestly

    Write a short report naming where the design worked, where it failed, and what was not tested. Then complete the learning check.

Common mix-ups and what to try

Instead of

A louder siren solves the problem.

Try

Volume does not help a user with hearing protection. A second channel such as vibration or light does.

Instead of

If the test worked once, the design is reliable.

Try

One successful run only shows it worked in that condition. The divider case shows a design can fail elsewhere.

Instead of

Start and end signals can be the same.

Try

Users need to tell them apart. The learning check asks students to test this directly.

More STEM & Computer Science units

Related teaching guides

Frequently asked questions

Do students design real school alarms?

No. All prototypes are classroom models. The unit does not involve changing real emergency procedures.

What materials are needed?

Paper icons and case cards are enough. Optional simple devices such as a buzzer or phone vibration can make tests more concrete.

Which course does it fit?

Engineering design, STEM electives, computer science or technology classes in Grades 6–9.

How does it handle disability topics?

Through user profiles and test conditions described in the cases, with a focus on design choices rather than labels.

What if it does not match our design standards?

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.

How is the learning check structured?

A 20-point independent task with model responses, scored on a 100-point sheet that credits predictions, test design and honest reporting.

Ready for your next lesson?

Teach design that works for every user with Design an Accessible Emergency Alert.

View Design an Accessible Emergency Alert

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.