UX/UI: Field navigation on treatment view

[g5WS]

Trio v0.8.4.63 dev 8cff8b6

Following #1422, I tried pressing down arrow repeatedly and found some inconsistent behavior.

1. I need to tap into a field for the number pad to appear. Should it appear automatically on load? Presumably, the user is there to enter data. This may improve quality of life for users with visual impairments.

2. Repeated down arrows stop responding. In the use case where protein and fat are both showing, when you tap into Carbs, then tap down arrow four times, you see the cursor move to fat, protein, bolus, then back to carbs. Tap down arrow four more times, and the behavior repeats. Tap down arrow four more times, and you will see the cursor get stuck in the bolus field, and further down arrow taps do not move the cursor back up to Carbs. Down arrow does not grey out.

3. Should pressing down arrow move the field select to External Insulin? Admittedly, it’s not a number, but I’m wondering if field navigation mechanism would also affect VoiceOver (and would be needed for visually impaired users).

I am testing on the latest iOS27 Developer Beta.

[LiroyvH]

Hi!

1.) do you mean you'd like the keyboard to show immediately when the treatments window is opened? I personally like it not doing that until you tap something, as it provides a full overview without the keyboard (you can see the small graph and recommendation at one glance). Also for the keyboard to appear it'd have to auto-select a field if I'm not mistaken. But maybe the user doesn't want to input anything in to that field, which makes the selection annoying. (Imho) Last but not least, say it auto-selects Carbs but you only want to bolus: then you have to scroll to bolus first and tap it; whereas with no keyboard on screen you can simply directly tap the bolus field and you're there. :) Tapping a field to open it or otherwise stay hidden (so current behavior) makes more sense to me.

2.) I cannot reproduce 2. I can infinitely tap the down or up button and it endlessly keeps cycling through the four fields (carbs, fat, protein, bolus or vice-versa) without any issues. However, I haven't tested iOS 27 so could be a new bug. I will deploy this to my test phone running iOS 27 and try again. But it being a beta makes this hard, it could be solved by Apple next week so to say...

3.) Good question. The same question can be asked for the "Reduced Bolus" and "Super Bolus" options (when you have that enabled)

[g5WS]

1.) do you mean you'd like the keyboard to show immediately when the treatments window is opened? I personally like it not doing that until you tap something, as it provides a full overview without the keyboard

I don’t know enough about the technicalities of supporting users with visual impairment to weigh one above the other.

2.) I cannot reproduce 2.

I tried again, and was able to reproduce, but I was able to cycle through more times before getting stuck. Perhaps this phenomenon is time dependent?

3.) Good question. The same question can be asked for the "Reduced Bolus" and "Super Bolus" options (when you have that enabled)

💯. I forgot about this because I still build with @MikePlante1’s segmented control. 😁😁😁. The radio buttons would be a thorny design challenge, because the Trio implementation is non-standard.

Trio allows users to unselect a selected radio button by tapping on it again. The web browser design spec does not allow users to unselect all radio buttons in a group once they have made a selection. You can change the selection, but not end the state where one button is selected.(https://www.w3.org/WAI/ARIA/apg/patterns/radio/#keyboardinteraction)

(I was going to wait until v0.9 before bringing this up again. But since you mention it… 🤭)

[dnzxy]

Those custom keyboard buttons will very likely be removed, so I'd suggest to park this issue as obsolete.