Research

Nothing on this Ken is a guess.

Every number below is read off the shipped code, not off a note somebody wrote about it. Each one sits next to the standard or the study it came from, and the small raised numbers elsewhere on this site point here.

A design decision is easy to state and hard to check. So each entry gives three things: what The Ken does, the figure actually in the build, and the source. The sources are other people's. Every one of them opens in full.

The entries are numbered for life. If we ever change our mind about one, the number stays and the entry says what changed.

The whole Ken was designed around unsteady hands.

The Ken is used by people whose hands shake, whose fingers are stiff, and who press harder and longer than a touchscreen expects. Four decisions come from that, and all four are measurable.

  1. 1

    Buttons are far larger than a phone's.

    In the build: the main buttons on the Ken's screen are between 80 and 110 pixels tall. The smaller Settings buttons are 56 pixels, which is the accessibility floor plus about a quarter again.

    W3C Web Accessibility Initiative, Understanding Success Criterion 2.5.5: Target Size (Enhanced). Sets 44 by 44 pixels at level AAA, and gives the reason as helping "users who may have trouble activating a small target because of hand tremors, limited dexterity, or other reasons".

  2. 2

    And larger again than the accessibility floor, because that floor was written for everyone rather than for older hands.

    In the build: each face on the home screen is a tile filling roughly a quarter of the screen, so the control used most often is the biggest thing on it. The Settings buttons in 1 are the small end at 56 pixels.

    Z. X. Jin, T. Plocher and L. Kiff, "Touch Screen User Interfaces for Older Adults: Button Size and Spacing", in Universal Access in Human-Computer Interaction, Springer, 2007. Measured reaction time, accuracy and preference against button size, button spacing and manual dexterity, on the stated ground that existing recommendations were written for a general audience.

  3. 3

    A tremor cannot press the same button twice.

    In the build: a second tap that lands within a centimetre of the first and within 350 milliseconds of it is thrown away. On the on-screen keyboard the window is 250 milliseconds, because "77" and "nn" are things people mean to type. Separately, more than ten taps in a second is treated as a child playing with the screen, and the Ken stops accepting taps for half a second.

    S. Agarwal and M. C. Biagioni, "Essential Tremor", StatPearls, StatPearls Publishing. Describes essential tremor as a 6 to 12 Hz postural tremor of the hands, and notes that its incidence rises with age. A shake in that range puts repeat contacts roughly 83 to 167 milliseconds apart, which is inside the window above; a deliberate second press is not.

  4. 4

    A card that has just appeared will not act on a press that was already on its way.

    In the build: when a card appears over the screen, its buttons are held for 1.5 seconds. The card says "Just a moment...", the button dims, and a dark bar sweeps along its bottom edge, so the wait is visible three separate ways rather than felt as a broken Ken.

    Same tremor evidence as 3. The hold exists because a hand travelling towards a button it wanted a moment ago will land on whatever has replaced it.

Every colour on the screen was measured before it was chosen.

Sight changes with age in ways that are well documented, and the accessibility standards say out loud which age they were calibrated against. That made the arithmetic straightforward.

  1. 5

    Text has to clear 4.5 to 1 against what is behind it.

    In the build: two tests compute the ratio rather than trusting a number written in a comment. One reads the colour values out of the shipped files; the second reads the colour off the rendered page, which covers the cases the first cannot parse. That distinction is not theoretical. One page on this site had a comment claiming 8.27 to 1 above a pairing that measured 3.96, and the comment is why nobody looked again for months.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.3: Contrast (Minimum). States that 4.5 to 1 "was chosen for level AA because it compensated for the loss in contrast sensitivity usually experienced by users with vision loss equivalent to approximately 20/40 vision", and that 20/40 "is commonly reported as typical visual acuity of elders at roughly age 80". That is our reader, described by the standard itself.

  2. 6

    Things that are not text have their own floor.

    In the build: the bar that sweeps across a held button was once a pale wash that measured 1.05 to 1 on two buttons, so a person pressed, saw nothing, and had no way to tell a waiting Ken from a broken one. It is now dark ink at 80 per cent, measured on every button it lands on: 4.64 to 1 on gold, 7.96 on cream, 3.58 on green, 3.01 on red.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.11: Non-text Contrast. Sets 3 to 1 for user interface components and meaningful graphics.

  3. 7

    Colour alone never tells you what something means.

    In the build: the green is #2AA06A and the red is #D94A3D, a pair that stays distinguishable to someone who cannot tell ordinary red from ordinary green. Neither is the only signal: an answer button is labelled "Answer", and a status dot shows a tick or a cross. In the admin portal a test holds those two colours and the amber to one definition each and refuses an off-palette green, red or amber anywhere in the markup.

    W3C Web Accessibility Initiative, Understanding Success Criterion 1.4.1: Use of Color. Names people with partial sight, people with limited colour vision and "older users with reduced color perception" as the reason.

  4. 8

    The text is set at large-print size and does not need to be enlarged first.

    In the build: body text on the Ken is 22 pixels, which is about 16.5 point. Live captions during a call are 44 pixels, about 33 point.

    Office for Disability Issues, Accessible communication formats, GOV.UK. Asks for "a minimum 12 point text size", says to "consider using 14 point text if the audience includes people with sight loss", and defines large print as "a point size of 16 and above".

Most of the people this is built for cannot hear a call properly.

  1. 9

    A call is captioned on screen, and the volume is set by the family rather than by the person struggling to hear.

    In the build: both call screens show live subtitles, at the 44-pixel size in 8, and a test refuses a build where either screen loses them. Volume is set from the admin portal, from anywhere.

    RNID, Prevalence of deafness and hearing loss. "Almost 80% of people over the age of 70 will have hearing loss", and "over half the population aged 55 or more have hearing loss".

Nothing disappears while it is still being read.

  1. 10

    A message on screen waits until the person is finished with it.

    In the build: notices stay for 20 seconds on the Ken and in the admin portal, and a tap dismisses one at any point. The portal's used to clear themselves after 3.5 seconds.

    W3C Web Accessibility Initiative, Understanding Success Criterion 2.2.1: Timing Adjustable. Written because "people with disabilities such as blindness, low vision, dexterity impairments, and cognitive limitations may require more time to read content".

Two findings decided what The Ken is, before any of the above.

  1. 11

    Being cut off raises the risk of dying earlier.

    In the build: the whole Ken. One screen, the faces of the people who matter, and nothing between the person and a call.

    J. Holt-Lunstad, T. B. Smith, M. Baker, T. Harris and D. Stephenson, "Loneliness and Social Isolation as Risk Factors for Mortality: A Meta-Analytic Review", Perspectives on Psychological Science, 10(2), 2015, pages 227 to 237. After controlling for confounds, social isolation gave an odds ratio of 1.29 and loneliness 1.26, which the authors give as a 29 per cent and 26 per cent increased likelihood of mortality.

  2. 12

    The ways a scammer reaches an older person are the ways an ordinary device is useful, so The Ken does not have them.

    In the build: no phone number, no email inbox, no web browser, no apps to install and no SIM card. The faces on the screen are the contacts the family approved in the portal, and a caller who is not one of them cannot get through.

    Age UK, "Older person becomes fraud victim every 40 seconds", 30 July 2019, analysing the Crime Survey for England and Wales 2017-18. Around 8 per cent of respondents aged 65 and over, more than 800,000 people, reported being a victim of fraud in the previous year.

  3. 13

    Over £500m per year is taken from individuals talked into paying a scammer, and the telephone is the costliest route in, so the Ken has no telephone number and no SIM card.

    In the build: a Ken can only be reached by a contact the family approved in the portal. There is no number to dial it on, so a cold call cannot arrive at all, and every approval leaves a record.

    UK Finance, Annual Fraud Report 2026, published June 2026, covering 2025. Criminals stole £1.28 billion through payment fraud in total. £576.4 million of that went to scams where the victim was talked into paying the money themselves, and £500.8 million of that fell on individuals rather than businesses. Of those cases, 17 per cent began over the telephone network and took 28 per cent of the money; 66 per cent began online and took 32 per cent. A scam that arrives by phone costs its victim more.

  4. 14

    Half of people over 75 take a live scam call on their landline in any three months, so the Ken has no number one can arrive on.

    In the build: the Ken cannot be dialled. Only a contact the family approved in the portal can make it ring.

    Ofcom, Scams Research 2021, fieldwork by Yonder among 2,000 UK adults, 18 to 19 September 2021. In the previous three months, 61 per cent of people aged 75 and over had received a suspicious call to their landline and 50 per cent had taken a live voice call, against 25 per cent and 15 per cent of those aged 16 to 34. The base for the 75 and over group is 140 people.

  5. 15

    Being caught costs an older person several times more, so the Ken never asks anybody to spot a fake.

    In the build: nothing on the Ken asks the person to judge whether a caller is genuine. A stranger cannot reach the screen, so there is no decision to get wrong.

    B. Havers, K. Tripathi, A. Burton, S. McManus and C. Cooper, "Cybercrime victimisation among older adults: A probability sample survey in England and Wales", PLOS ONE, 18 December 2024, reading the Crime Survey for England and Wales 2019-20 across 35,069 people. Among victims aged 75 and over, the odds of losing money were 4.25 times those of people aged 16 to 24.

  6. 16

    Millions of older people are already avoiding the phone because of scams, so the Ken removes the channels a scammer uses rather than asking anyone to be vigilant.

    In the build: there is no number to ring the Ken on and no inbox to write to it. The only people who can reach the screen are the ones the family approved in the portal, so answering it is always safe.

    Age UK, "Millions of over 50s fear opening their doors and answering their phones because of scams", 2024. Almost a fifth of over-50s in the UK, 4.9 million people, fear answering their phones, and 2.1 million say a fear of scams puts them off using a smartphone at all.

  7. 17

    Most people over 65 have already been targeted, and the harm outlasts the money, so the Ken is built so the attempt never arrives.

    In the build: no phone number, no inbox, no browser and no apps to install. A stranger has no route to the screen and nothing on the Ken asks its user to judge whether a caller is genuine.

    Independent Age, "The Hidden Cost of Scams", 4 October 2024. Nearly 3 in 5 people aged over 65 have been targeted by scams, with average losses of £4,000 per victim, 31% of victims reporting long-term mental health challenges and 12% negative physical health effects.

A source is not a certificate.

Citing the W3C's accessibility criteria is not the same as being audited against them, and we do not claim a certification we have not been given. Our claim is narrower and checkable: the figures above are the figures in the code, and the sources are the ones we used.

The Ken is a way to keep in touch. It is not a medical device, it does not diagnose or treat anything, and none of the research here is offered as clinical advice.

If you think one of these sources does not support what we have built on it, tell us and we will either fix the build or fix the page.