Conformance statement

FormAssembly web forms and their associated public pages (such as confirmation and save-and-resume pages) conform with WCAG 2.1 Level AA. This scope does not include the form builder or form management features used by form creators.

Conformance status: Partially conformant with WCAG 2.1 Level AA for the scope described above. Four criteria (1.3.1 Info and Relationships, 2.1.1 Keyboard, 2.1.2 No Keyboard Trap, and 4.1.2 Name, Role, Value) are partially supported in limited scenarios relating to matrix fields and the date picker; see known limitations below and our Voluntary Product Accessibility Template (VPAT) for criterion-level detail.

Section 508: FormAssembly web forms conform with the Revised Section 508 standards (January 2017/2018), consistent with our Voluntary Product Accessibility Template (VPAT).

Product version reviewed: FormAssembly 5.186.0 (respondent-facing forms).

Review date: July 14, 2026

Scope

This accessibility statement applies to respondent-facing web forms created with FormAssembly and their associated public pages. It does not apply to:

• The form builder
• Form management and administration features

Measures to support accessibility

FormAssembly takes the following measures to ensure accessibility:

• Include accessibility as part of our product design and development practices
• Conduct internal accessibility reviews against WCAG 2.1 Level AA
• Track accessibility defects and improvements in our engineering backlog
• Provide accessibility documentation (VPAT) for customers and procurement teams

Assessment approach

This conformance assessment was conducted through an internal structured review (June 2026), including:

• Representative sample of respondent forms (default and custom themes, multi-page workflows, rich field types, embed)
• Automated testing (axe DevTools, WCAG 2.1 AA)
• Manual keyboard, reflow, and screen reader spot-checks

Details are documented in our VPAT and internal evaluation record.

Known limitations

Area	Impact	Workaround / status
Matrix fields	Label-in-name markup (2.5.3) may not fully meet requirements in all cases; automated testing flags structural markup defects in matrix table headers (1.3.1, 4.1.2)	Screen readers announce row/column context in practice; engineering improvements in progress
Date picker	Calendar popup is not fully keyboard-operable (2.1.1)	Dates can be entered directly as text in the date field; engineering improvement in progress
Custom themes	Color contrast and focus indicator styling depend on administrator configuration	Default themes meet WCAG 1.4.3 and 2.4.7 requirements; administrators with Theme CSS access can configure colors to meet requirements

Feedback and contact

We welcome your feedback on the accessibility of FormAssembly web forms. Please contact the Support Team at [email protected].

Technical specifications

Accessibility of FormAssembly web forms relies on the following technologies:

• JavaScript
• HTML
• WAI-ARIA
• CSS