Forms everyone can complete.

Our commitment

Askery, Inc. targets conformance with WCAG 2.1 Level AAacross both the public forms your respondents complete and the studio your team builds in. This statement describes where we stand today, what is built in, and the limitations we're honest about. It is a living document and is reviewed as the product changes.

Conformance target

We measure against the four WCAG principles - content must be perceivable, operable, understandable and robust. Public forms are the highest-priority surface because they're completed by the broadest, least predictable audience, so they receive the most testing attention each release.

What's built in

• Semantic, structured markup. Forms render real landmarks, headings in order, lists and native controls rather thandiv soup, so assistive technology can navigate by structure.
• Every control is labelled. Each field has a programmatically associated <label>; help text and validation errors are linked to their input and announced, so no one is left guessing what a field wants.
• Full keyboard operation. Choice, rating, ranking, multi-page navigation and submission all work without a mouse, in a logical tab order, with no keyboard traps.
• Visible focus states. A clear, non-color-only focus indicator follows keyboard navigation everywhere, so users always know where they are.
• Token-driven color contrast. Colors come from a single theme contract rather than ad-hoc values in components, which lets contrast be reasoned about and held to the AA ratio consistently instead of slipping component by component.
• Accessible anti-spam. A server-enforced honeypot + per-IP rate limit run on every public form by default, with no visible challenge for real respondents. When an owner needs an interactive challenge they can opt into Cloudflare Turnstile - chosen specifically because it's privacy-friendly and skips the inaccessible image-recognition tests that legacy CAPTCHAs lean on.
• Respects user preferences.Reduced-motion preferences are honored and forms inherit the page's text scale, so zoom and OS settings keep working.

Ongoing work and known limitations

We test with screen readers and keyboard-only flows each release, but we don't claim perfection. Builder-side surfaces such as the logic flow visualization and analytics charts are inherently visual and remain an area of active improvement; complex data visualizations are reviewed for text alternatives but may not yet be fully equivalent. A formal VPAT is planned and will be published when it can be backed by a real audit rather than a self-assessment.

Feedback and assistance

If you hit an accessibility barrier - as a respondent or a builder - please tell us. Email support@askery.app or use the contact page with the page or form, what you expected, and the assistive technology you were using. We prioritize accessibility regressions and will work with you to provide the information or function you needed in the meantime.

Related: our security model and support options.