New axe violations since last sprint (last two weeks)

[mgifford]

Question

Sprints are every 2 weeks. What new errors were produced in that time? What errors were fixed? What URLs are added/removed?

Target Audience

developers

Input Options

Domain, violations, sort-by axe impact (critical, serious, moderate & minor), and technology.

We need the tech for the page so that we can limit it to just Drupal

Output Format

• [X] CSV
• [ ] XLSX
• [ ] HTML
• [ ] XML
• [ ] YAML
• [ ] JSON
• [ ] Something Else

Team

🌐 Accessibility Scans

References

No response

[TheBoatyMcBoatFace]

@mgifford how do you want to handle sprint dates?

Option 1 Would a field called sprint_start work? You would set the date your sprint started and then it would capture the results from then until now.

Option 2 If you have a csv of sprint dates in github or something, I can set a variable like sprint_team and you would put the name of the team, like va_platform_cms or something like that. Then, depending on the date, it would show you the results for the active sprint. I would need the csv to have the columns sprint_team, sprint_start, and sprint_end. I can break it out by org as well. Instead of va_platform_cms you would set the variable org_name to va and team to platform_cms.

I am guessing the first option is what you are looking for, but I want to ask just in case.

[mgifford]

I'm wondering if that's needed now since you've got the abilty to just pull start/stop dates. With the Google Sheet I created, we should be able to have that snapshot without adding more infrastructure. 

I would like to be able to just sort for critical, serious, moderate or minor errors. Frankly for most government sites being able to restrict critical/serious and WCAG 2.0/Section 508 would be really nice. 

I'm also not sure where the URL field went. Maybe it is back. That's also important. 

Being able to see the tech data would also be useful. Being able to query for Drupal would be huge.

[TheBoatyMcBoatFace]

The url field is back. It wasn't carried over in the recent view, but that has been resolved.