And make it so they don't have to log back in frequently.

I solved most of the sign-in problem for my dad by picking a simpler browser than Google Chrome, and by tweaking his browser settings to be just-so. That's not going to be much help for you, the website creator...

Maybe allow passkeys for login? These days, passkeys usually get stored/supplied by the underlying OS. (By usually, I mean that's the statistically most common source of the passkey today. They can also come from a browser plugin or a hardware key.)

- a large font size by default, and maybe a font size slider on the homepage. Test everything at 200-300% scale as WCAG recommends

- don't change the UI! Or change as little as possible, at least for existing users. Which kinda upturns the whole always-updating nature of web SaaS but I think it can be done

- hire a good designer who can streamline your UX and screens and keep only the bare minimum features

- maybe offer human support? Like a phone number? Probably unreasonable for you tho

Wish I had ideas for simpler login and auth.

Have you found any successful design strategies in your 10 years? Any insights from user testing?

I created this tool (https://anftr.com/) for some of my ex-colleagues in their early 50s who were trying to navigate the world of office software. They were struggling with Microsoft Word and Excel, and I have seen them yell at ChatGPT and bash their mouses constantly, hoping the computer will load files faster.

Essentially, you focus on text and video demos. The foundational design concept for elder tech is providing clear instructions and minimizing interactions.

If you want them to sign in, you should not require them to press a button more than two times.

To address things they tend to forget, consider a human custodian or "IT concierge" model, please. The reality is that after a certain age, people really struggle to learn new things and prefer talking to a person for help. Technology has its limitations.

If you are working with users aged 50 to 80, provide them with a phone number and charge a subscription for the service or a one-time payment. It might be borderline exploitative, but I have noticed that elderly individuals want a "solution" rather than a lesson.

You explain how to do something, and if they are eager to learn, they will. You offer them a solution either way. Please do not create a monetization model for this custodian service and keep the charge as low as possible.

The money you receive from this serves purposes: it is designed to help them second guess and try to help themselves. If you do not charge for something, they will just keep asking you questions. When you charge for something, they perceive it to have more value compared to it being free.

Do not prioritize ease of operation that compromises their security.

When I try to sign in to most apps on my TV, it usually displays an code that you can type in on another device so that you don't have to type in a long password using the D-pad on the remote. Could you maybe implement something similar for your website? This way, my grandmother could just call and read me a code, and then I could handle the sign in remotely. As long as you only need to sign in ~once a year, this would be my preferred option.

Not all seniors have trusted friends/family who can help them, but lots do, so making it easier for the helpers will in turn make it easier for the seniors. Plus, there's no phishing risk for the senior with this method, so it's a relatively secure option too. (There is a phishing risk for the helper, but presumably they're the least vulnerable person in this scenario)