Form users must understand the following information in order to interact with accessible forms/flows.
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.
Note: If a section is expanded, tabbing will take you directly into the section's controls. Tabbing puts the focus on each tab of a tab control. If a tab is selected, it becomes the active tab, and its contents will be in the natural tab order.
|Enter key or the space bar|
|Space bar only|
|shift + right/arrow|
Note: The right/left arrow keys can also be used to cycle/select the options of a radio control.
|Alt + up/down arrows on a windows keyboard or option + up/down arrows for the Mac|
The behaviors described below require the designer to enable the form/flow Accessible property. See Designing Accessibility forms/flows.
The designer can optionally enable the Accessibility property on the form/flow. 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 internationalization. Designer can translate this string to the preferred language as part of the form/flow internalization process.
You will notice a Text box on the wet signature lightbox. Type your name, using the keyboard. Typed text will be entered into the signature area. Signature controls on mobile devices will not have the text entry field.
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.
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.
The second setting is in the Safari browser:
To make a form/flow accessible in the designers, check the Accessibility property on the form/flow 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.
designers are encouraged to use the Hint and Help as much as possible. Assistive technology communicates the label of the control, the current value of the control and any hint text. Help is accessed by pressing the F2 key.
Provide relevant alternative text for for image controls. Alternative text can be localized by the designer when internationalizing the form (or flow). 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.
When using signatures we recommend using Signed Sections with Text/Signatures Images as these are the easiest for people to use. If you choose to use a Wet Signature control, an additional Text field displays.
The Text field provides a text entry area where you can type your name using the keyboard. Typed text will be entered into the signature area.
Signature controls on mobile devices will not have the text entry field.
The Topaz Electronic signature pad, if properly configured, works well with Wet Signature controls in forms/flows designed for accessibility. Refer to this topic for the configuration information.
Using placeholders in accessible forms is not recommended as they may be read by assistive technology as "empty line".
Use the summary property of the table control to specify extra help text that will be announced by AT tools.