Making Space for Everyone: How Family Memory Works for All Abilities

In her late seventies, Margaret developed macular degeneration — the kind of gradual central vision loss that makes faces blur and fine print disappear but leaves peripheral vision mostly intact. She adapted by learning to look slightly sideways at things, a compensation that worked well enough in daily life. What it didn't work well for was her family's photo-sharing app. The images were there. The captions were there. She simply couldn't read any of it.

Her granddaughter eventually printed photos and brought them in person. Margaret was grateful. But she had stories she wanted to contribute — memories the photos triggered, context only she carried — and the app's input interface was built for someone with hands steadier than hers and eyes keener than hers had become. So the stories stayed in her head. When Margaret died two years later, they went with her.

This is not a story about bad intentions. It's a story about a tool built for a hypothetical user who didn't exist in this particular family — and the quiet, invisible cost that followed.

The myth of the default user#

Every design makes assumptions. When a team sits down to build a family memory platform, they have an imagined user in mind: able-bodied, fully sighted, with fine motor control sufficient for touchscreens and keyboards, English-reading, cognitively clear, probably between thirty and fifty years old.

This user doesn't represent most families, which contain grandparents with arthritis, grandparents with low vision, grandparents who've lived their whole lives in languages other than English. Families contain toddlers and teenagers with sensory processing differences, adults recovering from strokes, family members whose cognitive abilities have changed with age or illness.

The W3C Web Accessibility Initiative has documented extensively how web tools fail users who fall outside the imagined default: insufficient color contrast for people with low vision, interfaces that cannot be navigated by keyboard for people who cannot use a mouse, audio content without captions for deaf and hard-of-hearing users, complex menus that overwhelm users with cognitive disabilities. These aren't rare edge cases. The Centers for Disease Control and Prevention estimate that one in four American adults has some form of disability. Among adults over sixty-five — the population that holds most of a family's oldest and least-documented memories — the proportion is substantially higher.

What inclusive design actually means#

The term "accessible design" has an unfortunate connotation in the technology industry: a checklist, a compliance burden, a set of features added after the real product is built to satisfy a regulatory requirement. This misunderstands the concept entirely.

Inclusive design, as articulated by Microsoft's Inclusive Design team and the universal design movement in architecture and product development, starts from a different premise: designing for the person with the greatest constraint produces something better for everyone. The curb cut — originally designed so wheelchair users could cross streets — turned out to help parents with strollers, travelers with luggage, delivery workers with hand trucks, and anyone on a bicycle. It helped people who never thought of themselves as needing that kind of accommodation.

The same pattern holds in digital tools. Features built for accessibility tend to benefit users well beyond the group they were designed for:

• Captions, built for deaf and hard-of-hearing users, help anyone watching video in a noisy room or a quiet library.
• Voice input, built for users who cannot type due to motor limitations, helps parents whose hands are full, people driving, and anyone who thinks better aloud than in writing.
• Large, high-contrast text, built for people with low vision, helps anyone reading in poor light, on a small screen, or when fatigued.
• Simplified navigation, built for users with cognitive disabilities, reduces friction for anyone who is stressed, overwhelmed, or unfamiliar with the interface.

WebAIM, one of the leading research and advocacy organizations in web accessibility, has conducted surveys of web accessibility failures for over two decades. The most common failures are almost always things that affect everyone to some degree: low contrast text, missing form labels, unclear navigation, overly complex interactions. Fixing them for people with disabilities makes the tool better for everyone.

The specific reality of family members with disabilities#

What does this mean in the context of family memory, specifically? Consider the range of people a single extended family might contain:

Older adults are the most common group affected. Arthritis, one of the most prevalent conditions among people over sixty-five, makes fine motor tasks painful. A grandmother who would love to write down family recipes may simply not be able to type them. Voice input becomes not a convenience but a necessity. Macular degeneration, glaucoma, and other vision conditions make small text and image-heavy interfaces inaccessible without screen reader support, adjustable text sizes, and meaningful alt text.

Children with sensory or developmental differences face different barriers. An autistic child who experiences sensory overwhelm may find complex, animated interfaces genuinely distressing. A child with dyslexia may be able to tell stories verbally but find text-based input discouraging. A child with attention differences may navigate away before completing a contribution if the interface requires too many sequential steps. These children have things to share, memories that belong in the family record — but only if the tool meets them where they are.

Adults living with acquired disabilities — someone managing chronic pain, recovering from a stroke, living with MS, or navigating early-stage dementia — have dynamic accessibility needs that don't fit neatly into any single category. Their abilities may vary day to day. A tool that works for them on a good day may be completely inaccessible on a difficult one.

None of these people are peripheral to their families. Often they are at the center — the grandmother who holds the oldest stories, the child who sees everything with fresh eyes, the parent whose diagnosis has made family memory feel more urgent than ever.

Dignity and the right to participate#

There is a version of this conversation that stays purely practical: here are the features that make a tool more usable for more people. But the stakes are higher than usability.

A family member who cannot participate in the process of preserving family memory is, in a real sense, excluded from the family's shared identity. The family archive becomes a document of who was able to contribute, not who was present. The stories of the person who couldn't type, couldn't see the interface, couldn't navigate the menus, simply don't appear — not because they had nothing to say but because the tool didn't make space for them.

The National Council on Disability has documented how exclusion from digital tools translates to exclusion from civic and social life more broadly. Family memory tools are not civic infrastructure in the legal sense, but they are social infrastructure in a very practical one. The right to participate in one's family's story is not a technical matter. It's a matter of dignity.

Consent as accessibility#

Inclusive design in family memory also requires thinking carefully about consent — particularly for family members whose agency is limited or variable.

Young children cannot meaningfully consent to being documented. A family memory practice that photographs and records children from birth until adulthood, with no mechanism for those children to later review, correct, or remove their own history, treats documentation as an adult prerogative over a child's story. As children grow, they should increasingly have agency over what of their story exists in the family archive.

People living with dementia face a different challenge. Early in the disease process, they may be fully capable of contributing stories and consenting to documentation. Later, that capacity diminishes, sometimes gradually, sometimes in fluctuating ways. A family memory tool that treats consent as a one-time setup choice rather than an ongoing conversation will fail people whose capacity changes over time.

People with cognitive disabilities often rely on caregivers or family members to manage their digital presence. This creates a well-documented risk: someone else's judgment substitutes for theirs. Inclusive design in this context means making it as easy as possible for the person with the disability — not just their caregiver — to express preferences about their own participation.

Building from the foundation, not patching at the end#

The consistent finding from decades of accessibility research is that the cost of retrofitting accessibility onto an inaccessible tool is always higher — in time, in money, in quality — than building with accessibility as a foundation from the start.

The W3C Web Accessibility Initiative's documentation of the Web Content Accessibility Guidelines (WCAG) was designed precisely to give designers and developers a framework for building accessible from the beginning, not fixing it later. The principles — Perceivable, Operable, Understandable, Robust — apply not just to web pages but to any interface through which people interact with information.

For family memory tools, building from this foundation means treating accessibility not as a feature among features but as a non-negotiable architectural principle: every interaction must be possible through multiple modalities (voice, touch, keyboard), every piece of content must be accessible to people with visual, auditory, and cognitive differences, and every consent mechanism must be genuinely usable by the person whose consent it seeks.

Every voice belongs in the family record#

Families are not made of people who are all equally comfortable with technology, equally sighted, equally motile, equally cognitively consistent. They are made of grandparents and toddlers, people with arthritis and people recovering from surgery, people who communicate better in voice than in writing and people who process the world differently than the designers of most tools have imagined.

A family memory practice worth having is one that finds a way to include all of them — not as an accommodation added later, not as an edge case handled with a workaround, but as the actual design goal from the beginning.

Margaret's stories are gone. But the failure that lost them was a design failure, not an inevitable one. The choice to build tools that meet the full range of human ability is available at any moment — and the families that make it will have archives that are more complete, more honest, and more truly representative of who they actually are.