Define roadmap for integration with WCAG-EM

[mgifford]

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

We need to have some clarity about we want to be able to use the Accessibility Insights reports in conjunction with something like a WCAG-EM tool.

Right now so many of these automated tools are used in a few different ways as people are evaluating websites. Defining a template for evaluating sites using Accessibility Insights & the WCAG-EM Report Generator would be brilliant.

Describe the desired outcome

I think it could look a little bit like this.

1. Start a new report
2. Define the scope
3. Explore the Target Website
4. Collect Sample URLs that either is a Structured Sample, a Randomly Selected Sample, or a Complete Processes
5. Open link to defined pages and examine it with FastPass (axe & tab)
   • Run assessment (which would automatically include the elements from the axe scan
   • Save the assessment and upload it to the WCAG-EM page
   • Repeat for all Sample URLs defined
6. Review the Report the Evaluation Findings
7. Save the JSON version of the Website Accessibility Evaluation Report and if needed the HTML

The JSON report could then be sent to the developers who could either parse the material into Jira or Trello. Or they could simply:

1. Import a the provided report
2. Review the scope
3. Review the Target Website
4. Verify that the Sample URLs are valid.
   • Ensure that the problems can be replicated by the development team.
   • Prioritize list of tasks to address concerns
   • Complete accessibility fixes
5. Open link to updated pages and examine it with FastPass (axe & tab)
   • Run assessment (which would automatically include the elements from the axe scan
   • Note changes which have been made and ideally point to pull requests or issue queues
   • Save the assessment and upload it to the WCAG-EM page
   • Repeat for all Sample URLs defined
6. Review the Report the Evaluation Findings
7. Save the JSON version of the Website Accessibility Evaluation Report and if needed the HTML
8. Diff the version of the report that the team was provided with the version of the report after revisions were made.

This would really help to ensure that development teams are able to resolve issues with confidence.

[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 feature request @mgifford! after talking with the team, we would be happy to take on a community contribution for this feature request for the particular request of a template and JSON report in the format of the WCAG -EM report generator.

[mgifford]

I'll re-open this if we get to developing that. In the interim though, thought I'd add a link to this related project https://github.com/GSA/open-product-accessibility-template

[mgifford]

Just as an update, OPAT is now going by OpenACR. There's also an editor that is live here https://gsa.github.io/openacr-editor/

We would want to be able to import in the same way as WCAG-EM is doing with JSON-LC formatted EARL data.