Insights

How I used a smart home to help with accessibility

Case study ·

This is a recent case study from a household I visited on site. I am not naming the family. A daughter asked what we could do to help her mam use the technology already in the house — especially whether smart services could be tied together so everyday jobs were less of a struggle.

The install is new. We have agreed to keep it simple for now, and I am waiting for proper feedback once they have lived with it. What follows is what we found, what we ruled out, and what we actually put in.

Start on site, not with a shopping list

I booked an initial consultation at the home. The point of that visit was not to sell a stack of gadgets. It was to understand the requirements, see what was already there, and watch how the house was actually used.

The person we were helping has difficulty seeing. That was especially obvious with a new smart TV: more buttons, more on-screen options, and a remote that assumes you can pick out small labels at a glance.

The family had already tried a universal big-button remote. It was not reliable enough, so they had gone back to the standard remote — which brought them full circle to the original problem.

The two jobs that actually mattered

Two issues came up again and again.

Getting stuck on the TV

The biggest day-to-day frustration was not “turning the television on.” It was opening streaming services such as Netflix and Disney+, then not being able to get back to the ordinary live channels. When that happened, she had to wait until someone came over to put it right. That is a loss of independence, not a minor annoyance.

Knowing who is calling

They were also having trouble identifying callers. Call screening had been tried. It did not work well enough for this household. The daughter wanted the phone to announce who was ringing so her mam could decide whether to answer — particularly with unknown numbers, where picking up blindly is a real risk.

If those announcements could sit inside a smart system, so much the better. The TV, we noted, already had the capability to talk to something like Amazon Alexa or Google Home.

Due diligence: what would not integrate

I checked whether the phone system could be integrated into Alexa or Google Home. For this setup, it could not. That is the sort of answer I would rather give on day one than discover after someone has bought a speaker and a false promise.

So the phone needed its own honest solution, and the TV needed a smart assistant that the set would actually cooperate with.

A phone that speaks the caller

After looking at what was available, I specified a Panasonic phone that announces the name if the number is in the address book, or the number if it is not. That is not a smart-speaker trick. It is the handset doing a job the smart platforms would not do here.

The practical effect is simple: she can know who is calling before she answers. Known family and friends are named. Unknown numbers are spoken as numbers, which is enough to pause and not treat every ring as someone she must pick up.

The TV: Samsung, a tablet, and Alexa

The television was a Samsung. It could integrate with a Samsung tablet and with Amazon Alexa. Google Home was an option on paper; from the research I did for this house, it had more limitations, so we did not force it.

Voice control through Alexa is now how the TV is used — including turning it on from standby. The aim was not a full home cinema remote replacement. It was a way to get in and out of the set without relying on a remote that was too small, too busy, or too easy to get lost in apps.

That does not magically make every on-screen menu large. It does mean the common jobs — power, and moving between what she wants to watch — can be spoken instead of hunted for on a handset.

Keep it basic on purpose

This is new technology for the person using it. We agreed to keep things basic rather than layering on routines, scenes, and a dozen extra devices. Independence is easier to protect if the system is small enough to remember.

There is more we can add later if they want it. In particular, routines and schedules for regular programmes she already watches — so the TV is ready at a familiar time, without another hunt through apps. That is a next step, not a day-one requirement.

What it does today

As of this install:

  • The daughter and her mam can know who is calling before answering
  • The TV can be controlled by voice through Alexa, including coming on from standby
  • We did not pretend the landline could live inside Alexa or Google when it could not
  • We have not piled on extra automations until they have had time to use what is there

I am waiting for feedback after they have lived with it. A case study written the week after an install can only tell you what we set out to fix and what we put in. Whether the phrases stick, whether getting back to live TV stays easy, and whether the spoken caller ID is enough — that is for them to tell me, not for me to assume.

What this kind of job usually needs

If you are looking at something similar for a parent or relative, the useful sequence is the same one we used here:

  1. Visit the house and look at what is already there — the TV brand, the phone, the remote they actually use.
  2. Name the two or three jobs that fail (here: streaming apps with no way back, and not knowing who is on the phone).
  3. Check integration properly before promising that “Alexa will do the lot.” Sometimes the right answer is a better phone, not a smarter speaker.
  4. Start smaller than the brochure. You can always add a routine for a regular programme later. You cannot easily undo a confusing system.

If you are in North Yorkshire or Teesside and want that kind of visit — patient, on site, and honest about what will not talk to what — that is the smart home work I do. We start from the house you already have.

Accessibility here was not a whole-house rebuild. It was a TV she could ask for, and a phone that told her who was ringing.

← All insights