FIT5152 Chap.4 Accessibility and Inclusive Design
Accessibility and Inclusive Design
Week 4 widens the idea of who a design must serve. The seminar opens with the scale of the issue, around one in six Australians living with disability, and with Microsoft’s inclusive design principles: recognise exclusion, learn from diversity, and solve for one person in a way that extends to many.
Exclusion is treated as a mismatch between a design and a human ability, which can be permanent, temporary or caused by the situation. The seminar also separates inclusive design into usability, inclusivity through internationalisation and localisation, and accessibility, which lowers barriers linked to disability.
The core of the week is the Web Content Accessibility Guidelines.
Their four principles, perceivable, operable, understandable and robust, each come with a key question you can put to a screen, and the guidelines nest from principles to guidelines to testable success criteria with A, AA and AAA conformance levels.
The chapter turns these into concrete techniques with numbers, such as limits on flashing content and minimum touch-target sizes, and contrasts universal design with optional accessibility features. It closes with assistive technologies, from screen readers to switch scanning, and with the limits of voice interfaces for blind users.
Submission 2 requires a WCAG principle on every low-fidelity screen and a storyboard that shows an accessibility issue.
What this chapter covers
- 01
Inclusive design principles
- 02
Permanent, temporary and situational exclusion
- 03
WCAG principles and key questions
- 04
Guidelines, success criteria and conformance levels
- 05
Techniques and thresholds for accessible screens
- 06
Universal design and accessibility features
- 07
Assistive technologies and voice interfaces
Worked example · free
Writing a WCAG annotation for a medication-reminder screen
- 1Principle: perceivable, because the missed-dose state is carried by colour alone.
- 1Excluded ability: people with colour blindness or low vision, permanently, and anyone reading the phone in bright sunlight, situationally.
- 1Fix: add the word “Missed” and an icon beside the dot, so the state survives without colour and can be read by a screen reader.
Key terms
- Inclusive Design
- A design methodology that includes, and learns from, the full spread of human differences.
- Situational Impairment
- A reduced ability caused by the context of use, such as glare, noise or having one hand occupied.
- Success Criterion
- A testable requirement in WCAG that sits beneath a guideline and determines conformance.
- Universal Design
- A single default design that everyone uses and that aims to suit the broadest range of abilities.
- Accessibility Feature
- An optional addition that addresses a specific exclusion and lets users personalise the defaults.
- Switch Scanning
- An input method in which a highlight moves across the screen and the user selects with a single switch.
Accessibility and Inclusive Design FAQ
What are the four WCAG principles?
Perceivable, operable, understandable and robust. Each asks a question of the design: can users detect the content, carry out the interactions, interpret what they perceive, and can technologies process the interface correctly?
Which conformance level should a website aim for?
The seminar describes A as the minimum core, AA as covering more disability barriers and AAA as advanced, and suggests A or AA as a sensible goal for most sites.
Is a slow internet connection an accessibility issue?
Not in the seminar’s framing. Missing connectivity, unaffordable purchases, damaged devices or missing functionality are real problems, but they are not accessibility issues linked to human ability.
What touch-target size does the unit recommend?
The seminar notes that Apple, Google and Microsoft recommend a minimum of about 40 to 50 device-independent pixels, roughly 7 to 10 millimetres, with padding to enlarge small targets.
Assessment move
Start by memorising the four WCAG key questions, because they turn an abstract standard into a quick test. Open three apps and, for each, find one element that helps and one that hinders under perceivable, operable and understandable, naming the excluded user each time.
Then build a small table of the numbers from this week, including flash limits, target sizes and reading level, and quiz yourself until you can recall them without the slides. Practise the exclusion spectrum by writing a permanent, a temporary and a situational example for seeing, hearing and touch.
Finally, sketch one storyboard frame that shows a persona meeting an accessibility barrier, because Submission 2 asks for exactly that and it is easier to rehearse on paper than under deadline pressure.
Working through Accessibility and Inclusive Design in FIT5152? Sia is AskSia’s AI Information Technology tutor — ask any FIT5152 Accessibility and Inclusive Design question and get a clear, step-by-step explanation grounded in how FIT5152 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
