Accessibility

A Popkit widget renders on your website, so it shows up in your audit, not ours. This is what it guarantees, what is left to you, and what it does not cover — written so you can hand it to whoever is asking.

What the widget does

Renders as a dialog with aria-modal, labelled by its own heading.
Traps focus while open and returns it to whatever had it before, so a keyboard user is never dropped at the top of the page.
Marks the rest of the page inert while a modal is open, so screen readers do not wander behind it.
Closes on Esc, and always has a visible dismiss control as well — a close button, a decline link or a backdrop. A widget with none of the three is refused at save time, because a keyboard shortcut is not a way out to somebody on a phone.
Every field carries a programmatic label, and the error message is in a live region so it is announced rather than only seen.
Honours prefers-reduced-motion: entrance animations are skipped entirely rather than shortened.
Inline widgets deliberately do not trap focus or make the page inert — they are part of the page, and treating a footer form as a modal would be hostile.

What is yours

Contrast. You choose the colours. The editor warns when a combination falls below 4.5:1, but it does not stop you — some brands have a palette they are required to use.
Your copy.Field labels, the heading, and the small print are yours; a label reading “Field 1” is accessible and useless.
Custom HTML. When you replace the template with your own markup, everything above is your responsibility instead of ours. The editor still refuses markup with no dismiss control.
When it appears.A popup that interrupts someone mid-task is a usability problem no amount of ARIA fixes. Consider the “not before page N” trigger.

What is not covered

We have not commissioned an independent WCAG audit. The claims above are from our own testing, and the widget markup is small enough that yours can verify them quickly.
No VPAT or ACR is published yet.

Found something wrong? Tell us and we will fix it — accessibility bugs are treated as bugs, not as feature requests.