Accessibility & Inclusivity

Making a mountain out of a molehill. Designing an application accessible to seniors.

September 5, 2023 2:45 PM
Long Lecture
🇵🇱 Polish
Bratysława 2

About

I will share how I transformed a project aimed at adding a dark mode in the interface of an application for registering car entries in logistics parks into designing a solution accessible to seniors. The users of the application are security guards who work at security posts at night, opening and closing gates for cars. Initially, the most frequently reported problem was glare from the screen and problems with reading data in tables. During my research, I diagnosed a broader problem - the application needed to be adapted to senior users.

My talk will explore the fear and uncertainty experienced by users aged 60+ who are forced to navigate an increasingly digital world. I will address why they are often apprehensive about using applications, computers, and technology in general. I will also emphasize the importance of understanding the needs and problems faced by seniors in order to design effective solutions that cater to their unique requirements. Through empathy and skillful design of tools that seniors use at work, we - designers - can help them climb the "rocky hills" of technology.

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

From the recording

Talk in brief

A Polish-language case study, rendered here in English, about redesigning a security-desk application used in logistics parks. A request for dark mode exposed a broader accessibility challenge: guards rotate frequently, many are over 65, and some have limited confidence with computers. The designer combined established guidance with field visits to guard booths, where usability sessions revealed needs that the original ticket missed. High-contrast alerts also served communication with drivers, training and support mattered as much as screen design, and real work could revert to paper when systems failed. The project shows why accessible interfaces must be tested in their physical, social, and operational context rather than inferred from age alone.

Key takeaways

  1. 01

    Look beyond the literal interface request

    A complaint about glare at night led to a wider review of readability, confidence, training, and the needs of older guards.

    Watch from 4:00
  2. 02

    Design accessibility for everyone on the rotation

    The same workstation may be used by a student one day and a retired person the next, so the interface cannot depend on one age profile.

    Watch from 5:14
  3. 03

    Test inside the real guard-booth workflow

    Field sessions uncovered driver disputes, interruptions, system failures, and workarounds that a remote screen review would have missed.

    Watch from 12:12
  4. 04

    Treat confidence and support as usability factors

    Guards avoided unfamiliar settings because computer problems felt risky, making onboarding and dependable assistance part of adoption.

    Watch from 15:37
  5. 05

    Preserve the communicative role of urgent states

    Large red alerts were not only for guards; the screen was physically shown to frustrated drivers as evidence that entry was blocked.

    Watch from 29:08
Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

A dark-mode ticket concealed a broader inclusion problem

The original issue said that the bright interface reflected in guard-booth windows and dazzled staff at night. Further questions showed that the workforce changed frequently and included many retired people. The project therefore expanded from applying a dark palette to examining whether data, controls, alerts, and support made the system workable for people with very different computer experience.

Watch from 4:00

Established guidance was only the starting hypothesis

Research on dark interfaces and older users informed decisions about eye strain, contrast, and readability, while Material Design provided a component foundation compatible with the intended implementation. Those sources helped produce a credible prototype, but they could not describe the exact environment of a logistics gate. Field testing remained necessary to discover whether the design supported the job.

Watch from 6:34

The booth context changed the meaning of interface elements

When a registration number is missing, a barrier stays closed and a queue grows behind the vehicle. Drivers may assume the guard is refusing entry, while the guard must contact the destination company and keep the situation under control. Interface clarity matters inside this chain of pressure, conversation, and physical movement, not only as an isolated task on a screen.

Watch from 12:12

Fear of the computer shaped feature adoption

Some guards avoided settings because an unexpected change might leave them unable to restore the workstation during a shift. Calls to support sometimes concerned turning on a monitor or recovering a minimized window rather than the application itself. A usable redesign therefore needed onboarding, predictable behavior, and access to help, not merely cleaner controls.

Watch from 15:37

The warning color communicated beyond the primary user

The redesigned alert was initially visually restrained, but observation showed that guards sometimes rotated the monitor toward a driver to demonstrate why the gate could not open. A large red message was legible from a distance and helped defuse blame. The next iteration restored that visual force because the alert served both operational status and face-to-face communication.

Watch from 29:08
Explore WaysConf 2026