Coding · 2nd Year · Software Engineering and Community Impact · 3.º Período

Designing for Accessibility and Inclusion

Investigate the historical progression of accessibility in technology and how software engineering can promote social inclusion for marginalised groups.

TL;DR: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.

• NCCA Curriculum Specifications
• NCCA Junior Cycle Short Course in Coding, Strand 3: Coding in action
• NCCA Junior Cycle Short Course in Coding, Strand 3: Coding in action - Application design

About This Topic

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.

In the NCCA Junior Cycle Coding course, 'Application Design' requires students to consider the end-user. This unit challenges students to think beyond their own experience and design for marginalized groups. Students grasp this concept faster through structured discussion and peer explanation of the barriers they find in everyday apps when they try to use them under simulated constraints.

Key Questions

1. How has technology historically excluded certain groups of people?
2. What are the core principles of accessible software design?
3. How can coding empower marginalised communities?

Watch Out for These Misconceptions

Common Misconception

Accessibility is only for people with permanent disabilities.

What to Teach Instead

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.

Common Misconception

Making an app accessible is too difficult and expensive.

What to Teach Instead

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.

Active Learning Ideas

Simulation Game

The Accessibility Audit

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.

45 min·Pairs

Gallery Walk

Inclusive Innovations

Display different assistive technologies (e.g., high-contrast modes, voice-to-text, specialized controllers). Students rotate and discuss which user group each innovation supports.

30 min·Small Groups

Inquiry Circle

Designing for a Persona

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.

50 min·Small Groups

Frequently Asked Questions

What are the core principles of accessible software design?

The main principles are Perceivability (users can see or hear the info), Operability (users can navigate easily), Understandability (the UI is clear), and Robustness (it works on different devices and assistive tech).

How can coding empower marginalised communities?

Coding allows for the creation of bespoke tools that solve specific community problems. For example, apps that translate sign language into text or provide navigation for the visually impaired can significantly increase independence and social inclusion.

What is 'Universal Design'?

Universal Design is the concept of creating products and environments that are usable by all people, to the greatest extent possible, without the need for adaptation or specialized design.

How can active learning help students understand accessibility?

Empathy is the key to understanding accessibility. Active learning strategies, like 'empathy testing' where students simulate different impairments while using software, provide an immediate, emotional understanding of why accessible code matters. It shifts the topic from a 'checklist of rules' to a human-centered design challenge.