you could adapt the approach above for sure.
The order of the list will determine the order of tabbing so if the component orders don’t change on screen then it should be work… or have I missed something.
You can add flags into the loop, using the visible attribute or add a tag to the component that can be used in the loop to know whether to skip it or not.
The problem with replicating a tab key press on a button click is that as soon as you click the button to tabNext that button now has focus and so literally hardwiring tabNext would not go to the expected component. You’d have to do something like the above anyway I think… Or some other hack.