Something I've noticed repeatedly is how easily we equate the presence of technology with accessibility.

Someone has a smartphone, internet, email and the required app, so technically everything is available.

But can they reliably achieve the intended outcome?

For example, a calendar can be correctly installed and synchronised while still being effectively unusable to the person who needs the appointment information.

An online account can exist while authentication makes accessing it impractical.

A voice assistant can be installed while the person's actual circumstances make using it difficult.

I've started thinking about this as the difference between technical availability and functional availability.

The test I find more useful is:

Can the person reliably achieve the intended outcome in their actual environment?

It seems particularly relevant as governments and essential services continue moving more interactions online.

I'm interested in whether others working in disability, aged care, accessibility or community services see the same distinction.

I've been thinking about something I regularly see in everyday communication.

A person's phone works. Their email works. Their calendar works. Their internet works.

But an appointment might arrive by SMS, supporting information by email, changes through a portal, authentication through another account and reminders somewhere else.

Nothing is technically broken.

Yet the person still struggles to reliably achieve the outcome.

I've started describing this as Communication Fragmentation.

I think it's particularly relevant when helping older people, people with disability, or simply anyone managing a growing number of services and accounts.

Sometimes adding another app isn't the solution. Bringing the existing pieces together may be far more useful.

I'm interested in whether others are seeing the same thing in their own families or work.

I've been thinking about something I see repeatedly.

Every year we add:

another account

another password

another authentication method

another app

another online service

Individually they're manageable.

Collectively they become difficult to keep track of.

I'm starting to think this creates something like Communication Debt—hidden complexity that only becomes obvious when something changes or stops working.

Have you seen this happen with yourself, your parents, clients or colleagues?

I'm curious whether others have noticed the same pattern.

​

Something I've noticed over years of helping people with everyday communication is this:

Very few people actually care about the technology itself.

What they care about is confidence.

Will the phone work?

Will the authentication code arrive?

Will the appointment still be in the calendar?

Will someone be able to help if something changes?

The device is almost secondary.

The communication environment is what determines whether everyday life feels straightforward or stressful.

I'm starting to think we spend too much time talking about technology and not enough time talking about confidence.

Has anyone else noticed the same thing with family members, clients or even in their own life?

I've noticed a pattern through my work helping people navigate communication with modern services.

A lot of discussion focuses on teaching people more digital skills.

But I think there's another side to the problem.

Many everyday tasks now involve multiple organisations, accounts, passwords, authentication codes and devices.

The task itself hasn't become harder.

The communication environment has.

I've started asking a different question:

How do we make communication better match the person's existing skills instead of expecting them to constantly learn new systems?

Sometimes the solution isn't more training.

Sometimes it's simplifying the environment.

Curious whether others are seeing the same pattern in healthcare, disability, aged care or even with family members.

Something I've been thinking about from client work.

Most new technology doesn't just add a feature.

It also adds another dependency.

Another login.

Another recovery method.

Another authentication step.

Another cloud account.

Individually they're easy enough.

Collectively they become the reason people struggle years later when something changes.

I'm starting to think we spend too much time comparing products and not enough time comparing how many ongoing dependencies they introduce.

Has anyone else noticed this, either in IT, customer support or just managing technology for family members?

Something I've been noticing through my work.

People often describe technology as suddenly stopping.

But when we look back, the signs were usually there for a long time.

A new phone.

A forgotten password.

An old recovery email.

A software update.

A service provider change.

None of those things seem significant on their own.

Together, they slowly make a system less reliable until one day an everyday task becomes impossible.

Has anyone else found that the final failure is often just the point where the accumulated changes become visible?

I've been noticing something through my work.

When digital systems become more complicated, most discussion focuses on usability or security.

What I rarely hear discussed is participation.

Some people don't complain.

They don't contact support.

They don't write negative reviews.

They simply stop engaging.

They avoid changing providers.

They put off online tasks.

They ask someone else to do it.

I'm curious whether others have seen the same thing—in technology, healthcare, government or customer service.

Is "quiet withdrawal" an underestimated consequence of increasing digital complexity?

Hey everyone,

I recently spent a deep-dive session optimising a Samsung Galaxy S24 running TalkBack for a blind individual. While the S24 hardware is excellent, modern Android user interfaces (UIs) introduce specific friction points for Assistive Technology users.

We successfully stripped away the visual clutter, bypassed interaction traps, and streamlined the workflow to reduce cognitive load. If you or someone you support is setting up a modern Samsung device with the Android Accessibility Suite, here is the exact system-level optimisation blueprint based on what actually worked on the ground:

1. Eliminate Hidden Screen Takeovers (Samsung Calendar)

• The Problem: The native Samsung Calendar app frequently pushes notification overlays onto the screen. For a blind user, this creates immediate spatial confusion because an application has hijacked the screen layout without clear audio context, making it incredibly difficult to figure out how to dismiss it.
• The Fix: Go to Settings > Apps > Samsung Calendar > Notifications, and disable all General Notifications. This blocks the app from silently taking over the screen layout, while keeping your main Google Calendar completely accessible via virtual assistant voice.

2. How to Break a TalkBack "Element Trap" (The Two-Finger Tap)

• The Problem: TalkBack frequently gets stuck on a single UI element, demanding a double-press to interact with it. When this happens, it stops tracking where your finger actually is on the rest of the glass, making the phone feel completely frozen or unresponsive to single-finger exploration. I was not able to work out how it was getting stuck to an element. 
• The Fix: Do not reboot. Tap the screen with two fingers simultaneously. This native gesture forces TalkBack to release its focus lock on that single trapped element, instantly allowing you to scroll your finger around the rest of the screen to hear what's there and regain full navigation control.

3. Google Contacts vs. Samsung Contacts (Accessibility UI Layout)

• The Problem: In the native Samsung Contacts app, to use voice search, you have to navigate down the screen, click into the contacts search field, and then find the microphone icon tucked to the right. It requires too much manual tracing on the glass.
• The Fix: Swap to the Google Contacts app. The search field sits predictably at the very top of the screen, with the microphone voice-input icon immediately to the right. It requires significantly less physical tracking to execute a search.

4. Stop the "Robot Talk" Audio Clutter

• The Problem: TalkBack defaults to high verbosity, constantly reading out useless cosmetic screen data, structural layouts, and formatting hints that add unnecessary noise to the auditory feedback path.
• The Fix: Go to Settings > Accessibility > TalkBack > TalkBack Settings. Turn OFF "Speak Usage Hints" and OFF "Speak Text Formatting." This instantly cleans up the audio feedback path so the phone only states the vital text.

5. Gemini Voice Dialling Actually Works on the S24

• The Win: Historically, on older Samsung UIs or alternative devices, replacing the default assistant with Google Gemini meant losing the ability to make hands-free phone calls on behalf of the user. However, on the S24 running the latest Samsung UI, integrating Google Gemini works flawlessly for voice dialling out of the box. We coupled this with native Gemini camera tools for rapid, highly accurate scene intelligence and object description.

6. Standardise Navigation & Kill the Overlays

• The Layout: Switch the device layout back to traditional 3-button navigation (Recents | Home | Back) instead of gesture navigation. This provides static, predictable tactile anchors on the bottom of the glass.
• The Bloat: Turn off Samsung "Briefing" overlays and disable Digital Wellbeing tracking services in the background. This dramatically cuts down on accidental notification pop-ups that interrupt the screen reader experience.

Hopefully, this layout logic helps someone else optimise their device setup! Let me know if you’ve run into any other specific UI traps on modern Android versions.

Samsung S22 + Gemini can’t make phone calls, but Google Assistant still works (my workaround)

Spent a few hours troubleshooting this today with a quadriplegic client who needs completely hands-free phone calls.

Issue:

• Samsung S22 SM-S901
• Gemini enabled as the assistant
• Saying “Call Bob Smith” worked up to a point
• Gemini found the contact and displayed their name and number
• Asked, “Do you want to make the call?”
• After saying “Yes,” it failed with a generic error message

Things I tried:

• Switched from Samsung Phone to Google Phone
• Uninstalled and reinstalled Gemini
• Restarted the phone multiple times
• Checked permissions
• Tried initiating calls by voice and by tapping the displayed contact
• Same error every time

The solution:
I switched the default assistant back to Google Assistant, and it immediately worked. Voice commands such as:

“Hey Google, call Bob Smith”

worked perfectly.

My conclusion is that Gemini can understand the request and resolve the contact, but on this S22 it fails at the final step of actually executing the call. Google Assistant still has more reliable system integration for hands-free calling.

I suspect this may be a Samsung One UI update and Gemini integration bug rather than a permissions issue, especially since the exact same phone and contacts work immediately when reverting to Google Assistant.

Has anyone got the same phone and can test this error.

Has anyone else experienced this on an S22 or other Samsung devices? If so, did you find a fix, or are you also falling back to Google Assistant for reliable voice calling?