I have a wizard that on the first page a user can toggle what all pages they want to access. It is meant to narrow down the available options to what they need. When a user turns one of the options off, I disable that page. I don't hide it because the functionality with the add/remove pages tends to put the newly added pages at the bottom of the wizard (which I don't want).
The next problem I run into is the functionality of the Previous / Next Buttons. If the next or previous page is disabled, the relative button is also disabled. Which means the user now has to click the actual step instead of clicking next.
I attempted to add my own buttons but without access to the individual steps like the default buttons have I can't determine if the steps are disabled or not. My goal is to click the "Next" or "Previous" button and determine what the next available step (if it is non-linear) is instead of forcing the user to figure out they need to click the step in the stepper section.
There is a hack to get around this, but the business logic is not ideal, and it is very rigid. I would prefer not to go this route. The work around is checking all the possible combinations of variables that control the disabled option for each page.