>A few developers gave us early feedback and requested screenshots of the pages where accessibility violations occurred.
It's amazing how much a screenshot will do for my motivation to fix a frontend bug. Visually identifying severity is much easier than reading and making a mental judgement.
I like using video as well. The whole "picture is worth 1000 words" adage is true, and it makes all kinds of bugs far easier to recognize.
I'm sure other tools are great too but I find Cleanshot on macOS makes it super convenient to do it, so there's no excuse not to document reports with images and/or videos.
I do the same with pull requests. Words are almost always essential, but demonstrating bugs/changes/features directly through accompanying visuals is hard to beat.
If you don't need to edit the screenshot, Command+Control+Shift+4 will bring up crosshairs that will put the screenshot selection in your clipboard and won't save it to disk. It's super handy for doing a ton of quick, one-offs.
I dreaded videos for a few reasons, some of which could have been fixed, but some were human nature.
First, they didn't play in all browsers at the company I worked at. That meant I had to either download it, or use a different browser for that.
But even then, it was a game "guess what the CSR thought was wrong" in the video. Usually after watching a rather long intro sequence before getting to the actual bug.
If the company is trying to replace written bug reports with videos for speed or convenience, it's a nightmare for the devs.
If it's just an add-on to show the specifics, then it might actually be good. I rarely got those.
It's amazing how much a screenshot will do for my motivation to fix a frontend bug. Visually identifying severity is much easier than reading and making a mental judgement.