Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Accessible forms/flows workflows can assist users with visual and motor impairments.

v6.1 can be used to build accessible forms/flows workflows that meet Section 508 and WCAG 2.0 accessibility standards. Note that of course, you can also build forms/flows that workflows that do not take advantage of
accessibility features. For Example, form controls that are missing informative labels and help, hint text will not pass accessibility certification.

Form designers are responsible for testing their own forms/flows workflows to verify that they pass their own certification process.

  • Frevvoproduct
     supports accessibility for use mode forms/flows workflows only
  • Accessibility will not be supported in this release for mobile devices, Task List and Spaces  

For users requiring assistive technology, 

 supports the following screen readers:

  • Mac OSX Voice Over on Safari only
  • JAWS for Windows on IE (10/11) 

When using JAWS, the latest version of IE (ie11 presently) is recommended for optimal results.

Assistive technology communicates the labels of form controls, the current value of the control, help text, and any hint text.    



Table of Contents

Using forms/



Form users must understand the following information in order to interact with accessible forms/flowsworkflows.

Keyboard Functions:

The following keyboard combinations are used when a user is not using a screen reader. If you are using a screen reader please read the documentation specific to your screen reader and see the topic Using Assistive Technology below.



The behaviors described below require the designer to enable the form/flow workflow Accessible property. See Designing Accessibility forms/flowsworkflows.


Required Controls

The designer can optionally enable the Accessibility property on the form/flowworkflow. When enabled, required fields display a asterisk.  If users move ahead from a required field without filling it, the error, "You can't leave this empty <control name>" displays. The translatable string, You\ can't\ leave\ this\ empty: is included in the downloaded locale file for form/flow workflow internationalization. Designer can translate this string to the preferred language as part of the form/flow workflow internalization process.

Wet Signature controls 


Using Assistive Technology

If you are using a screen reader please read the documentation specific to your screen reader. The only interaction that is specific to 

is that you press the F2 key to display or hear field help text. The help text will disappear from the screen when the user advances to the next control.


If you use a navigation shortcut key such as the 'F' key to move through the cells in a table, when using JAWS, the fields are announced with the row number and column. If you use the down arrow key (or up arrow to reverse) to navigate, JAWS does not announce row & column. This is a function of the JAWS reader and cannot be changed by frevvo.

Enabling full keyboard navigation on the Mac

If you are using the Safari and/or Firefox browsers on a Mac, there are two preferences that you must enable to allow full keyboard only navigation via the tab key.  Setting these options makes it possible for the user to tab to any control types, which are normally prevented by default.

The first setting is a system preference so it will affect most browsers you use on the Mac.

  1. Go to System Preferences and select the Keyboard option (it may be “Keyboard & Mouse” depending on your version of OS X).
  2. From within the Keyboard preferences, select the Shortcuts tab.
  3. Locate the Full keyboard access: In windows and dialogs, press Tab to move the keyboard focus between option, and select "All Controls.

The second setting is in the Safari browser:

  1. Go to Safari -> Preferences
  2. Under the Advanced tab, select the Press Tab to highlight each item on a webpage check box.

Designing Accessibility forms/



To make a form/flow workflow accessible in the designers, check the Accessibility property on the form/flow workflow properties panel. This property is by default unchecked and when checked enables specific advanced accessibility behavior. For Example, Required controls will include an asterisk in the label.


Provide relevant alternative text for for image controls. Alternative text can be localized by the designer when internationalizing the form (or flowworkflow).  Assistive Technology will communicate the value of the Alternative Text. This field is intentionally left blank in the designer so it will not be overlooked.


The Topaz Electronic signature pad, if properly configured, works well with Wet Signature controls in forms/flows workflows designed for accessibility. Refer to this topic for the configuration information.