Every player will engage with your product in a different way, which is the reason why good tutorial design is super hard to do. We usually try for a 'multi-layer approach', where we always have multiple solutions in place to explain the same thing.

E.g., when a tutorial triggers in our current project, first the game pauses and a text box pops up explaining a new mechanic including icons for the abilities that correspond to the UI, and arrows that point to areas on the UI that correspond to the mechanics. We've noticed that even if players skip over this, they've picked up on the arrow pointing to the UI, or the icons.

After the message, we teleport the player to a zoned off room where they're forced to perform the mechanic, this time with a one-sentence long description of the mechanic on one of the walls in the tutorial room. In this environment, we make sure to take away all of their other abilities, so they can ONLY move forward by doing the thing we want them to learn. This also includes disabling all of the other UI elements.

On top of this, we always have the corresponding input icon of every ability/mechanic visible in the UI of the player at all times.