Atharva Wankhede

One-click accessibility audits are useful but I always wonder how deep they go. WCAG has levels and a lot of automated tools catch the obvious color contrast and alt text issues while missing the more nuanced interaction patterns that actually affect screen reader users. Does Able flag the harder stuff or is it mostly the mechanical checks?

Capture and annotate tools look simple but the ones that actually stick are the ones where the gap between taking the screenshot and having a shareable, marked-up version is less than 10 seconds. What's the export flow look like for Dipshot? The format and whether annotations are preserved as a layer vs flattened matters depending on whether the output is going into a deck, a Notion page, or a...

This is the tool I didn't know I needed. I constantly take screenshots for changelogs and documentation and the extra step of jumping into Figma to wrap them properly always breaks the flow. Having it come out polished with custom backgrounds right from the menu bar is the right level of friction reduction for this kind of task.

The Cursor analogy is doing a lot of heavy lifting here. Cursor works well partly because code has clear structure, but video editing involves a lot of subjective judgment calls around pacing, tone, cuts. Curious what the 'taste' model actually looks like in practice and how much back-and-forth is typically needed to get to a cut you'd actually use.