Technologies · Year 8

Active learning ideas

Assistive Technologies and Design

Active learning works well here because students need to experience the gaps between intention and access. When they try tools themselves, they notice barriers that lectures alone cannot reveal. This builds empathy and technical insight at the same time.

• ACARA Content Descriptions
• AC9TDI8K05
• AC9TDI8P05

• 20–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Stations Rotation
• 45 min · Small Groups

Stations Rotation: Assistive Tech Trials

Prepare four stations with laptops loaded: screen reader emulator, voice control simulator, magnification tool, and keyboard-only navigation. Small groups spend 8 minutes at each, testing sample websites and noting what works or fails. Groups report findings to the class.

Differentiate between various assistive technologies and their functions.

Facilitation Tip

For the Station Rotation, set each station with a brief task card and a timer so students rotate with focus rather than rushing to finish.

What to look for

Provide students with a screenshot of a simple web page element (e.g., a login form). Ask them to list two design choices that would make it difficult for a screen reader user and suggest one improvement for each.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 02

• Simulation Game
• 30 min · Pairs

Pairs Prototype: Screen Reader Button

Pairs use HTML editors to create a button with proper labels and ARIA attributes. They test it with a free screen reader tool like NVDA simulator. Pairs swap prototypes for mutual testing and suggest fixes.

Analyze how specific design choices can either enable or hinder assistive technology use.

Facilitation Tip

During the Pairs Prototype, ask students to script the exact sequence a screen reader would announce when a button is activated, forcing precision in labeling.

What to look for

Pose the question: 'Imagine you are designing a new social media app. Which three assistive technologies would be most critical to consider for initial design, and why?' Facilitate a brief class discussion on their reasoning.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 03

• Simulation Game
• 25 min · Whole Class

Whole Class Audit: Design Critique

Project student prototypes on screen. Class votes on accessibility using a checklist for voice control and screen reader compatibility. Discuss changes as a group and revise one example live.

Construct an interface element that is designed to be compatible with a screen reader.

Facilitation Tip

In the Whole Class Audit, circulate with a checklist of WCAG criteria so students compare their findings against a shared standard.

What to look for

Show students a short, unlabeled video clip demonstrating a specific assistive technology in use (e.g., someone using voice control to navigate a website). Ask students to write down the name of the technology and its primary function.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 04

• Simulation Game
• 20 min · Individual

Individual Mockup: Voice Menu Sketch

Students sketch a menu navigable by voice commands only. Use paper prototypes to simulate interactions. Share digitally for class feedback on command clarity.

Differentiate between various assistive technologies and their functions.

Facilitation Tip

For the Individual Mockup, provide grid paper and colored pencils to emphasize layout as a critical accessibility factor, not just color contrast.

What to look for

Provide students with a screenshot of a simple web page element (e.g., a login form). Ask them to list two design choices that would make it difficult for a screen reader user and suggest one improvement for each.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

A few notes on teaching this unit

Start with direct experience before theory. Research shows that empathy alone does not translate to better design; students need to test assumptions through structured simulations. Emphasize iteration: the first draft of an accessible feature is rarely the last. Avoid letting students default to visual fixes like bigger fonts without considering how screen readers interpret the same page. Use real-world examples to ground abstract concepts in concrete outcomes.

Successful learning looks like students moving from noticing problems in others’ designs to proposing fixes they can defend with evidence from their own trials. They should articulate specific features that support or hinder access, not just describe tools.

---

Watch Out for These Misconceptions

• During Station Rotation: Assistive Tech Trials, students may assume all tools feel the same for every user.

  During Station Rotation: Assistive Tech Trials, ask each pair to document one unique barrier they encountered and one moment of clarity, then share comparisons aloud to highlight differences in user needs.

• During Pairs Prototype: Screen Reader Button, students might think a button’s visual design matters most for accessibility.

  During Pairs Prototype: Screen Reader Button, have students swap scripts between pairs so they hear how the same button announces differently based on label choice, reinforcing that content matters more than appearance.

• During Whole Class Audit: Design Critique, students may believe adding color contrast fixes all accessibility issues.

  During Whole Class Audit: Design Critique, require students to test their fixes with a screen reader emulator, forcing them to address non-visual barriers they might have missed initially.

---

Methods used in this brief

• Stations Rotation
• Simulation Game