Fine print · 3 of 3

Accessibility statement

Last updated: 9 August 2026

A tool this simple has no excuse for shutting anyone out. Our working target is WCAG 2.1 level AA across the whole site, including the studio.

What’s in place

• Full keyboard operation. Every control in the studio (templates, colour swatches, segmented toggles, exports) is a real button or input, reachable and operable by keyboard, with visible focus states.
• Semantic structure. Proper landmarks, one h1 per page, labelled form fields, and a skip-to-content link on every page.
• Contrast. Text colours in both light and dark themes are chosen to meet AA contrast against their backgrounds.
• Reduced motion. The site honours prefers-reduced-motion and keeps animation minimal to begin with.
• Screen reader announcements. The signature preview is a live region, and copy/export confirmations are announced via a status toast.
• No time limits, no flashing content, no autoplaying anything.

Known limitations

• The signature preview renders email HTML: table markup whose colours you choose yourself. If you pick a low-contrast accent for your own signature, the preview will faithfully show it (and the compatibility check will nudge you).
• Colour input relies on the browser’s native colour picker, whose accessibility varies by browser.

Found a barrier?

If anything here is harder to use with assistive technology than it should be, that’s a bug and we want it reported: hello@plainforge.com. Accessibility reports get the same priority as broken-rendering bugs: the front of the queue.