Quick question for people shipping Framer client sites: what accessibility check do you still do manually before handoff?

I have been tightening a small plugin called Ally Auditor around that exact moment when the page already looks finished, but the boring QA details can still slip through:

- images that never got real alt text

- headings that look right visually, but are not structured

- icon buttons or links with no readable label

- contrast that changed during the final visual pass

- some lightweight proof that the check was actually done

The thing I am trying to avoid is the giant "audit report" feeling.

I want it to feel more like a quick QA pass inside Framer before you send the site to a client or publish a template.

If you build in Framer, which one would you want a plugin to catch first: alt text, contrast, headings, labels, or report proof?

Blunt feedback is genuinely useful for the next pass.

Quick question for people shipping Framer client sites: what accessibility check do you still do manually before handoff?

I have been tightening a small plugin called Ally Auditor around that exact moment when the page already looks finished, but the boring QA details can still slip through:

- images that never got real alt text

- headings that look right visually, but are not structured

- icon buttons or links with no readable label

- contrast that changed during the final visual pass

- some lightweight proof that the check was actually done

The thing I am trying to avoid is the giant "audit report" feeling.

I want it to feel more like a quick QA pass inside Framer before you send the site to a client or publish a template.

If you build in Framer, which one would you want a plugin to catch first: alt text, contrast, headings, labels, or report proof?

Blunt feedback is genuinely useful for the next pass.