Some businesses (clinics, insurance, funeral services, associations, neighbourhood shops) have a considerable share, sometimes the majority, of customers over sixty. And yet many of those websites get designed with the same visual criteria as a startup aimed at thirty-somethings: small type, subtle contrast, menus that only open with unintuitive gestures. The result is a website that is attractive to whoever designed it and frustrating for whoever needs it most.
Why "designing for older adults" does not mean making an ugly website
There is a mistaken idea that adapting a website for older people means huge letters, garish colours and an outdated look. In reality, the adjustments that help the most are almost invisible aesthetically: a bit more font size, a bit more contrast, slightly bigger buttons, fewer steps to complete an action. None of these adjustments make a website look "old"; in fact, many of them line up exactly with the good accessibility practices that benefit every user, regardless of age.
Eyesight changes with age, and design needs to account for it
Past a certain age it is common to experience reduced visual acuity, more sensitivity to glare, and more difficulty distinguishing colours with low contrast between them. In practical terms, this translates into very specific needs: body text of at least 18 pixels (better still if size can be easily adjusted), high contrast between text and background, and avoiding colour combinations that rely solely on hue difference without a difference in brightness, like certain reds against certain greens.
Motor precision changes too, and it directly affects buttons
It is not just about eyesight: precision with a mouse or a finger on touchscreens also tends to decline with age, due to tremor or reduced fine motor skill. Buttons and links that are too small or too close together generate frequent misclicks, a silent source of frustration that pushes people to abandon the website without being able to explain exactly why it felt so hard. A comfortable minimum button size (around 44 by 44 pixels, the same reference used in accessibility guidance for all users) and enough spacing between clickable elements solves much of the problem.
Vocabulary and jargon: another invisible barrier
Terms like "checkout," "onboarding" or "dashboard," common in the vocabulary of people who work in digital, can be completely opaque to someone less familiar with the internet. This is not about dumbing down the language, but about using clear words that anyone recognises without effort: "complete your order" instead of "checkout," "your account" instead of "dashboard." That clarity helps everyone, but it is decisive for someone who has not internalised that technical vocabulary.
Forms: fewer steps, more confirmation, less time pressure
Long forms or processes with a time limit (like a session that expires within a few minutes) generate disproportionate anxiety in users less accustomed to moving quickly online. Reducing the number of fields, clearly confirming every completed action ("Your appointment has been booked for Thursday at 10:00") and avoiding overly tight session times makes the process feel manageable instead of threatening.
The phone is still the safety net
However well-designed a website is, there will always be a share of older customers who prefer to finish the process by phone, especially for important or financial decisions. Displaying a visible, easy-to-find phone number, instead of hiding it at the bottom of a contact page, is not a failure of digital design: it is recognising that, for some people, trust still runs through talking to someone.
How to genuinely validate whether your website works for this audience
The most honest validation does not come from a technical checklist, but from sitting someone over sixty (ideally someone similar to your real customer, not a relative used to helping you with technology) in front of your website and asking them to complete a specific task without help. The points where they hesitate, ask for help, or simply give up are exactly the points that need fixing first.
Browser zoom: why it should never be blocked
Some websites, for purely aesthetic reasons, block the user's ability to zoom the browser or touchscreen. For someone with visual difficulties, this restriction removes the one adaptation tool they had available, turning a minor issue into a total access barrier. Always allowing native browser zoom is one of the cheapest, highest-impact interventions there is for this audience.
Icons with no text: a common trap for those unfamiliar with digital symbols
A magnifying glass icon for search, or three horizontal lines for the menu, are symbols most younger users recognise automatically through sheer repeated exposure over the years, but that can mean nothing to someone less familiar with the internet's visual conventions. Pairing the most important icons with a short word of text ("Search," "Menu") removes this ambiguity at almost no visual cost.
Patience with reaction times: not penalising slowness with aggressive timeouts
Some interactions (menus that close automatically if the mouse moves away, confirmation messages that disappear after a few seconds) assume a reaction speed not every user has. Giving more time before these elements automatically close or disappear prevents someone with slower reactions from being left literally unable to complete an action they were about to finish.
Step-by-step instructions versus interfaces that assume prior knowledge
Many interfaces assume the user already knows how to interpret certain visual patterns (a three-dot icon for more options, a swipe gesture to reveal hidden actions). For users less familiar with these conventions, brief, visible instructions the first time a feature is used, instead of assuming the pattern will be understood on its own, make a real difference between successfully completing a task or abandoning it out of confusion.
Human contact as part of the design, not as its failure
It is tempting to think a perfectly designed website for this audience should never need human help, but that expectation is unrealistic and, for some businesses, not even desirable. Designing with the assumption that some users will prefer to complete the process with phone support, and building that option in as a path just as valid and well signposted as the digital one, is a form of inclusive design as legitimate as any purely visual adjustment.
The value of testing with real relatives, limitations and all
Although testing with real customers is ideal, testing with an older relative, while being aware they may be more forgiving than a stranger, still provides valuable information, better than testing with nobody from that profile at all. What matters is not mistaking that informal test for definitive validation, and supplementing it as much as possible with at least one case outside the close circle.
Frequently asked questions
Does designing for older adults hurt the experience for younger users?
No, almost every adjustment (better contrast, bigger buttons, clearer language) improves the experience for any user, not just older ones. It is one of the few accessibility improvements that literally benefit everyone with no cost to other profiles.
Do I need a separate version of my website for older users?
Maintaining two separate versions is usually neither necessary nor advisable, since it doubles the maintenance burden. It is better to build these criteria into the single design of the website, benefiting all visitors equally.
What font size is recommended for an older audience?
As a reference, body text of at least 18 pixels, with the ability for the user to increase the size from their own browser without the design breaking, covers the needs of most of this audience well.
Are multi-step forms always bad for this audience?
Not necessarily, if each step is simple and clearly confirmed. The problematic combination is many fields per screen, little progress confirmation and tight time limits, which together generate most of the frustration.
How do I test my website with older users if I do not know anyone in that profile?
You can arrange short sessions with real customers willing to help in exchange for a small token of appreciation, or turn to user research services that provide specific profiles. Even two or three informal tests provide more insight than none at all.
Should the contact phone number appear on every page?
Ideally yes, or at least in a consistently easy-to-find place (header or footer), especially for businesses where part of the customer base prefers to resolve doubts by talking to someone before deciding.
Why do some websites block zoom, and should mine?
Some do it for aesthetic reasons or to control how the design looks at all times. It is not advisable: blocking zoom removes an essential accessibility tool for many users, not just older people, with no real benefit in return.
Are icons with no text always an accessibility problem?
Not all of them, but the less universal ones (anything beyond the now widely recognised magnifying glass or hamburger menu) should be paired with a text label to avoid ambiguity, especially for important actions on the site.
Should my interfaces include explicit instructions for common visual patterns?
For important features, yes, especially the first time a user encounters a pattern that assumes prior knowledge (gestures, menu icons). A brief, visible instruction reduces confusion without needing to redesign the interface.
Is it a design failure if a customer needs phone support to complete an online process?
No, it is simply acknowledging that some users prefer that route. Building in the phone option as a path just as valid and well signposted is a legitimate form of inclusive design.
Is it useful to test my website with an older relative instead of a real customer?
It provides valuable information, with the caveat that a relative may be more forgiving than a stranger. It is better than testing with nobody from that profile, but it is worth supplementing with at least one case outside the close circle.