Skip to content
Computing · Year 9

Active learning ideas

Representing Characters (ASCII/Unicode)

Active learning works for this topic because students need to see the gap between what they type on screen and what the computer stores in binary. These activities let pupils hold the bits in their hands, convert them themselves, and watch encoding problems appear in real files. That gap between expectation and reality drives the ‘aha’ moments that stick better than any explanation alone.

National Curriculum Attainment TargetsKS3: Computing - Data RepresentationKS3: Computing - Binary and Digitisation
25–45 minPairs → Whole Class4 activities

Activity 01

Case Study Analysis30 min · Pairs

Binary Encoding Challenge: ASCII Letters

Provide letter-to-binary charts for A-Z. Pairs encode their names into 7-bit ASCII, then decode classmates' binary back to text. Discuss bit limitations with symbols. Extend to group sharing via printouts.

Explain the necessity of character encoding standards like ASCII and Unicode.

Facilitation TipFor the Binary Encoding Challenge, have students work in pairs with printed ASCII tables, forcing them to verbalize each binary step aloud while converting their partner’s name.

What to look forProvide students with a short sentence containing both English letters and a common symbol (e.g., 'Year 9 is cool!'). Ask them to: 1. Write the ASCII binary code for the first three letters. 2. Explain why Unicode would be necessary if the sentence included a character like 'é'.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 02

Case Study Analysis45 min · Small Groups

Unicode vs ASCII Display Hunt

Small groups open text files saved in ASCII and UTF-8 with international characters or emojis. Note display differences on different apps. Predict fixes by changing encodings, then test.

Compare the limitations of ASCII with the advantages of Unicode.

Facilitation TipDuring the Unicode vs ASCII Display Hunt, give each group a USB drive with differently encoded copies of the same poem so they can physically swap files and observe changes on the same screen.

What to look forDisplay a short text file that has been saved with an incorrect encoding (e.g., a UTF-8 file opened as Latin-1). Ask students: 'What do you see happening to the text? What is the likely cause of this display issue?'

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 03

Case Study Analysis40 min · Small Groups

Mojibake Mystery Solving

Distribute files with intentional encoding mismatches showing garbled text. Groups identify the error type, convert using online tools, and recreate issues. Present findings to class.

Analyze how different character encodings can lead to display issues if not handled correctly.

Facilitation TipIn the Mojibake Mystery Solving station, provide hex editors on low-power laptops so students can edit bytes directly and watch characters flip in real time, reinforcing the link between binary and display.

What to look forPose this question to small groups: 'Imagine you are designing a new global messaging app. What character encoding standard would you choose, and why? What potential problems might you still encounter, even with your chosen standard?'

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 04

Case Study Analysis25 min · Individual

Custom Character Map Creation

Individuals design a mini 8-bit extension to ASCII for 10 new symbols. Share and vote on class set, discussing why standards matter over personal codes.

Explain the necessity of character encoding standards like ASCII and Unicode.

Facilitation TipWhen groups create their Custom Character Map, insist they include at least two emojis and two accented letters so they confront Unicode’s expanded range immediately.

What to look forProvide students with a short sentence containing both English letters and a common symbol (e.g., 'Year 9 is cool!'). Ask them to: 1. Write the ASCII binary code for the first three letters. 2. Explain why Unicode would be necessary if the sentence included a character like 'é'.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

A few notes on teaching this unit

Approach this topic as a detective story: start with the familiar (letters) and quickly reveal the hidden system of bits, then show how that system breaks when faced with global text. Avoid long lectures; instead, structure each activity so errors are inevitable and therefore productive. Research shows that debugging encoding issues in authentic files cements understanding far more than abstract slides can. Keep tools simple—plain text editors and hex viewers are enough to expose the gap between storage and display.

By the end of the activities, students can convert text to ASCII binary and back without error, explain when Unicode is required, and debug garbled text by checking file encodings. They will justify choices of encoding for multilingual messages and identify the limits of each standard through first-hand evidence.


Watch Out for These Misconceptions

  • During the Binary Encoding Challenge, watch for students who assume ASCII covers all their keyboard symbols.

    While students encode their first names, have them hit keys like ‘é’ or ‘€’ and notice the blank cells in the printed ASCII table. Immediately shift to Unicode conversion using an online tool so they see the new code points appear.

  • During the Unicode vs ASCII Display Hunt, watch for the belief that Unicode stores pictures instead of codes.

    In the hunt, ask groups to open a UTF-8 file containing an emoji and a hex editor side-by-side. They will see the emoji’s hex codes (e.g., 0x1F600) and recognize the pattern matches ASCII, not an image file.

  • During the Mojibake Mystery Solving, watch for the idea that encoding doesn’t affect binary storage.

    When groups flip one bit in a UTF-8 ‘é’ (0xC3 0xA9), ask them to reopen the file in a hex editor. They’ll observe the binary changed and the text corrupted, proving encoding directly alters stored bits.


Methods used in this brief