Export "as JSON" from FastPass

[jsnmrs]

Is your feature request related to a problem? Please describe.

I noticed that "Export result" options differ depending on whether you're coming from a FastPass or an Assessment.

Describe the desired outcome

Export "as JSON" option available when exporting results from FastPass.

Describe alternatives you've considered

I could run a full assessment and only include programmatic tests to achieve a similar result, but it's a few extra clicks.

Additional context

I want to feed FastPass results into a dashboard showing results across many URLs. JSON would be the ideal format for that workflow.

FastPass export result modal screen

Assessment export result modal screen

[ghost]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[ferBonnin]

Hi @jsnmrs thanks for the feature request! we have a couple of questions:

• Can you please tell us more about your scenario?
• FastPass consists of 3 steps, are you looking for the results of automated checks only or also needs review and tab stops (asking because from the workaround you mentioned we are not clear if its all 3 steps) ?

[ghost]

The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights!

[jsnmrs]

Hi @ferBonnin — sure thing!

Scenario-wise, I hope to have support staff run a FastPass on a URL and optionally complete the tab stop review. If there are "needs review" items, they would also be optional. We would take the JSON report for that URL and feed it into a dashboard that shows FastPass results over time. These reduced scans will supplement our less frequent, complete assessments.

Ideally, the JSON output would match the HTML export, regardless of which of the three FastPass steps are complete. For example, if someone only ran the automated checks, the tab stops would be listed as "incomplete."

Does that clarify a bit?

[ghost]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[ferBonnin]

thanks for the additional information on your scenario @jsnmrs. After reviewing with the team, we have added this to the backlog and marked it as help wanted. We would be happy to take on a community contribution for this feature request!

[jsnmrs]

Much appreciated! Thanks @ferBonnin

[Pranav-yadav]

Hey @ferBonnin !
Any status on this?

I can help with this one; if not already assigned to anyone :)

PS: Though, Jason has explained the expected behavior very well, how this need to be approached programmatically?
Will have a look at the respective code, soon..

[DaveTryon]

@Pranav-yadav, please feel free to submit a PR on this

[Pranav-yadav]

It's great that this issue is being revived after almost A YEAR.
I actually don't have much time to work on this.
Thanks.

[JunkParticleLander]

Watching this one. Could really help as we are testing multiple sites.