NVDA Keyboard Navigation Issue in Process Block (Step Progression)

I’m testing the Process block for keyboard and screen reader accessibility using NVDA and wanted to confirm expected behavior.

Initially, NVDA reads the step buttons (Step 1, Step 2, etc.) along with the left/right navigation arrows, and then proceeds to read the content of Step 1. After the Step 1 content is read, pressing Tab moves focus to the next interactive element in the following block, rather than moving to Step 2.

At the moment, the only way to reach Step 2 is by using Shift + Tab to go back to the step buttons and activating it.

Is this the expected keyboard interaction for the Process block, or should Step 2 be part of the natural tab order immediately after the Step 1 content?