Ofcom’s 2024 Online Nation report put a number to something most product teams already suspect but rarely act on: the over-55 demographic is one of the fastest-growing online cohorts in the UK. Not just growing. Growing fast. And yet, if you spend an afternoon watching someone in that age group try to use a typical SaaS product or a government-adjacent web app, you will feel genuine embarrassment at the assumptions baked into our interfaces. I’ve sat in enough usability sessions to know that the gap between what designers think older users can handle and what actually happens on screen is enormous.
This isn’t an accessibility checkbox article. It’s about the specific, recurring design decisions that make products hostile to people over 55, and what switching those decisions actually looks like in practice. The fix is almost never a separate “accessibility mode”. It’s just better design.
Why the over-55 audience is not who you think it is
The lazy mental model of an older user is someone confused by technology. That model is outdated and statistically wrong. Many people in the 55-75 bracket have been using the internet since the late 1990s. They have more disposable income than younger demographics, they shop online, they bank digitally, they stream. According to Ofcom’s internet use research, broadband penetration among over-65s in the UK has risen significantly year on year. These are not digital novices. They are experienced users dealing with interfaces built by people who did not design with them in mind.
The actual challenges are specific. Contrast sensitivity changes with age. Motor precision decreases. Reading speed slows when type is small or poorly spaced. Working memory means multi-step flows with no persistent progress information are genuinely harder to complete. None of these things mean someone is bad at technology. They mean the technology is bad at accommodating normal human variation.
The contrast and type size failures that are everywhere
Grey text on a white background is the single most common UI failure I see when looking at products aimed at a general UK audience. Designers use it because it looks refined. WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text. The trendy light-grey placeholder text in form fields routinely fails this. The secondary text on pricing pages fails this. The fine print on checkout screens absolutely fails this.
Type size is the other obvious one. A base font size of 14px or 15px might render acceptably on a 27-inch monitor at your desk. On a tablet held at arm’s length by someone whose near vision has shifted, it is punishment. Sixteen pixels should be the floor. Eighteen is more honest for body copy. Line height below 1.5 compounds the problem by collapsing the space between lines that lets the eye track correctly.
If you’ve been reading my earlier piece on choosing and pairing system fonts for the web, you’ll know that system fonts carry genuine legibility advantages at body size, particularly because they’ve been hinted and rendered for the OS they live on. That advantage matters more for older users than it does for anyone else.
Touch targets and motor precision
A 24px icon button that expands a menu is fine when you’re 29 and have the fine motor control of someone who grew up texting on a glass screen. It’s a genuine barrier when your hands are less precise. Apple’s Human Interface Guidelines recommend a minimum touch target of 44 by 44 points. Google’s Material Design says 48 by 48dp. Most production UIs I audit for clients are hitting 32 by 32 on interactive elements, sometimes less.
The fix is not complicated. Add padding. Use larger hit areas than the visible icon. Space interactive elements so that missing one doesn’t accidentally trigger another. These are also excellent improvements for mobile users on a bumpy train, so they help everyone. Good accessibility decisions usually do.
Related to this: hover states that only appear on desktop are not a navigation strategy. Dropdown menus that require hovering and then moving precisely into a sub-menu without the menu disappearing are a known usability failure for everyone, but disproportionately so for users with slower or less precise cursor movement. The solution is click-to-open behaviour or a transition delay on the menu close.
Cognitive load and the multi-step flow problem
The pattern I see causing the most drop-off with older UK users in usability research is multi-step flows with no persistent progress indicator and no ability to go back without losing state. Checkout flows. Application forms. Account setup wizards. The assumption is that a user will hold the full mental model of where they are in the process. That assumption is wrong for many users, and increasingly wrong as the complexity of the task increases.
Persistent breadcrumbs on long forms. Clear step indicators that say “Step 3 of 5”. Save and return later functionality for longer forms. Autofill that actually works correctly with UK address formats. These are table stakes that many products have not implemented.
Error messages deserve their own mention. Generic messages like “An error occurred” or “Invalid input” with a red border and no further context are genuinely useless. Precise errors that say “Your sort code should be six digits with no spaces” or “Your date of birth should be in DD/MM/YYYY format” are what accessibility looks like in practice.
The icon-only interface trap
Icon-only navigation has been creeping into UK product design for years. It looks clean in Figma mockups at 100% zoom. It is confusing in practice for a significant portion of users. My piece on how product teams are getting their icon systems wrong covers this at length, but the short version is: icons without labels are only clear when the iconography is universal and learnt. Most product icons are neither. Older users who didn’t grow up with a particular design language’s conventions find ambiguous icons significantly harder to decode. Add labels. Combine the icon with text. It adds a few pixels of height to your nav and it eliminates a major source of confusion.
Designing for older users UK accessibility in real product decisions
The design decisions that actually fix these issues are not a separate track from good design. They’re the same decisions. High contrast ratios look more professional, not less. Larger text with good line height reads better for everyone. Clear error messages reduce support tickets. Persistent progress indicators reduce abandonment. These are all wins on metrics that product teams already care about.
If your team hasn’t done usability testing with participants over 55, do it. Recruit through local community organisations, Age UK, or digital inclusion programmes. Watch what happens. I guarantee you will find at least three things to fix before the session ends, and you will fix them faster than any other research you’ve done, because the problems are visible and the solutions are concrete.
One practical first step: run your existing UI through a contrast checker (there are browser extensions for this) and sort the failures by page priority. Fix the worst offenders on your homepage and primary conversion flows first. That alone will move your accessibility score and your conversion numbers simultaneously.
The broader point is that designing for older users in the UK isn’t a niche concern or an edge case. It’s designing for a large, growing, and financially significant audience that is currently being failed by most of the interfaces they encounter. Fix the contrast. Fix the type size. Fix the touch targets. Fix the error messages. Then actually test with the people you’re designing for. The rest follows from there.