Ability to add comments, if needed, in lists of instances when an item is flagged as a failure.

[anipv]

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

It would be good to have an optional comment box for each non-automated criteria , to provide further explanation about the issue flagged, if needed

Describe the desired outcome

I'd like to be able to add optional comments to failed checks in order to provide additional guidance or context to developers. Additionally it'll help a tester (especially if someone is testing multiple pages) with. Ideally, this could be an additional optional column in the instances table, or an add button could be placed in the table which triggers a dialog similar to adding an issue in non-automated checks, or even a comment field in the "Getting Started" for each section.

Describe alternatives you've considered

Currently I put it under Keyboard Navigation even though it does not fit into that section. When gathering analytics, the errors listed under the Keyboard navigation are not accurate because of this. Sometimes I even upload an additional Word document as an attachment which is again not ideal. I would like to keep all documentation in one place.

Additional context

I work for a government agency and would like to promote use of this application more broadly across the agency, and this feature will make working with other divisions within the agency smoother.

[DaveTryon]

Hi, @anipv! Thanks for your feature suggestion. We've reviewed it and added it to our internal feature backlog. It's impossible to predict when this might make it to the web extension, but we'll do our best to make it happen. Thanks for using Accessibility Insights!

[anipv]

Hi there!
Thanks for the follow up reply. I see there's another similar "Need Help" request under Issues (https://github.com//issues/485).
How can I help to make this happen sooner :-)
TIA

[DaveTryon]

@anipv You're correct that this is basically a dupe of #485. We had a huge backlog that we were never going to be able to complete, so this got removed as part of the backlog cleanup. I don't have a great answer on how to move this along, other than to contribute a PR that adds the code in all the places it needs to be (UX, reading and writing this in both Assessment and QuickAssess, tests, etc.) It's a fairly large piece of work, which is probably why it kept getting pushed aside by other things. We have some other large items in our backlog that will realistically take some time to complete, but at least this is back on the radar.

Thanks for using Accessibility Insights!