Let's say the user only wants to run the accessibility audits. We dont technically need to reload the page.

And the user may have navigated the app to a specific state they want to test, or made some DOM tweaks and want to evaluate if they are working better.

These usecases seem valid, so I'm thinking we should figure out if an audit requires a page reload. We can then communicate to the user if we expect a reload or not.

Just guessing, but I think we already know this. Do any of the audit's requiredArtifacts have a gatherer with a beforePass? If not, no reload technically needed.

cc @alice