age-inclusive-design
Skill5 starsChanged 9 months agoMITView on GitHub
Design for users of all ages. Use when user asks to 'make accessible for older adults', 'improve age-inclusive design', 'help elderly users', 'reduce age-related friction', 'design for all ages', 'age-friendly interface'.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- llms-full.txtllms.txt
- llms.txtllms.txt
- accessibilitySkill
- cognitive-accessibilitySkill
- conflict-de-escalationSkill
- cultural-sensitivitySkill
- depression-sensitive-contentSkill
- empathetic-communicationSkill
- neurodiversity-aware-designSkill
- supportive-conversationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
32 rules. About 0 are common, 32 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈32
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Use this skill when:
- Distinctive: line 67
Use minimum 16px font for body text
- Distinctive: line 68
Ensure 4.5:1 contrast ratio (WCAG AA)
- Distinctive: line 71
Use simple, familiar language
- Distinctive: line 76
Ask about preferred font sizes
- Distinctive: line 78
Ask about preferred level of assistance
- Distinctive: line 82
Never assume all older adults are the same
- Distinctive: line 83
Never use age stereotypes (e.g., "elderly don't use tech")
- Distinctive: line 84
Never make interactions time-sensitive without warning
- Distinctive: line 85
Never hide important information in small text
- Distinctive: line 86
Never assume low tech literacy (many seniors are tech-savvy)
- Distinctive: line 96
Safety boundaries apply: Do not make medical or clinical claims about age-related conditions.
- Distinctive: line 109
Use sans-serif fonts (easier to read)
- Distinctive: line 110
Avoid decorative or script fonts
- Distinctive: line 111
Use adequate line spacing (1.5x)
- Distinctive: line 112
Use adequate letter spacing
- Distinctive: line 118
Ensure sufficient contrast without being harsh
- Distinctive: line 128
Avoid edges and corners (harder to tap)
- Distinctive: line 129
Place important actions in center
- Distinctive: line 130
Avoid requiring precise taps
- Distinctive: line 144
Don't require memory of previous steps
- Distinctive: line 153
Avoid CAPTCHA if possible (or provide audio option)
- Distinctive: line 158
Don't use technical jargon
- Distinctive: line 164
Use simple, direct language
- Distinctive: line 165
Avoid jargon and slang
- Distinctive: line 171
Use clear images that support content
- Distinctive: line 173
Avoid text in images
- Distinctive: line 179
Avoid time limits where possible
- Distinctive: line 180
If required, warn clearly
- Distinctive: line 189
Ask confirmation for important actions
- Distinctive: line 191
Don't require precise input
- Distinctive: line 307
All older users are the same
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Age-Inclusive Design
Purpose
This skill helps create digital experiences that work well for users of all ages. It addresses age-related changes in vision, motor control, cognition, and technology comfort to reduce friction and improve accessibility for older and younger users alike. Based on ISO 25556:2025 (Ageing-inclusive digital economy) and NIST usability guidelines.
When to Use
Use this skill when:
- Designing for older adults (65+)
- Creating multi-generational products
- Improving accessibility for elderly users
- Reducing age-related friction in interfaces
- Making content accessible across age groups
- Addressing usability concerns for seniors
Age-Related Changes to Consider
Vision Changes
- Reduced visual acuity
- Need for larger text
- Reduced contrast sensitivity
- Difficulty focusing on close objects
- Increased sensitivity to glare
- Changes in color perception
Motor Changes
- Reduced fine motor control
- Tremors or shaky hands
- Reduced grip strength
- Slower response times
- Difficulty with precise movements
Cognitive Changes
- Slower processing speed
- Reduced working memory
- Difficulty with new interfaces
- May prefer familiar patterns
- May need more time for decisions
Technology Comfort
- May be less familiar with technology
- May lack confidence with new interfaces
- May prefer step-by-step guidance
- May be wary of online security
Boundaries
Always
- Use minimum 16px font for body text
- Ensure 4.5:1 contrast ratio (WCAG AA)
- Make click/touch targets minimum 44x44px
- Provide clear, immediate feedback
- Use simple, familiar language
- Offer customization options
Ask First
- Ask about preferred font sizes
- Confirm before auto-completing actions
- Ask about preferred level of assistance
Never
- Never assume all older adults are the same
- Never use age stereotypes (e.g., "elderly don't use tech")
- Never make interactions time-sensitive without warning
- Never hide important information in small text
- Never assume low tech literacy (many seniors are tech-savvy)
Principles
This skill is grounded in the Humanity4AI core principles and the following skill-specific principles:
- Age is not a deficit. Design guidance must treat older and younger users as capable individuals with different interaction preferences, not as impaired users.
- Context determines accessibility. Age-related changes vary widely between individuals. Recommendations must be framed as considerations, not absolute requirements.
- Explicit uncertainty over false certainty. Acknowledge when a recommendation may not apply to all users in a given age group.
- Inclusive design benefits everyone. Improvements for older adults (larger touch targets, clearer language, reduced cognitive load) improve usability for all users.
- Safety boundaries apply. Do not make medical or clinical claims about age-related conditions.
Design Guidelines
Typography
Font Size
- Body text: minimum 16px (18-20px recommended)
- Headings: 24px+ for H1, 20px+ for H2
- Provide user option to increase size
Font Choices
- Use sans-serif fonts (easier to read)
- Avoid decorative or script fonts
- Use adequate line spacing (1.5x)
- Use adequate letter spacing
Contrast
- 4.5:1 minimum for normal text (WCAG AA)
- 3:1 for large text (WCAG AA)
- 7:1 for AAA compliance
- Ensure sufficient contrast without being harsh
Touch Targets
Minimum Size
- 44x44px minimum (WCAG)
- 48x48px recommended for older users
- Space between targets: 8px minimum
Placement
- Avoid edges and corners (harder to tap)
- Place important actions in center
- Avoid requiring precise taps
Navigation
Clear Navigation
- Consistent placement across pages
- Clear, descriptive labels
- Breadcrumb trails for orientation
- Skip links for screen readers
Process Steps
- Break complex tasks into steps
- Show progress indicators
- Allow saving progress
- Don't require memory of previous steps
Forms
Input Design
- Clear labels above fields
- Show all required fields
- Provide inline validation
- Use real-time feedback
- Avoid CAPTCHA if possible (or provide audio option)
Error Handling
- Clear error messages
- Suggest corrections
- Don't use technical jargon
- Allow easy correction
Content
Writing for All Ages
- Use simple, direct language
- Avoid jargon and slang
- Define technical terms
- Use active voice
- Short paragraphs (3-4 sentences max)
Visual Content
- Use clear images that support content
- Provide alt text for all images
- Avoid text in images
- Use sufficient contrast
Interaction Design
Time Limits
- Avoid time limits where possible
- If required, warn clearly
- Allow extension of time limits
Feedback
- Immediate feedback for actions
- Clear confirmation of completed actions
- Status updates for long processes
Error Prevention
- Ask confirmation for important actions
- Provide undo options
- Don't require precise input
Instructions
Step 1: Audit Current State
Review the design for:
- Font sizes (minimum 16px body)
- Touch target sizes (minimum 44x44px)
- Contrast ratios (4.5:1 minimum)
- Navigation complexity
- Form design
- Content readability
- Error handling
Step 2: Identify Issues
Categorize findings:
- Critical: Barriers preventing use
- High: Significant friction
- Medium: Minor inconvenience
- Low: Enhancement opportunity
Step 3: Prioritize Fixes
Address issues in order:
- Critical barriers first
- Then high friction
- Then medium/low improvements
Step 4: Implement Changes
For each issue:
- Identify the problem
- Provide specific solution
- Include code/examples where relevant
Examples
Example 1: Font Size
Input: Body text is 12px
Issue: Too small for many older users
Solution: Increase to 18px minimum
body {
font-size: 18px; /* Was 12px */
line-height: 1.6;
}Example 2: Touch Targets
Input: Small buttons that are close together
Issue: Hard to tap accurately with reduced motor control
Solution: Increase size and spacing
.button {
min-height: 48px;
min-width: 48px;
margin: 8px;
padding: 12px 24px;
}Example 3: Navigation
Input: Complex navigation with many options
Issue: Overwhelming, hard to find items
Solution: Simplify and organize
- Use clear categories
- Limit top-level items to 7
- Use familiar terminology
- Add search
Example 4: Forms
Input: Form with no clear labels, error messages in technical language
Issue: Confusing, frustrating to complete
Solution: Clear labels and helpful errors
- Labels above fields
- "Email address" not "Email"
- Error: "Please enter a valid email" not "Invalid value"
What Not to Do
Avoid
- Tiny text (under 16px)
- Low contrast (gray on white)
- Small, close touch targets
- Time-limited interactions
- Complex navigation
- Technical jargon
- Assuming tech illiteracy
Don't Assume
- All older users are the same
- Older users can't learn new things
- Younger users don't need accessibility
- Technology comfort is based on age alone
Additional Resources
- references/standards.md - ISO 25556:2025, WCAG guidelines
- references/patterns.md - Age-inclusive design patterns
- references/stereotypes.md - Age stereotypes to avoid
- references/font-guidelines.md - Typography guidelines
- references/interaction.md - Interaction design
- references/checklist.md - Implementation checklist
- references/examples.md - Good and bad examples
Script Usage
This skill includes validation scripts:
- audit_assumptions.py — Check for age-related assumptions
- detect_stereotypes.py — Detect age stereotypes
- analyze_clarity.py — Analyze font and readability
- validate_language.py — Validate age-friendly language
# Audit assumptions
# Detect stereotypesThis skill helps create age-inclusive digital experiences.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

