Accessibility Compliance Module
Overview
Form Builder:
Each Form.io component is tested for accessibility compliance using standalone applications. To create accessible forms, we offer a form builder that includes only the components that have been revised and designed in compliance with WCAG 2.1 standards.
When building forms leveraging the Form Manager application, the Form Builder will automatically restrict non-accessible components and settings allowing the user to create fully accessible forms.
When leveraging the Developer Portal the following components should not be used when creating fully accessible forms. These components are not included in the Accessibility Compliance Module, and do not meet accessibility-compliant standards or follow best practices in catering to a broader audience engaging your forms:
Tags
Address
Survey
Tabs
Data Map
DataGrid
EditGrid
Recaptcha
Nested Form
Sketchpad
Tagpap
DataTable
Signature
Custom
Form rendering module handles the following:
Screen readers' announcements upon user action
Focus order/Focus trap/Focus placement
Dynamic change of aria-attributes
Validation messages handling
Special styles for invalid/valid fields
Form.io USWDS template module OR Form.io Bootstrap template module handles the following:
Proper HTML markup (every form field needs an associated label, correct component structure etc.)
Aria-attributes such as aria-describedby, aria-labelledby, etc.
Additional helpful messages for sighted users
Additional instructions for non-sighted users (e.g. number types, etc.)
WCAG compliant color contrasts (only applicable for USWDS for now)
Contact sales@form.io for more information
Features
Accessible Form Manager
Accessibility Templates (USWDS)
Accessibility templates github path: https://github.com/formio/uswds
Provides HTML markup for accessible forms.
Accessibility Module
Provides overrides for formio.js renderer and builder.
Cuts down options within the Form.io Portal Form Builder to avoid components for which accessibility is not supported.
Includes Builder markup overrides to make the builder accessible (keyboard accessibility, accessible drag-n-drop functionality, additional screen reader announcements upon user actions).
Handles dynamic changes on the form and during building a form.
When customers utilize BOTH USWDS + VPAT for embedded forms within their applications, they receive the following features:
Features coming from the Form.io USWDS templates (#2 above):
Proper HTML markup (every form field needs an associated label).
Aria-attributes such as
aria-describedby
,aria-labelledby
, etc.Additional messages for sighted users (e.g. allowed file types for File component).
Features coming from the Form.io VPAT module (#3 above):
Screen readers messages upon user action (File, Wizard components).
Focus behavior handling (File, Wizard, Panel components).
Dynamic change of aria-attributes (all form fields).
Validation messages handling (all form fields).
Special styles for invalid fields (all form fields).
Additional Features coming from using the combined Form.io USWDS+VPAT modules:
Accessible tooltips.
Accessible Date/Time component.
Ability to use accessible “Modal Edit” windows for components when being filled in by end users.
Each Form.io component is tested for accessibility compliance using standalone applications. To create accessible forms, we offer a form builder that includes only the components that were revised and designed in compliance with WCAG 2.1 standards
Accessible Form Manager
Repositories used:
https://github.com/formio/formmanager (also included in standard FMGR)
https://github.com/formio/angular (also included in standard FMGR)
https://github.com/formio/formio.js (also included in standard FMGR)
https://github.com/formio/uswds * (only included in Accessible FMGR) * - this repositories have accessibility features listed above
How to enable the Accessible Form Manager Application:
To enable the Accessibility Compliance Module, the following environment variable will need to be included in your Enterprise Server as part of your deployed environment.
VPAT=true
How to Embed Accessible Forms that were built within the Accessible Form Manager Application into customer applications (with accessible templates and VPAT functionality included in the applications):
Repositories used:
To embed the “https://examples.form.io/example”
directly to a website the following code should be used.
Alternative Use Case: Embedding the Accessible Form Builder (commercial not OSS) directly within the customer application:
Repositories used:
An alternative way to use the Accessible form builder is to embed the Form.io Form Builder within the application using the following code.
Last updated