Run in reporting mode vs failure mode

[isen0011]

Thanks for writing this - we look forward to using it widely to help us with the new Title II regulations.

One thing that would help us move forward is to have the ability to add the gem to all of our projects, but instead of having every system test fail when it encountered an accessibility issue to instead save the failure and instead give us a report of all the accessibility issues. We could then use that for reporting to our management and tracking our progress towards closing accessibility gaps.

Ideally we'd love to have something where we set a configuration setting, like config.capybara_accessibility_audit.reporting_only that, when run would give us output something like

Finished in 5 minutes 5 seconds (files took 2.45 seconds to load)
238 examples, 0 failures, 24 failed accessibility tests

Failed accessibility tests examples:
... detailed breakdown of the accessibility tests that failed...