MaestroThe UI design product. | Form BuilderPlatform Developer | 19.11 This feature was updated in 19.11.
Journey Maestro provides some basic, component-level accessibility automatically. For instance, linking a component’s label text with its input field. However, a Maestro Template Designer and Form Builder need to perform the following additional tasks to achieve maximum form's accessibility:
We recommend configuring as much accessibility features in a template as possible.
Let's look at each accessibility configuration in details.
This policy property defines how validation and navigation operates for the form as a whole. Sequential page navigation is better for accessibility as it provides a simpler experience where users navigate through the form sequentially, one page at a time, and does not allow them to progress until the current page passes validation.
Unconstrained page navigation allows the user to navigate to any page, in any order, which can be confusing particularly on mobile devices, and doesn't perform full form validation until they attempt to submit it from the final page. This can cause a potential problem that will be difficult to correct for multi-page forms.
To configure Sequential Page Navigation, select Form Options > Form - Policies > Validation Mode.
In this example, we use the Avalon template. The Maguire template has a slightly different form option's categories.
To configure page's headers, select Page > Properties > Display Text and use the Title Text and Subtitle Text fields.
In this example, the Tell us about you will be rendered as the
<h1> element. The Subtitle Text will be rendered as the
<h1> element as well.
To configure section's headers, select Section > Properties > Label. Also, use the Additional Text field to specify any extra content for a form user.
In this example, the About You label will be rendered as the
<h3> element, whilst the Additional Text will be rendered as the
When creating lists, it is important to ensure that the correct HTML mark-up is used so assistive technologies read the lists out properly. When copying and pasting content from external sources, such as Word Documents, the mark-up is often lost and replaced by characters representing the numbers or bullets in the list. Whilst visually this may look fine, the lack of correct HTML mark-up will prevent screen readers from interpreting the list as an HTML list.
The Maestro editor provides the built-in rich text editor so you can add lists.
To add a list HTML element, select Text Display > Label and click Insert / Remove Numbered List or Insert / Remove Bulleted List as required
Click Source to review the source code and verify that correct HTML mark-up is used:
Images can be one of the following:
Usually, it's up to a form developer to decide whether an image should be treated as decorative or informative.
To add an inattentive text to an image, select Image > Properties > Image > Alternative Text
Informative images should not be used as a background image as it is not possible to provide them with alternative text and some browsers remove background images when put in high contrast mode. It is fine to use decorative images as a background image.
To set up a background image, select Component > Styles > Background.
Fields that are not stand-alone and only make sense in the context of a group of fields should be contained within a Fieldset component. For instance, when using:
You should provide a meaningful description of the group in the Label of the Fieldset, which is a legend text and is displayed a heading. The legend text will be used by assistive technologies to inform the user of the context for fields within the fieldset. For instance, tabbing to a checkbox button whilst a screen-reader is running might inform the user that they are currently focused on a checkbox button with caption Email for the fieldset How would you like us to contact you?:
To set up a description, select Fieldset > Properties > Label:
Without the fieldset, the user would only be informed that they are focused on a checkbox button with caption Email which is clearly insufficient. To avoid repetition, the majority of assistive technology will only inform the user of the fieldset legend for the first field focused within the group, regardless of which field that is, namely, not necessarily the first field in the group by position.
The Radio Button Group component already includes fieldset so you don't need to add it.
For the sake of usability, labels should generally be placed above input fields. This is how Maestro's components are configured by default. You can, however, change the placement of a label to the left of an input field. This is typically done on receipts as a way of saving space. However, you can change label location to the left.
To change label location to the left, select Field > Properties > Layout > Label Placement Left.
Colors used in a form must meet accessibility requirements for contrast of foreground and background objects for partially sighted and color-blind users.
You can check your form using a contrast tool such as TPGi's Color Contrast Analyser.
We recommend adding a Label above the field, which is the default in Maestro, because it is best for accessibility as it keeps the caption closest to its field. In particular, this makes it easier for users of magnifier software to locate the field associated with a label without having to move the cursor too far and reduces the chances of finding the wrong field by mistake.
Top placement also provides the best scan line between captions and inputs for fields. A scan line refers to eye movement along a straight line as a sighted user browses a form or searches for a specific field. Other label placement results in additional, unnecessary movement as the sighted user’s eye jumps around between labels and inputs that are less aligned.
To clear the placeholder text, select Field > Properties > Accessibility > Placeholder Text.
Placeholder text is the light grey text that is displayed in a field until data is entered at which point it is removed.
Placeholder text is not accessibility compliant due to the lack of consistent support in assistive technologies. Some assistive technologies ignore placeholder text entirely. Some always notify the user of the placeholder text regardless of whether there is data in the field or not and makes no differentiation between the placeholder text versus the entered data.
Only a small proportion of assistive technologies do the correct thing in only notifying the user of the placeholder text when it is visible on-screen.
It can be tempting to hide the built-in field label and create a replacement with a separate text display component in order to achieve a layouts,such as a label, that is wider than its field.
Although, this approach may look identical on-screen to sighted users, this does not provide the browser functionality where selecting a label sets focus to its field.
To resolve the specific case of long labels, it is better for accessibility to use a combination of shortening the label, widening the component and moving non-critical information from the label to a popover tooltip or a message box located close to the component.
To edit component's label, select Component > Properties > Label.
Disabled form content is problematic for accessibility and should be avoided.
Typically, disabled content is visible on-screen for sighted users but not active and visually indicated as disabled with grey-out styling. Disabled content is not discoverable for users of assistive technology which results in a mismatch of information. For instance, in the case of disabling the continue button for a page until certain actions are performed a sighted user can see that the button is disabled and may be able to deduce that they need to perform an action before it will be enabled.
However, a user of assistive technologies will have no knowledge of the existence of the continue button at all which is likely to lead to confusion of what action is expected of them in order to progress.
In this case, it is better for all users to keep the continue button enabled and inform the user what is expected of them with error messaging if they attempt to progress without completing necessary actions.
The other common alternative approach to disabling components is to hide them.
aria-label HTML attribute allows you to provide an accessible name for an element so users of assistive technology will be able to recognize it. You should use
aria-label if the element doesn't have a visible name you can reference, for example,
aria-label="Submit my form". For more information, see ARIA (Accessible Rich Internet Applications) documentation and ARIA specification.
aria-label, select Component > Properties > Accessibility >Aria Label:
In this example, we use the Submit component with an empty label and an icon to show on a Submit button. After you publish the form, the
aria-label="Submit my form" property is added to the
<button> element so assistive technology, such as a screen reader, will interpret it accordingly.
Next, learn about rule templates and rule helpers in a form.