Related Topics
This principle relates to how user interface components and navigation operate.
2.1.1 Keyboard
Level A - All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
Process Director uses HTML controls and links for all form controls. All user-acessible objects are navigable via keyboard, e.g., users can use the tab key to navigate from one control to the next. The path of the user's movement is controlled by the location of the control on the form. Navigation operates from left to right and from top to bottom for browsers that have European language settings, and from right to left and top to bottom for other browser language settings. Additionally, the use of the Set Focus Custom Task enables you to specify a custom tab order, if you desire, though this is generally not necessary in the context of a form, which generally has a logical structure to begin with, and corresponds with the natural reading order of the specified culture.
2.1.2 No Keyboard Trap
Level A - If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Note 1: Since any content that doesn't meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion.
Though all controls on a form are keyboard navigable automatically through a set tab order in Process Director, it is possible for you to create a keyboard trap when using the Set Focus Custom Task. For instance, you can set the focus to field 3 when a customer completes field 1, then, in field 3, set the focus back to field one. This would create a never-ending tab cycle between field 1 and field 3, thus creating a keyboard trap, requiring the user to use the mouse to navigate to a different field. You should, as a best practice, extensively test any use of the Set Focus Custom Task to ensure you don't create a keyboard trap.
2.1.3 Keyboard (No Exception)
Level AAA - All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Process Director's tab order is generally compliant with this specification, though, as mentioned in 1.2.1, above, you can, as a designer, break it.
2.1.4 Character Key Shortcuts
Level A- If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
Turn off: A mechanism is available to turn the shortcut off;
Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
This is generally not relevant to Process Director.
Guideline 2.2 – Enough Time
Provide users enough time to read and use content.
2.2.1 - Timing Adjustable
Level A - For each time limit that is set by the content, at least one of the following is true:
Turn off: The user is allowed to turn off the time limit before encountering it; or
Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
Essential Exception: The time limit is essential and extending it would invalidate the Activity; or
20 Hour Exception: The time limit is longer than 20 hours.
This is generally not relevant to Process Director forms, as they aren't content-timed. This may be relevant to Knowledge Views, however, which do have a Automatically refresh results (in seconds) property available on the Configure tab of the Knowledge View Definition. As a best practice, ensure that you don't impose automatic refreshes on Knowledge Views unless it is essential for real-time event viewing.
2.2.2 Pause, Stop, Hide
Level A - For moving, blinking, scrolling, or auto-updating information, all of the following are true:
Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an Activity where it is essential; and
Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an Activity where it is essential.
This is generally not relevant to Process Director.
2.2.3 No Timing
Level AAA - Timing isn't an essential part of the event or Activity presented by the content, except for non-interactive synchronized media and real-time events.
Process Director is generally compliant with the specification, unless an automatic refresh is intentionally implemented by the designer, as in the case of Knowledge Views, as mentioned in 2.2.1, above.
2.2.4 Interruptions
Level AAA - Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Process Director is generally compliant with this specification, as users control the timing of data submission by manual action.
2.2.5 Re-authenticating
Level AAA - When an authenticated session expires, the user can continue the Activity without loss of data after re-authenticating.
Reauthentication isn't required in process Director by default, though designers can impose it. For example, in the Advanced tab of a User Timeline Activity, there is a Re-authenticate users property that can be set to require a user to reauthenticate prior to performing an Activity, but this reauthentication occurs before the data entry session is invoked. While it is possible to set up more onerous reauthentication requirements outside of Process Director, i.e., at the network security level, and Process Director will respect those requirements, Process Director doesn't, by default, require reauthentication or time users out.
2.2.6 Timeouts
Level AAA - Users are warned of the duration of any activity that could cause data loss, unless the data is preserved for more than 20 hours when the user doesn't take any actions.
As mentioned in 2.2.5, above, this isn't generally relevant to Process Director.
Guideline 2.3 – Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
2.3.1 Three Flashes or Below Threshold
Level A - Web pages don't contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
As a best practice, designers should never include such elements in an object viewable by end users.
2.3.2 Three Flashes
Level AAA - Web pages don't contain anything that flashes more than three times in any one second period.
As a best practice, designers should never include such elements in an object viewable by end users.
2.3.3 Animation from Interactions
Level AAA - Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
As a best practice, designers should never include such elements in an object viewable by end users.
Guideline 2.4 – Navigable
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks
Level A - A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
While it's difficult to think of a use case in which this might be relevant, the Section and Embedded Section controls can be used to enable users to show or hide repeated blocks of content, as a best practice.
2.4.2 Page Titled
Level A - Web pages have titles that describe topic or purpose.
All user-viewable objects in Process Director have an instantiated name property that can be customized. This instance name serves as the page title when displayed to end users. As a best practice, designers should provide the appropriate instance names for every object. By default, when an object is created, a generic instance name is created for that object. For example, when creating a new form definition, the default Instantiated Form Name is "{FORM_DEF_NAME} Submitted On {CREATE_DATE}". When a new instance of a form definition named "Vacation Request" is created on 1 January, 2020, the user will see the title of the page as "Vacation Request Submitted on 1/1/2020".
2.4.3 Focus Order
Level A - If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
This specification is generally covered b the answers provided in 2.2.1-2.2.3 above, along with the same caveat that the use of the Set Focus Custom Task requires extensive testing to ensure that the focus is properly navigable by end users.
2.4.4 Link Purpose (In Context)
Level A - The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
As a best practice, designers creating hyperlinks using the Hotlink control, or manually creating hyperlinks in the raw HTML of an HTML control, should comply with this requirement, so that end user know the context and purpose of the link before clicking it.
2.4.5 Multiple Ways
Level AA - More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
In addition to the links provided to objects in the user's Task List, or in the Forms I can Submit Knowledge View, designer should, as a best practice, incorporate navigation buttons and/or dashboard/workspace links to all forms or other objects to which users have access. Workspace, dashboard, and Desktop interface links are fully configurable by designers.
2.4.6 Headings and Labels
Level AA - Headings and labels describe topic or purpose.
In addition to the automatic heading incorporated int Process Director's Section controls, The Online Form Designer also incorporates Header formatting for other content. As a best practice, designers should ensure that all heading and labels are appropriately descriptive.
2.4.7 Focus Visible
Level AA - Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Process Director is generally compliant with this specification, and highlights the field/control that has the focus when using keyboard navigation, i.e., tabbing between controls.
Guideline 2.5 – Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures
Level A - All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
This is generally not relevant to Process Director.
2.5.2 Pointer Cancellation
Level A - For functionality that can be operated using a single pointer, at least one of the following is true:
No Down-Event: The down-event of the pointer isn't used to execute any part of the function;
Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
Up Reversal: The up-event reverses any outcome of the preceding down-event;
Essential: Completing the function on the down-event is essential.
This is generally not relevant to Process Director.
2.5.3 - Label in Name
Level A - For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
This is generally not relevant to Process Director, as all labels are text-based.
2.5.4 Motion Actuation
Level A - Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation.
This is generally not relevant to Process Director.
2.5.5 Target Size
Level AA - The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:
Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
Inline: The target is in a sentence or block of text;
User Agent Control: The size of the target is determined by the user agent and isn't modified by the author;
Essential: A particular presentation of the target is essential to the information being conveyed.
As a best practice, designers should ensure that user interface targets are sized appropriately.
Other Accessibility Principles
Principle 1 - Perceivable: This principle relates to making information and user interface components presentable to users in ways they can perceive.
Principle 3 - Understandable: This principle relates to making information and the operation of the user interface understandable to users.
Principle 4 - Robust: This principle relates to making content robust enough to be interpreted by a wide variety of user agents, including assistive technologies.
Documentation Feedback and Questions
If you notice some way that this document can be improved, we're happy to hear your suggestions. Similarly, if you can't find an answer you're looking for, ask it via feedback. Simply click on the button below to provide us with your feedback or ask a question. Please remember, though, that not every issue can be addressed through documentation. So, if you have a specific technical issue with Process Director, please open a support ticket.
