Computer Science · 9th Grade

Active learning ideas

Designing Accessible Interfaces

Active learning works because accessibility design demands empathy beyond abstract rules. Students must physically experience limitations to internalize how barriers shape user experience, turning guidelines into lived practice rather than distant requirements.

• Common Core State Standards
• CSTA: 3A-AP-16
• CSTA: 3A-IC-26

• 15–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Gallery Walk
• 40 min · Small Groups

Gallery Walk: Accessibility Audit

Post screenshots of five real websites around the room. Student groups rotate through each, using a provided checklist (contrast, alt text, keyboard navigation, label clarity) to score the site's accessibility. Groups share their worst finding with the class and suggest one fix.

Explain how to design software that is accessible to users with different physical abilities.

Facilitation Tip

During the Gallery Walk, position yourself at a midpoint so you can overhear discussions and redirect common misconceptions about what counts as an accessibility feature.

What to look for

Students pair up and exchange wireframes of a simple interface feature (e.g., a login form). Each student critiques their partner's design, identifying one area that could be more accessible and suggesting a specific improvement related to keyboard navigation or color contrast.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 02

• Case Study Analysis
• 25 min · Individual

Simulation Experience: Keyboard-Only Navigation

Students attempt to complete a set of tasks on a website using only the keyboard, no mouse or trackpad. They document which tasks were impossible or frustrating, then discuss what interface changes would have helped.

Critique existing interfaces for their accessibility features.

Facilitation Tip

For the Keyboard-Only Navigation simulation, physically sit next to students to see where they hesitate or resort to mouse use, then ask them to verbalize their struggle.

What to look for

Provide students with a screenshot of a common website or app. Ask them to list two specific accessibility features they would add or improve, explaining why each change would benefit a particular user group.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 03

• Case Study Analysis
• 35 min · Pairs

Redesign Challenge: Make It Accessible

Pairs receive a wireframe of an inaccessible form or interface. They identify at least four accessibility violations and produce a revised wireframe that addresses each. Pairs present their before-and-after to another pair for peer feedback.

Construct an interface that incorporates principles of universal design.

Facilitation Tip

In the Redesign Challenge, provide color contrast checkers and keyboard testers so students validate their solutions against measurable standards rather than aesthetic preference.

What to look for

Present students with a short scenario describing a user with a specific disability (e.g., a user who cannot use a mouse). Ask them to identify three actions that user would struggle with on a given interface and propose one design change to address each struggle.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 04

• Think-Pair-Share
• 15 min · Pairs

Think-Pair-Share: Who Benefits from Captions?

Students individually list all the situations where video captions are useful beyond deaf viewers. They share with a partner, then the class compiles a full list. This reframes accessibility as universal benefit rather than accommodation.

Explain how to design software that is accessible to users with different physical abilities.

Facilitation Tip

Keep the Think-Pair-Share small groups to three or four so every voice is heard when identifying who benefits from captions beyond the deaf community.

What to look for

Students pair up and exchange wireframes of a simple interface feature (e.g., a login form). Each student critiques their partner's design, identifying one area that could be more accessible and suggesting a specific improvement related to keyboard navigation or color contrast.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Teach accessibility as a design constraint, not a checklist. Use repeated simulations to build frustration first—frustration that fuels better design decisions. Avoid framing it as charity; emphasize that inclusive design expands audiences and improves usability for everyone. Research shows students retain accessibility principles better when they experience the barriers directly rather than read about them.

Students will move from recognizing accessibility to applying it. They should articulate specific design choices that remove barriers, justify those choices with user needs, and critically assess interfaces against real-world standards.

---

Watch Out for These Misconceptions

• During the Keyboard-Only Navigation simulation, watch for students who assume accessibility only applies to permanent disabilities.

  After the simulation, ask students to describe situations where temporary limitations—a sprained wrist, a phone held in bright light—would force them to rely on keyboard-only navigation, then connect those moments to universal design.

• During the Redesign Challenge, watch for students who equate accessibility with removing visual appeal.

  During the peer review phase, have students compare their redesigned interfaces against the originals and identify two features that improved both accessibility and visual hierarchy, reinforcing that constraints drive creativity.

---

Methods used in this brief

• Gallery Walk
• Case Study Analysis
• Think-Pair-Share