Making the internet more accesible for elderly users

The internet is filled with research on accessibility, but much of it focuses on broad topics like visual impairments and hearing loss. However, my experience helping elderly individuals with IT issues has shown me that many so-called "simple" interfaces can still be confusing for them. For instance, some elderly users don’t realize they can scroll on certain websites, while others struggle to understand expandable sections (accordions) that require an extra click to reveal more information. To explore these challenges, I conducted research with elderly users to understand their struggles with common interface elements. This article shares my findings and provides practical recommendations for designing websites that are more intuitive for seniors. How I went to work I designed a usability study focusing on interfaces used for scheduling appointments, including: Selecting an appointment date Selecting a date Selecting a time Entering an address For each type of interface, I selected several widely used design patterns and recreated them in Figma to maintain a consistent style. I then asked respondents (all aged 60 and older) to describe how the interface works and noted when they encountered difficulties. Finally, I asked them which interface they preferred. Key findings from interface testing Making an appointment Appointment pickers are commonly used by businesses like barbers and dentists. I tested two versions: a traditional monthly date picker and a weekly view with visible time slots. Monthly date picker Although this format is widely used, several respondents found it unclear. Many didn't immediately understand that the available time slots were tied to the selected date. Weekly date picker Respondents preferred a layout where all available time slots were immediately visible without extra clicks. Surprisingly, they also understood the "next" and "previous week" buttons. Unfortunately the second I haven't seen the second date picker much in components inside much used libraries. However, implementing this design at a larger scale presents challenges. If too many dates are displayed, readability suffers. If unavailable dates are removed, users might not realize they are skipping days. While this format is better for clarity, these pitfalls must be carefully managed. Selecting date I compared two common date picker styles: a traditional monthly calendar and a scroll-based picker, as seen on Apple devices. Monthly calander date picker Scroll-based date picker Despite the popularity of Apple products among respondents, the traditional monthly date picker was preferred. This suggests that even if users are familiar with a particular interface from their phones/tablets, it doesn’t necessarily mean they find it intuitive. Selecting time I tested four different time input methods: Up/down buttons time picker Analog clock time picker Dropdown time picker Slider time picker My initial assumption was that the analog clock would be the most intuitive since it mirrors real-world clocks. I also suspected the dropdown menu would be difficult since scrolling remains a challenge for many elderly users. The results were surprising. The up/down button selector was the most successful. While it requires more clicks to reach a desired time, the large text and simple interface made it easier to use than other options. Entering an address Address input fields often include auto-suggestions and real-time map updates. While this is generally helpful, I encountered a case where a respondent couldn’t find their home on the map, preventing them from placing an order on a website. Most respondents preferred auto-suggestions, as they made entering an address faster. However, it is crucial to include an option for manual entry in case the system fails. Having an extra button for manual entry can introduce confusion due to the additional choice, but it remains necessary to avoid accessibility issues. Given these factors, I recommend prioritizing manual address entry as the primary method. While auto-suggestions can enhance usability, they should never be the only option, as they do not always work reliably for all users. General recommendations Through my experience assisting elderly users with common IT problems, I’ve identified several recurring issues that developers should consider: Make buttons larger Many elderly users have unsteady hands, making small buttons difficult to click. Larger buttons improve usability and reduce frustration. Clearly indicate scrollable areas Many seniors do not instinctively scroll. If a form’s “Next” button is out of view, some users may not realize they need to scroll down to find it. Consider: Keeping critical buttons within the visible screen area. Using clear visual cues

Mar 16, 2025 - 15:10

Making the internet more accesible for elderly users

The internet is filled with research on accessibility, but much of it focuses on broad topics like visual impairments and hearing loss. However, my experience helping elderly individuals with IT issues has shown me that many so-called "simple" interfaces can still be confusing for them. For instance, some elderly users don’t realize they can scroll on certain websites, while others struggle to understand expandable sections (accordions) that require an extra click to reveal more information.

To explore these challenges, I conducted research with elderly users to understand their struggles with common interface elements. This article shares my findings and provides practical recommendations for designing websites that are more intuitive for seniors.

How I went to work

I designed a usability study focusing on interfaces used for scheduling appointments, including:

Selecting an appointment date
Selecting a date
Selecting a time
Entering an address

For each type of interface, I selected several widely used design patterns and recreated them in Figma to maintain a consistent style. I then asked respondents (all aged 60 and older) to describe how the interface works and noted when they encountered difficulties. Finally, I asked them which interface they preferred.

Key findings from interface testing

Making an appointment

Appointment pickers are commonly used by businesses like barbers and dentists. I tested two versions: a traditional monthly date picker and a weekly view with visible time slots.

Monthly date picker

Although this format is widely used, several respondents found it unclear. Many didn't immediately understand that the available time slots were tied to the selected date.

Weekly date picker

Respondents preferred a layout where all available time slots were immediately visible without extra clicks. Surprisingly, they also understood the "next" and "previous week" buttons.

Unfortunately the second I haven't seen the second date picker much in components inside much used libraries.

However, implementing this design at a larger scale presents challenges. If too many dates are displayed, readability suffers. If unavailable dates are removed, users might not realize they are skipping days. While this format is better for clarity, these pitfalls must be carefully managed.

Selecting date

I compared two common date picker styles: a traditional monthly calendar and a scroll-based picker, as seen on Apple devices.

Monthly calander date picker

Scroll-based date picker

Despite the popularity of Apple products among respondents, the traditional monthly date picker was preferred. This suggests that even if users are familiar with a particular interface from their phones/tablets, it doesn’t necessarily mean they find it intuitive.

Selecting time

I tested four different time input methods:

Up/down buttons time picker

Analog clock time picker

Dropdown time picker

Slider time picker

My initial assumption was that the analog clock would be the most intuitive since it mirrors real-world clocks. I also suspected the dropdown menu would be difficult since scrolling remains a challenge for many elderly users.

The results were surprising. The up/down button selector was the most successful. While it requires more clicks to reach a desired time, the large text and simple interface made it easier to use than other options.

Entering an address

Address input fields often include auto-suggestions and real-time map updates. While this is generally helpful, I encountered a case where a respondent couldn’t find their home on the map, preventing them from placing an order on a website.

Most respondents preferred auto-suggestions, as they made entering an address faster. However, it is crucial to include an option for manual entry in case the system fails. Having an extra button for manual entry can introduce confusion due to the additional choice, but it remains necessary to avoid accessibility issues.

Given these factors, I recommend prioritizing manual address entry as the primary method. While auto-suggestions can enhance usability, they should never be the only option, as they do not always work reliably for all users.

General recommendations

Through my experience assisting elderly users with common IT problems, I’ve identified several recurring issues that developers should consider:

Make buttons larger

Many elderly users have unsteady hands, making small buttons difficult to click. Larger buttons improve usability and reduce frustration.

Clearly indicate scrollable areas

Many seniors do not instinctively scroll. If a form’s “Next” button is out of view, some users may not realize they need to scroll down to find it. Consider:

Keeping critical buttons within the visible screen area.
Using clear visual cues (such as arrows or partial cut-offs) to indicate that more content exists below.

Retain scrollbars

Some users still use the scrollbar itself rather than a mouse wheel or trackpad gestures. So don't remove scrollbars and scrollbar buttons for aesthetic reasons.

Always provide a back button

Although browsers have built-in back buttons, many elderly users don’t recognize them. Providing an explicit “Back” button within your interface ensures they can navigate with confidence.

Minimize memory load

Short-term memory declines with age. If a form spans multiple pages, pre-fill previously entered information so users don’t have to remember what they entered on a previous screen.

Use larger text

While accessibility standards allow users to zoom in, many seniors don’t know how to do this. Designing with a slightly larger font size from the outset improves readability without requiring extra user effort.

Final thoughts

Thank you for reading! This is my first post, so I appreciate your feedback. My goal is to share insights that many full-stack developers might not be aware of. Accessibility should go beyond standard guidelines to include elderly users.

With more government services moving online, digital literacy is no longer optional. We must ensure that the internet remains accessible to everyone, including seniors who may not have family members to assist them. I hope this article inspires developers to create more user-friendly experiences for elderly users!

If you have any thoughts or experiences on this topic, feel free to share!