Accessibility and Inclusive Design

Active learning works for accessibility and inclusive design because barriers become visible only when students experience them firsthand. Simulations remove abstract concepts, making empathy concrete and design principles unforgettable.

• Year 10
• Technologies
• 4 activities
• 25 min–50 min

Learning Objectives

1. Analyze common digital barriers faced by users with visual impairments, such as insufficient color contrast or lack of keyboard navigation.
2. Evaluate the effectiveness of existing digital interfaces based on accessibility principles and inclusive design standards.
3. Design a prototype for a digital feature that incorporates at least three specific accessibility enhancements.
4. Explain how accessible design benefits users without permanent disabilities, citing examples like resizable text or clear navigation.
5. Critique the reasons why accessibility is often overlooked in software development cycles.

Experiential Learning

⏱ 45 min·Small Groups

Simulation Stations: Experience Barriers

Set up stations with tools like color blindness simulators, screen readers, and one-handed gloves. Small groups spend 8 minutes per station attempting tasks such as form filling or image identification. They record barriers and brainstorm fixes in shared notes.

Prepare & details

How does an accessible design benefit users who do not have a permanent disability?

Facilitation Tip: During Simulation Stations, circulate with a timer to keep rotations tight and prevent over-explaining in one group.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Experiential Learning

⏱ 30 min·Pairs

Pairs Audit: Check Real Sites

Provide WCAG checklists focused on contrast, navigation, and alt text. Pairs evaluate the school website or a popular app, noting three barriers each. They propose simple changes and vote on class priorities.

Prepare & details

What are common digital barriers for people with visual impairments?

Facilitation Tip: For Pairs Audit, require students to screenshot each barrier they find and paste it into a shared doc before proposing solutions.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Experiential Learning

⏱ 50 min·Small Groups

Group Prototype: Redesign an Interface

Small groups select a common app screen and redesign it paper-based for accessibility, adding features like high-contrast buttons and voice commands. They test prototypes on classmates for feedback. Refine and present improvements.

Prepare & details

Why is accessibility often treated as an afterthought in software development?

Facilitation Tip: In Group Prototype, assign roles (e.g., researcher, designer, presenter) to ensure every student contributes visibly.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Experiential Learning

⏱ 25 min·Whole Class

Whole Class Debate: Prioritize Accessibility

Pose scenarios on development trade-offs. Students vote and argue positions in a structured debate, citing user benefits. Summarize key insights on shared board.

Prepare & details

How does an accessible design benefit users who do not have a permanent disability?

Facilitation Tip: In Whole Class Debate, provide a simple scoring rubric so students evaluate arguments based on user impact, not just personal preference.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Teaching This Topic

Teach this topic through cycles of experience, reflection, and redesign. Avoid lecturing on WCAG guidelines; instead, let students discover standards by trying and failing to make interfaces usable. Research shows that empathy alone doesn’t transfer to design skills, so pair simulations with structured audits and iterative prototyping.

What to Expect

Successful learning looks like students identifying real barriers in websites, proposing inclusive fixes, and defending their choices with user-centered reasoning. Collaboration ensures diverse perspectives inform decisions.

Watch Out for These Misconceptions

Common Misconception

During Simulation Stations, watch for statements like 'This only matters for people who can't see.'

What to Teach Instead

Use the simulation reflections to redirect: ask students to recall how blurred vision made them rely on captions or how one-handed navigation forced them to rethink mouse-dependent tasks. Compare their notes in pairs to highlight universal benefits.

Common Misconception

During Group Prototype, watch for comments like 'Adding accessibility will slow us down.'

What to Teach Instead

Have groups compare their first draft to the revised version. Track time spent on alt text or color choices and contrast it with time saved from fewer user complaints in usability testing. Debrief as a class to quantify minimal effort versus broad impact.

Common Misconception

During Simulation Stations, watch for assumptions that accessibility is only about visual impairments.

What to Teach Instead

After the motor-skill station, prompt students to redesign a drag-and-drop task using keyboard-only controls. After the cognitive station, challenge them to simplify instructions without reducing content. Use their prototypes to map which barriers align with which disabilities.

Assessment Ideas

Quick Check

After Simulation Stations, display two screenshots of real websites. Ask students to identify one barrier per screenshot and write a one-sentence fix aligned with the principle they experienced (e.g., color contrast, captions). Collect responses anonymously to identify patterns.

Discussion Prompt

After Whole Class Debate, assign small groups to draft a class consensus on the top three accessibility priorities for a new school app. Each group presents one priority with a user scenario, and the class votes on the most compelling argument.

Peer Assessment

During Pairs Audit, have pairs submit a shared document listing three barriers and three fixes. The teacher reviews the documents to assess whether students correctly identified issues and proposed solutions aligned with WCAG basics (e.g., alt text, keyboard navigation).

Extensions & Scaffolding

• Challenge early finishers to redesign a complex dashboard (like a school portal) using only high-contrast colors and keyboard navigation.
• Scaffolding for struggling students: Provide a checklist of common barriers (e.g., missing alt text, poor color contrast) to guide their audits.
• Deeper exploration: Invite a guest speaker with lived experience of a disability to discuss how specific design choices affect their daily digital life.

Key Vocabulary

WCAG	Web Content Accessibility Guidelines are a set of international standards for making web content more accessible to people with disabilities. They provide a framework for developers to follow.
Alt Text	Alternative text is a descriptive phrase or sentence that conveys the content or function of an image. Screen readers read alt text aloud to visually impaired users.
Keyboard Navigation	The ability to operate all interactive elements of a website or application using only a keyboard, without a mouse. This is crucial for users who cannot use a mouse.
Color Contrast Ratio	The difference in luminance (brightness) between two colors. Sufficient contrast is essential for readability, especially for users with low vision or color blindness.
Perceivable	Information and user interface components must be presentable to users in ways they can perceive. This means users must be able to see, hear, and feel the content.