How do you keep tracking symptoms on days you can barely hold your phone?

Why do bad days matter most for the record?

Because they are the record. A diary filled in only on days you feel able to fill it in is a diary of your better days, and every average it produces is flattering. Compliance studies of paper diaries found that most entries were not made when they claimed to be (Stone et al., 2002); the bad days are exactly when that happens. The design goal is therefore not a complete entry but a possible one.

What iPhone settings help most?

Apple’s accessibility support pages cover each in detail (Apple Support). The important step is doing this on a good day, when you can afford the hour of learning.

How small can an entry get?

Two taps: open the tracker, set the intensity. Everything else should be optional or remembered. Concretely:

• Prefill. The sheet opens showing yesterday’s values. If nothing changed, you confirm; if one thing changed, you adjust it.
• One scale. Intensity on a horizontal bar under the thumb, with the anchors printed. No number pad.
• Location remembered. If the knee was the left knee last time, it is the left knee until you say otherwise.
• No typing. A note is optional and never required. Choices are chips, not text fields.
• Reachable. The add button lives at the bottom, not the top right, so it is usable with the hand that is holding the phone.

If an app’s shortest entry needs more than this, cut measures until it does.

What should happen with text at accessibility sizes?

Everything you wrote should keep growing; the app’s own chrome may stop where it would break. The web standard for this, WCAG, asks that text can be resized to 200% without loss of content or function (WCAG 2.2), and iOS apps that support Dynamic Type go well beyond that. Signs of an app that did the work: grids collapse to one column, chips scroll instead of squeezing, nothing is cut off with an ellipsis, and the 0–10 scale stays usable rather than wrapping.

What about days you cannot log at all?

Leave the gap. A day without an entry should read as “not logged”, and a good app will show it that way rather than as a zero. Backfilling from memory the next day produces exactly the smoothed, peak-weighted account that the diary exists to avoid. If you want the day to carry information, a single tap for “bad day, could not log” is a reasonable compromise, recorded as what it is.

How is Longnote built for this?

Longnote supports VoiceOver throughout: every control is labelled, selected states are announced, and the 3-D body atlas is mirrored by accessible text, so nothing lives only in the picture. Text scales to the largest accessibility sizes, with grids collapsing to one column rather than squeezing. Reduce Motion turns every transition into a cross-fade, and nothing loops. The logging sheet prefills from the last entry, the intensity bar sits under the thumb, and the add button and tab bar stay at the bottom of the screen. This website holds itself to WCAG AA contrast in light and dark, respects reduced motion and reduced transparency, and is complete without JavaScript.