Misleading UX on input screen with OK/Cancel choices

[ILIMB]

Whenever I see the input screen asking for any kind of input, instead of tapping on OK, I instinctively tap the underlying checkmark button which is at the bottom right of the screen, still visible from the previous screen, and my action is interpreted as "cancel", and I have to repeat.
This design is clearly confusing, and not a good UX practice: if there are OK/Cancel options, those shall be the only selectable actions, the overlay shall not go away just by clicking outside it.

 

[Endercraft]

Can you say what actions are affected because I don't remember this being a thing.

 

[ILIMB]

Literally all modal screens in the app.
Which, unless there is an underlying button still visible, might be also working. But the transparency is little and the contrast high, in the example below, and the button in the bottom right corner screams "OK", and it's the closest action to the user's fingers when typing on the overlaid keyboard.

 

[Endercraft]

So if I understand correctly you instinctively try to click on the button instead of OK. I must admit that the fact that clicking anywhere that's not the screen cancels any changes and that's pretty annoying.

 

[ILIMB]

Exactly, when you click out, even inadvertently, you lose any change and are required to start over. In this case I pressed the check button at least a couple of times in a row, before building "muscle memory" that it wasn't the right course of action according to the provided UI.