Accessibility Compliance Module

Overview

Forms necessarily require a degree of end-user interaction, which highlights the need to make that interaction accessible. Applications that require compliance with various accessibility standards and guidelines must be thoughtful about the design of the forms and the way those forms are presented within the application. Simply using form components rated to be compliant with accessibility standards does not ensure that the whole form or broader application is accessible. Application developers must evaluate the finished product holistically.

Form.io offers a variety of tools and best practices through the entire platform to support developers in implementing accessible applications.

Standards, Tools, and Templates

There are many standards used to evaluate the accessibility of an application. One of the most common standards is the Web Content Accessibility Guidelines, published by the World Wide Web Consortium (W3C). The current standard is WCAG 2.1.

WCAG 2.1 evaluates web accessibility based on several principles. When a Form.io component is described as meeting WCAG 2.1 compliant it means that component, when used according to best practices, will not interfere with a web applications WCAG 2.1 rating.

Additionally, the United States General Service Administration developed the US Web Design System (USWDS), a collection of standardized UI components and visual styles, to provide developers with a number of resources to aid in delivering accessible web applications and services. Form.io offers a USWDS template that renders form using markup and classes that are compatible with USWDS standards.

The following sections describe the role each component of the Form.io Platform plays in enabling developers to deliver an accessible application.

Form Builder

Each Form.io component is evaluated for for accessibility compliance based on how to component is presented within a standalone application. To create accessible forms, Form.io offers an accessibility-focused version of the form builder that includes only the components that that comply with WCAG 2.1 standards.

When building forms using the Form Manager application, the Form Builder will automatically restrict non-accessible components and settings allowing the user to create fully accessible forms.

When building forms using the Developer Portal Form Builder, the following components met WCAG 2.1 accessibility standard during testing, and may be used to create fully accessible forms:

Basic
Advanced
Layout
Data
Premium

Text Field

Email

HTML

Hidden

Data Source

Text Area

URL

Content

Container

File

Number

Phone Number

Columns

Review Page

Password

Date & Time

Field Set

Checkbox

Day

Panel

Select Box

Time

Table

Select

Currency

Well

Radio

Button

A selection of components may present elements or functionality that do not comply with accessibility standards. The following components are not included in the Accessibility Compliance Module, and should not be used on forms where access by a broad audience with varying abilities is a priority:

Components with limited accessibility
  • Tags

  • Address

  • Survey

  • Tabs

  • Data Map

  • DataGrid

  • EditGrid

  • CAPTCHA

  • Nested Form

  • Sketchpad

  • Tagpad

  • 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)

Accessibility Features

  1. Accessible Form Manager

  2. Accessibility Templates (USWDS)

  3. 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):

  1. Proper HTML markup (every form field needs an associated label).

  2. Aria-attributes such as aria-describedby, aria-labelledby, etc.

  3. Additional messages for sighted users (e.g. allowed file types for File component).

Features coming from the Form.io VPAT module (#3 above):

  1. Screen readers messages upon user action (File, Wizard components).

  2. Focus behavior handling (File, Wizard, Panel components).

  3. Dynamic change of aria-attributes (all Form fields).

  4. Validation message handling (all Form fields).

  5. Special styles for invalid fields (all Form fields).

Additional Features coming from using the combined Form.io USWDS+VPAT modules:

  1. Accessible tooltips.

  2. Accessible Date/Time component.

  3. Ability to use accessible “Modal Edit” windows for components when being filled in by end users.

Accessible Form Manager

Repositories used:

  1. https://github.com/formio/formmanager (also included in standard FMGR)

  2. https://github.com/formio/angular (also included in standard FMGR)

  3. https://github.com/formio/formio.js (also included in standard FMGR)

  4. 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.

<html>
    <head>
        <meta charset="utf-8">
        <link rel="stylesheet" href="https://cdn.form.io/formiojs/formio.full.min.css">
        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/uswds/2.12.0/css/uswds.min.css">
        <link rel="stylesheet" href="dist/uswds.css">
        <script src="https://cdn.form.io/formiojs/formio.full.min.js"></script>
        <script src="dist/uswds.js"></script>
        <script src="dist/vpat.js"></script>
    </head>
    <body>
        <div id="formio"></div>
        <script type="text/javascript">
            Formio.use(uswds);
            Formio.use(vpat);
            Formio.createForm(document.getElementById('formio'), 'https://examples.form.io/example');
        </script>
    </body>
</html>

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.

<html>
    <head>
        <meta charset="utf-8">
        <link rel="stylesheet" href="https://cdn.form.io/formiojs/formio.full.min.css">
        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/uswds/2.12.0/css/uswds.min.css">
        <link rel="stylesheet" href="dist/uswds.css">
        <script src="https://cdn.form.io/formiojs/formio.full.min.js"></script>
        <script src="dist/uswds.js"></script>
        <script src="dist/vpat.js"></script>
    </head>
    <body>
        <div id="builder"></div>
        <script type="text/javascript">
            Formio.use(uswds);
            Formio.use(vpat);
            Formio.builder(document.getElementById('builder'));
        </script>
    </body>
</html>

Last updated

Was this helpful?