Active learning ideas
Technology has the power to include or exclude. This topic investigates the history of accessibility, from the invention of Braille to modern screen readers and eye-tracking software. Students explore how 'universal design' ensures that software is usable by people with diverse physical and cognitive abilities.
Activity 01
Students try to navigate a popular website using only their keyboard (no mouse) or a screen reader. They record the 'pain points' and suggest coding fixes.
How has technology historically excluded certain groups of people?
Activity 02
Display different assistive technologies (e.g., high-contrast modes, voice-to-text, specialized controllers). Students rotate and discuss which user group each innovation supports.
What are the core principles of accessible software design?
Activity 03
Groups are given a 'user persona' (e.g., an elderly person with low vision) and must sketch an app interface that meets that person's specific needs.
How can coding empower marginalised communities?
A few notes on teaching this unit
Watch Out for These Misconceptions
Accessibility is only for people with permanent disabilities.
Students often forget about 'situational' disabilities (e.g., using a phone in bright sunlight). Use peer discussion to show that accessible design actually makes things better for everyone.
Making an app accessible is too difficult and expensive.
Many believe it's an 'extra' step. Hands-on modeling of simple HTML tags (like 'alt' text for images) shows that good coding practices often include accessibility by default.
Methods used in this brief
Open Source and Collaborative Movements
Trace the history of the open-source movement and its impact on collaborative problem-solving and democratic software development.
8 methodologies
The Evolution of User Interfaces
Analyse how user interfaces have evolved from punch cards to touchscreens, reflecting changes in human-computer interaction and society.
8 methodologies