Appian Accessibility Conformance Report

Also applies to:

EN 301 549 Criteria

• 9.1.1.1 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian platform sets text alternatives for some non-text content by default using  HTML and ARIA techniques.

The Appian user interface framework (“SAIL”) allows application designers to define text alternatives for non-text content.

Exceptions:

• Captions set for image fields are not announced by screen readers when a text alternative is provided for the image or when the image is used in a link.

• Icons used in tokens created by Picker components  that identify the entity as a group or a user have no text alternative.

• The Appian logo graphic has an incorrect text alternative of "logo".

• CSS background images are used to convey the purpose of grid pagination controls.

Also applies to:

EN 301 549 Criteria

• 9.1.2.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.1.2.2 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian is not multimedia creation/editing software. However, content authors can include prerecorded multimedia presentations that have transcripts embedded in the video track of the presentation (open captions).

Exception:

• The media player used by Appian does not have a control that allows users to turn closed captions on and off for captions that are not embedded in the presentation video track.

Also applies to:

EN 301 549 Criteria

• 9.1.2.3 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.1.3.1 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian product uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.

Exceptions:

• The grid column header for cells that contain a token from a selected picker value is not announced by screen readers when the token receives keyboard focus.

• Newly-served content in chained interfaces that behave as single-page applications is not identified by screen readers.

• Browser component node elements (tree) are not ordered correctly in the rendered DOM.

• Screen readers do not announce the single or first option value returned from searchable Picker components when they are initially navigated to.
• Screen readers announce cells in sortable grid columns as being sortable but this function cannot be performed within the cell.
• Selectable grids that use the checkbox selection style have an incorrect column header value for the column that contains row selection checkboxes.

Also applies to:

EN 301 549 Criteria

• 9.1.3.2 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian product generates semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls.

Exceptions:

• Browser component child node elements are read by screen readers in an illogical order.
• Activating a record view tab causes a screen reader to begin reading at the beginning of the interface when Browse mode is invoked after tab activation.
• Activating a record action menu button causes a screen reader to begin reading at the beginning of the interface when securityOnDemand is enabled.

Also applies to:

EN 301 549 Criteria

• 9.1.3.3 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.1.4.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Application designers may choose how to use color in user interfaces that they design with Appian. Appian provides capabilities for defining text alternatives of designer-specified content.

Also applies to:

EN 301 549 Criteria

• 9.1.4.2 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.2.1.1 (Web)

Revised Section 508

• 501 (Web)(Software)

All functionality of the Appian product is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Exception:

• When multiple tokens are present from Picker component selections, attempting to remove the first tokens (leftmost) in the token list with the keyboard removes the last (rightmost) token in the list when using a screen reader.

Also applies to:

EN 301 549 Criteria

• 9.2.1.2 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.2.1.4 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.2.2.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.2.2.2 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.2.3.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.2.4.1 (Web)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software

The Appian product uses a skip link to bypass repeated navigation links  and has ARIA landmarks defined. In addition, content authors can create semantic page headings with appropriate heading levels.

Exception:

• The skip link does not correctly move virtual focus. This impacts screen reader users who continue navigation in browse mode after activating the link.

Also applies to:

EN 301 549 Criteria

• 9.2.4.2 (Web)

Revised Section 508

• 501 (Web)(Software)

Web pages within the Appian product have descriptive titles that indicate the topic or purpose of each page.

Exception:

• SAIL wizards and some chained tasks do not update the document title for each interface presented in the wizard or task.

Also applies to:

EN 301 549 Criteria

• 9.2.4.3 (Web)

Revised Section 508

• 501 (Web)(Software)

Focusable components receive focus in an order that preserves meaning and operability.

Exceptions:

• Tokens that are created from Picker component selections are removed from the focus order when the first token is navigated to with the keyboard and the maximum number of tokens have been created.

• Items in the option list produced by activating a Picker component are not accessed in a logical order when using swipe gestures on a mobile device.

• Items in the Time widget option list are not accessed in a logical order when using swipe gestures on a mobile device.

• Keyboard focus is lost when activating the First and Last page grid pagination controls.

• Browser node elements have an incorrect tab order.

• The pane layout is included in the tab order when actionable controls are present within the pane.

Also applies to:

EN 301 549 Criteria

• 9.2.4.4 (Web)

Revised Section 508

• 501 (Web)(Software)

Links generated by the Appian product use descriptive text to identify the purpose  of links. Where links can contain images, Appian allows for the inclusion of text in the link or a text alternative for the image.

Application designers may choose to include links in user interfaces that they design with Appian. Appian provides capabilities for defining the text of designer-specified link content. Designers can also provide visually-hidden text to links to provide additional context for screen reader users.

Also applies to:

EN 301 549 Criteria

• 9.2.5.1 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.2.5.2 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.2.5.3 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.2.5.4 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.3.1.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.3.2.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.3.2.2 (Web)

Revised Section 508

• 501 (Web)(Software)

Changing the setting of most components in an Appian user interface does not initiate a change of context.

Exception:

• Activating a record view tab causes a screen reader virtual cursor to be repositioned at the beginning of the interface.

Also applies to:

EN 301 549 Criteria

• 9.3.3.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Appian provides capabilities for specifying error message text for user interface components configured by application designers.

Additionally, the Appian product uses the aria-invalid attribute to flag inputs with errors and relay this information to Assistive Technologies.

Exceptions:

• Errors displayed when submitting the Change Password form are not announced by screen readers on form submission.

• Invalid form fields in the Change Password form are not programmatically indicated as being invalid.

• Grid field error messaging requires mouse and keyboard focus to expose error messages.

Also applies to:

EN 301 549 Criteria

• 9.3.3.2 (Web)

Revised Section 508

• 501 (Web)(Software)

Appian provides capabilities for specifying labels and instructions for user input components configured by application designers.

The Appian product uses standard HTML and WAI-ARIA attributes to associate labels and instructions with user interface elements. 

Exceptions:

• The login page uses only placeholder text for form field labels.

• Instructions provided for rich text links are not programmatically associated with the link

4.1.1 Parsing (Level A)

Also applies to:

WCAG 2.0 and 2.1 - Always supports

WCAG 2.2 (obsolete and removed) - Does not apply

Also applies to:

EN 301 549 Criteria

• 9.4.1.1 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.4.1.2 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.

The date picker is appropriately defined as a labeled application. Because of support-level variations of Windows screen readers, additional instructions for navigation of the component are added for screen reader users.

Exceptions:

• The inputs used in the date time component have the same programmatic label.

• Sortable grid column headers have an invalid defined role.

• Browser component nodes have an undefined role and state.

• The hierarchy tree and org chart components are hidden from assistive technology and have no programmatic role and state defined.

• The screen reader announcement of the dynamic state change of a card choice component is overridden by the grid alert announcement when the card choice applies a grid filter that returns no records.

• The checkbox used to select all rows in selectable grids that use the selection style of checkbox performs no function and is not programmatically indicated as being disabled.

• Screen readers announce cells in sortable grid columns as being sortable but this function cannot be performed within the cell.

• The visible instructions for the Username input in the Forgot Password interface are not programmatically associated with the input.

• The application loading bar and its progress is not indicated to assistive technology in Appian Portals (does not apply to Sites).

• Invalid form fields in the Change Password form are not programmatically indicated as being invalid.

• Form fields in the Change Password form are not programmatically indicated as being required.

• Some screen readers do not indicate grid rows as being selected when the row highlight selection style is used.

• The error state and error message used for the card choice component are not programmatically associated with the card choice group label.
• Items in record action menus are not announced by screen readers as they are navigated to.

Also applies to:

EN 301 549 Criteria

• 9.1.2.4 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.1.2.5 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian product does not include audio or video content by default. However, application designers may choose to include synchronized media content in user interfaces that they design with Appian. In such cases, content authors have the ability to use prerecorded media that has audio descriptions included in the audio track. 

Exception: 

• The media player provided by Appian does not have a control that can enable audio description.

Also applies to:

EN 301 549 Criteria

• 9.1.3.4 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.1.3.5 (Web)

Revised Section 508 – Does not apply

Appian provides a mechanism to indicate the purpose of each input field that gathers user information in a programmatically identifiable way. Because of the large number of possible autocomplete values, values that are available for Appian developers to use are based on browser compatibility and use cases.

Also applies to:

EN 301 549 Criteria

• 9.1.4.3 (Web)

Revised Section 508

• 501 (Web)(Software)

Administrators may configure custom color schemes for the Appian product. Any web-supported color scheme may be selected, allowing for satisfactory contrast requirements.

Also applies to:

EN 301 549 Criteria

• 9.1.4.4 (Web)

Revised Section 508

• 501 (Web)(Software)

Appian product user interfaces support standard zoom capabilities built into modern web browsers and operating systems.

Also applies to:

EN 301 549 Criteria

• 9.1.4.5 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.1.4.10 (Web)

Revised Section 508 – Does not apply

Appian user interfaces reflow to fit the width of the window.

Exception:

• Some list options in dropdown components are not visible and cannot be scrolled into view when content is magnified.

Also applies to:

EN 301 549 Criteria

• 9.1.4.11 (Web)

Revised Section 508 – Does not apply

The Appian platform provides a mechanism to allow users to modify their display to ensure non-text content provides sufficient contrast.

Exception:

• On the login screen, input textbox borders have insufficient color contrast (not configurable within user accessibility settings).

Also applies to:

EN 301 549 Criteria

• 9.1.4.12 (Web)

Revised Section 508 – Does not apply

Also applies to:

EN 301 549 Criteria

• 9.1.4.13 (Web)

Revised Section 508 – Does not apply

When a component in an Appian user interface triggers additional content to become visible, that content is dismissible, hoverable, and persistent.

Exception:

• Hover cards that are produced when hovering over a user avatar or user name link cannot be dismissed with the Escape key.

Also applies to:

EN 301 549 Criteria

• 9.2.4.5 (Web)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software

Also applies to:

EN 301 549 Criteria

• 9.2.4.6 (Web)

Revised Section 508

• 501 (Web)(Software)

Heading and label text in Appian user interfaces are specified by application designers. Appian provides capabilities for defining descriptive headings and labels.

Also applies to:

EN 301 549 Criteria

• 9.2.4.7 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian product uses visual changes to elements to indicate the current position of focus.

Exceptions:

• When using the VoiceOver screen reader on a Mac, the focus indicator for dropdown list options is incorrectly drawn around the entire listbox instead of being drawn around each option as it receives focus.

• The currently selected outermost hierarchy tree and org chart component node lacks indication of keyboard focus.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 - Does not apply

2.5.7 Dragging Movements (Level AA 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 - Does not apply

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 - Does not apply

Also applies to:

EN 301 549 Criteria

• 9.3.1.2 (Web)

Revised Section 508

• 501 (Web)(Software)

The Appian product does not support the programmatic language determination of passages or phrases in content.

Also applies to:

EN 301 549 Criteria

• 9.3.2.3 (Web)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software

Also applies to:

EN 301 549 Criteria

• 9.3.2.4 (Web)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software

Also applies to:

EN 301 549 Criteria

• 9.3.3.3 (Web)

Revised Section 508

• 501 (Web)(Software)

Also applies to:

EN 301 549 Criteria

• 9.3.3.4 (Web)

Revised Section 508

• 501 (Web)(Software)

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 - Does not apply

Also applies to:

EN 301 549 Criteria

• 9.4.1.3 (Web)

Revised Section 508 – Does not apply

The Appian product uses semantically-correct markup to allow assistive technologies to interpret platform status messages that do not receive focus.

Exception:

• System (platform-level) error messages are not announced by some screen readers when they appear.

Users with limited manipulation may encounter some content that may not be easily used with a keyboard or other pointer device and may not know where they are within content as noted in Table 1 and Table 2.

The Appian product supports standard input mechanisms such as user-provided keyboards, pointing devices and speech recognition. Usage of the product does not require reach or level of strength.

Users having limited language, cognitive, and learning abilities may encounter some content that  is difficult to perceive based on the order in which it can be accessed, some keyboard interaction patterns, and control names, roles, or states as noted in Table 1 and Table 2.