Accessibility statement

Our target

We build Frontsheet to meet WCAG 2.2, Level AA. That means clear headings, labels that describe what a control does, visible keyboard focus, sufficient color contrast, and support for reduced motion. It's a target we build toward, not a certification; we haven't commissioned an independent audit, and we say so here instead of implying one.

What we've done

• every page uses a single, meaningful heading structure;
• interactive elements have a visible focus outline, not just a color change;
• form fields carry real labels, not placeholder text standing in for one;
• error and status messages are announced to screen readers, not just shown visually;
• color is never the only way we show status; a label or icon comes with it;
• motion respects your system's reduced-motion setting.

Known gaps

Frontsheet is still growing, and some areas haven't had a full accessibility pass yet, particularly newer workspace features built quickly for early customers. We don't have a complete, itemized list to publish today. When you report a barrier, we log it, fix what we can promptly, and tell you honestly if something will take longer.

Reporting a barrier

If something on Frontsheet is hard to use with a screen reader, keyboard-only navigation, voice control, or any other assistive technology, tell us. Email support@frontsheet.com with the page, what you were trying to do, and what happened. Include your browser and assistive technology if you can; it helps us reproduce the problem faster. We read every message and reply directly.

Related pages

For how we handle your information, see our trust and data page, our privacy policy, and our terms of service.