Making the button an early tabindex is one of the best options you have.
Also, since the action is already visibly relevant, it's the option the users are going to tap/click the most, just by default action.
Also, if what they are acknowledging is a license, conditions, general terms or similar text, users will tap/click/accept by default because there is no other way to keep going on the application. Even when they haven't read what they are acknowledging. So you can count on that defective behaviour.
If the text and the confirmation are really necessary, and you want the user to accept it, just make it more visible that the cancel option. You can make it a bit bigger, or make the cancel button look like it is not clickable/tappable. Any option that makes the "confirm" more visible works. Although, in my opinion, both buttons should have the same visual weight since both are as relevant, they both represent the user's option and decision.
Finally, and this is a matter of opinion, I would use a consistent design, if the "confirm" is a button, then cancel should also be one, even if your idea is to direct the user to a page where something is explained.