Appian Accessibility Conformance Report VPAT 508

VPAT® Version 2.1 – March 2018

Name of Product/Version: Appian 18.1

Platform: Web

Date: April 2018

Contact information: accessibility@appian.com

Evaluation Methods Used: Conformance to the listed accessibility standards has been evaluated by Appian using a combination of static analysis tools and manual testing with assistive technologies.

 

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ Level A   –   Yes  |   No

Level AA   –   Yes  |   No

Level AAA   –   Yes  |  No

Section 508 as published in 2017, at http://www.Section508.gov Yes  |  No
EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at http://mandate376.standards.eu/standard Yes  |  No

Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Supports with Exceptions: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.
  • Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.

 

WCAG 2.0 Report

Tables 1 and 2 also document conformance with:

  • EN 301 549:  Chapter 9 – Web, Chapter 10 – Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 – Non-Web Software (closed functionality).
  • Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.

Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

 

Table 1: Success Criteria, Level A

Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.1 (Web)
  • 10.2.1 (non-web document)
  • 11.2.1.1 (Software)
  • 11.2.2.1 (Closed Functionality Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses standard HTML and WAI-ARIA techniques for providing text equivalents of non-text elements. This includes the use of “alt” attributes for images and the use of “aria-label” or “aria-describedby” attributes for other visual elements.

The Appian user interface framework (“SAIL”) allows application designers to define a text-only representation of any UI if it is determined to be necessary for accessibility.

Some purely decorative elements that have no functional or informational purpose may not provide a text alternative.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.2 (Web)
  • 10.2.2 (non-web document)
  • 11.2.1.2 (Software)
  • 11.2.2.2.1 and 11.2.2.2.2 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product does not include audio or video content by default. However, application designers may choose to include video content in user interfaces that they design with Appian. In such cases, designers may include alternative representations (such as text transcripts) that present equivalent information to the videos.
1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.3 (Web)
  • 10.2.3 (non-web document)
  • 11.2.1.3 (Software)
  • 11.2.2.3 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Does Not Support The Appian product does not include audio or video content by default. However, application designers may choose to include video content in user interfaces that they design with Appian. In that case, Appian does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.4 (Web)
  • 10.2.4 (non-web document)
  • 11.2.1.4 (Software)
  • 11.2.2.4 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable The Appian product does not use synchronized media.
1.3.1 Info and Relationships (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.7 (Web)
  • 10.2.7 (non-web document)
  • 11.2.1.7 (Software)
  • 11.2.2.7 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.
1.3.2 Meaningful Sequence (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.8 (Web)
  • 10.2.8 (non-web document)
  • 11.2.1.8 (Software)
  • 11.2.2.8 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product generates semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls.
1.3.3 Sensory Characteristics  (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.9 (Web)
  • 10.2.9 (non-web document)
  • 11.2.1.9 (Software)
  • 11.2.2.9 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product does not depend solely on sensory characteristics such as shape, size, visual location, orientation, or sound to understand content.

For example, while labels and instructions display in close proximity to corresponding input elements, the Appian product also uses WAI-ARIA techniques to ensure that those relationships are available to Assistive Technologies.

Application designers may choose how to use sensory elements in user interfaces that they design with Appian. Appian provides capabilities for defining text alternatives of designer-specified content and specifying the overall layout.

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.10 (Web)
  • 10.2.10 (non-web document)
  • 11.2.1.10 (Software)
  • 11.2.2.10 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.

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.

1.4.2 Audio Control (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.11 (Web)
  • 10.2.11 (non-web document)
  • 11.2.1.11 (Software)
  • 11.2.2.11 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product does not include audio or video content by default. However, application designers may choose to include video content in user interfaces that they design with Appian. Appian provides capabilities for pausing and adjusting the volume of designer-specified video content.
2.1.1 Keyboard (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.15 (Web)
  • 10.2.15 (non-web document)
  • 11.2.1.15 (Software)
  • 11.2.2.15 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product is a web-based application that supports standard keyboard navigation and input functions (such as pressing [Tab] to move between input fields, pressing the arrow keys to move between list items, and pressing [Space] or [Enter] to make selections).
2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.16 (Web)
  • 10.2.16 (non-web document)
  • 11.2.1.16 (Software)
  • 11.2.2.16 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product is a web-based application that supports standard keyboard navigation and ensures that keyboard users cannot be trapped in a subset of content.
2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.17 (Web)
  • 10.2.17 (non-web document)
  • 11.2.1.17 (Software)
  • 11.2.2.17 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports with Exceptions The Appian product has a session timeout alert to notify users when a session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message and choose to extend their session.
2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.18 (Web)
  • 10.2.18 (non-web document)
  • 11.2.1.18 (Software)
  • 11.2.2.18 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable The Appian product does not include moving, blinking, scrolling, or auto-updating information.
2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.19 (Web)
  • 10.2.19 (non-web document)
  • 11.2.1.19 (Software)
  • 11.2.2.19 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable The Appian product does not use flashing interface elements.
2.4.1 Bypass Blocks (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.20 (Web)
  • 10.2.20 (non-web document) – Does not apply
  • 11.2.1.20 (Software) – Does not apply
  • 11.2.2.20 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports A hidden link (available to screen readers) allows users to jump to the main content of each page.
2.4.2 Page Titled (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.21 (Web)
  • 10.2.21 (non-web document)
  • 11.2.1.21 (Software) – Does not apply
  • 11.2.2.21 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Web pages within the Appian product have descriptive titles that indicate the topic or purpose of each page.
2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.22 (Web)
  • 10.2.22 (non-web document)
  • 11.2.1.22 (Software)
  • 11.2.2.22 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses a logical tab order through interactive elements such as links and form controls.

Appian also uses semantically correct markup, ensuring that the markup matches the visual presentation of content on the page.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.23 (Web)
  • 10.2.23 (non-web document)
  • 11.2.1.23 (Software)
  • 11.2.2.23 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses descriptive text or WAI-ARIA techniques, such as adding an “aria-label” attribute to table paging control icons, to identify the purpose of links.

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.

3.1.1 Language of Page (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.27 (Web)
  • 10.2.27 (non-web document)
  • 11.2.1.27 (Software)
  • 11.2.2.27 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses the language attribute on the HTML element to specify the default language of a page.
3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.29 (Web)
  • 10.2.29 (non-web document)
  • 11.2.1.29 (Software)
  • 11.2.2.29 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports When a component in an Appian user interface receives focus, it does not initiate a change of context.
3.2.2 On Input (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.30 (Web)
  • 10.2.30 (non-web document)
  • 11.2.1.30 (Software)
  • 11.2.2.30 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Changing the setting of a component in an Appian user interface does not initiate a change of context.
3.3.1 Error Identification (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.33 (Web)
  • 10.2.33 (non-web document)
  • 11.2.1.33 (Software)
  • 11.2.2.33 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Appian provides capabilities for specifying error text for user interface components configured by application designers with Appian.

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

3.3.2 Labels or Instructions (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.34 (Web)
  • 10.2.34 (non-web document)
  • 11.2.1.34 (Software)
  • 11.2.2.34 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Appian provides capabilities for specifying labels and instructions for user input components configured by application designers with Appian.

The Appian product uses standard HTML and WAI-ARIA attributes to associate labels and instructions to user interface elements. This includes the use of “aria-labelledby” and “aria-describedby” to describe relationships to Assistive Technologies.

4.1.1 Parsing (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.37 (Web)
  • 10.2.37 (non-web document)
  • 11.2.1.37 (Software)
  • 11.2.2.37 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses semantically-correct markup for all interface elements. The markup is programmatically generated to prevent parsing errors.
4.1.2 Name, Role, Value (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.38 (Web)
  • 10.2.38 (non-web document)
  • 11.2.1.38 (Software)
  • 11.2.2.38 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.5 (Web)
  • 10.2.5 (non-web document)
  • 11.2.1.5 (Software)
  • 11.2.2.5 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable The Appian product does not use synchronized media.
1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.6 (Web)
  • 10.2.6 (non-web document)
  • 11.2.1.6 (Software)
  • 11.2.2.6 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable The Appian product does not use synchronized media.
1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.12 (Web)
  • 10.2.12 (non-web document)
  • 11.2.1.12 (Software)
  • 11.2.2.12 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports with Exceptions The visual presentation of text in the Appian product provides sufficient contrast.

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

Placeholder text on login page does not meet necessary contrast requirements.

1.4.4 Resize text (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.13 (Web)
  • 10.2.13 (non-web document)
  • 11.2.1.13 (Software)
  • 11.2.2.13 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Appian product user interfaces support standard zoom capabilities built into modern web browsers and operating systems.
1.4.5 Images of Text (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.14 (Web)
  • 10.2.14 (non-web document)
  • 11.2.1.14 (Software)
  • 11.2.2.14 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product does not use images of text by default. Application designers may choose to include images of text in user interfaces that they design with Appian.
2.4.5 Multiple Ways (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.24 (Web)
  • 10.2.24 (non-web document) – Does not apply
  • 11.2.1.24 (Software) – Does not apply
  • 11.2.2.24 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports The Appian product provides capabilities for incorporating navigation links and search functions in user interfaces built with Appian. Application designers may choose to implement these techniques as they see fit.
2.4.6 Headings and Labels (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.25 (Web)
  • 10.2.25 (non-web document)
  • 11.2.1.25 (Software)
  • 11.2.2.25 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses semantically-correct markup for all interface elements, including headings and labels.

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

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.26 (Web)
  • 10.2.26 (non-web document)
  • 11.2.1.26 (Software)
  • 11.2.2.26 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product uses visual changes to elements to indicate the current position of focus.
3.1.2 Language of Parts (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.28 (Web)
  • 10.2.28 (non-web document)
  • 11.2.1.28 (Software) – Does not apply
  • 11.2.2.28 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Does Not Support In the Appian product, the language of a page can be programmatically determined. However, there is no mechanism to specify different languages for subsets of a page. Even though the language of different parts of a page cannot be programmatically determined, all content specified by application designers, regardless of language, renders in Appian user interfaces.
3.2.3 Consistent Navigation (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.31 (Web)
  • 10.2.31 (non-web document) – Does not apply
  • 11.2.1.31 (Software) – Does not apply
  • 11.2.2.31 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports The Appian product uses the same navigation mechanisms across pages.
3.2.4 Consistent Identification (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.32 (Web)
  • 10.2.32 (non-web document) – Does not apply
  • 11.2.1.32 (Software) – Does not apply
  • 11.2.2.32 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports The Appian user interface framework (“SAIL”) provides a standard component library for application designers, ensuring consistent functionality and presentation across pages.
3.3.3 Error Suggestion (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.35 (Web)
  • 10.2.35 (non-web document)
  • 11.2.1.35 (Software)
  • 11.2.2.35 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product provides suggestions for correcting errors such as identifying required fields using the “aria-required” attribute. Application designers may also choose to include supplemental text notifying users of form errors such as required fields that were not completed.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.36 (Web)
  • 10.2.36 (non-web document)
  • 11.2.1.36 (Software)
  • 11.2.2.36 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The Appian product provides capabilities for application designers to design their user interfaces for error prevention. Designers may choose to incorporate methods such as checking for input errors, ensuring that submissions are reversible, and allowing users to review and confirm information prior to submission.

Table 3: Success Criteria, Level AAA

Notes: The Appian product has not been evaluated for WCAG 2.0 Level AAA conformance.

 

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Supports The Appian product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.
302.2 With Limited Vision Supports The Appian product supports standard browser magnification and contrast adjustments.
302.3 Without Perception of Color Supports Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.
302.4 Without Hearing Not Applicable The Appian product does not include audio-only features that require hearing to be used.
302.5 With Limited Hearing Not Applicable The Appian product does not include audio-only features that require hearing to be used.
302.6 Without Speech Not Applicable The Appian product does not require speech input.
302.7 With Limited Manipulation Supports The Appian product supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions.
302.8 With Limited Reach and Strength Not Applicable
302.9 With Limited Language, Cognitive, and Learning Abilities Supports

Chapter 4: Hardware

Notes: The Appian product is a web software application and is not subject to the requirements of this section.

Chapter 5: Software

Criteria Conformance Level Remarks and Explanations
501.1 Scope – Incorporation of WCAG 2.0 AA See WCAG 2.0 section See information in WCAG section
502 Interoperability with Assistive Technology Heading cell – no response required Heading cell – no response required
502.2.1 User Control of Accessibility Features Not Applicable Appian is not considered platform software as defined by Section 508.
502.2.2 No Disruption of Accessibility Features Supports Appian is compatible with operating system and browser accessibility features configured by the user.
502.3 Accessibility Services Heading cell – no response required Heading cell – no response required
502.3.1 Object Information Supports The Appian product uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes.
502.3.2 Modification of Object Information Supports The Appian product uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies.
502.3.3 Row, Column, and Headers Supports with Exceptions The Appian product uses standard HTML attributes to define table structure and relationships, including column headers, to Assistive Technologies.

Appian does not provide capabilities for designating row headers for designer-specified table content.

502.3.4 Values Supports The Appian product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies.
502.3.5 Modification of Values Supports The Appian product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies.
502.3.6 Label Relationships Supports The Appian product uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes.
502.3.7 Hierarchical Relationships Supports The Appian product uses standard HTML markup to express hierarchical relationships.
502.3.8 Text Supports The Appian product renders strings as plain text values in HTML for maximum compatibility with assistive technologies.
502.3.9 Modification of Text Supports The Appian product renders strings as plain text values in HTML for maximum compatibility with assistive technologies.
502.3.10 List of Actions Supports The Appian product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies.
502.3.11 Actions on Objects Supports The Appian product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies.
502.3.12 Focus Cursor Supports The Appian product uses visual changes to elements to indicate the current position of focus.
502.3.13 Modification of Focus Cursor Supports The Appian product uses standard HTML elements with standard cursor controls for user input.
502.3.14 Event Notification Supports with Exceptions The Appian product has a session timeout alert to notify users when a session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message and choose to extend their session.
502.4 Platform Accessibility Features Not Applicable Appian is not considered platform software as defined by Section 508.
503 Applications Heading cell – no response required Heading cell – no response required
503.2 User Preferences Supports The Appian product respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, Appian user interfaces will display with high contrast.
503.3 Alternative User Interfaces Not Applicable Appian does not provide any alternative user interfaces that function as assistive technology.
503.4 User Controls for Captions and Audio Description Heading cell – no response required Heading cell – no response required
503.4.1 Caption Controls Does Not Support Appian does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.
503.4.2 Audio Description Controls Does Not Support Appian does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.
504 Authoring Tools Heading cell – no response required Heading cell – no response required
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) See WCAG 2.0 section See information in WCAG section
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Not Applicable
504.2.2 PDF Export Not Applicable
504.3 Prompts Not Applicable
504.4 Templates Not Applicable

Chapter 6: Support Documentation and Services

Notes: This report covers accessibility conformance for the Appian product and does not discuss Documentation or Support Services.

 

EN 301 549 Report

Chapter 4: 4.2 Functional Performance Statements (FPS)

Criteria Conformance Level Remarks and Explanations
4.2.1 Usage without vision Supports The Appian product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies
4.2.2 Usage with limited vision Supports The Appian product supports standard browser magnification and contrast adjustments
4.2.3 Usage without perception of colour Supports Colour is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.
4.2.4 Usage without hearing Not Applicable The Appian product does not include audio-only features that require hearing to be used
4.2.5 Usage with limited hearing Not Applicable The Appian product does not include audio-only features that require hearing to be used
4.2.6 Usage without vocal capability Not Applicable The Appian product does not require speech input
4.2.7 Usage with limited manipulation or strength Supports The Appian product supports standard input mechanisms such as user-provided keyboards and pointing devices
4.2.8 Usage with limited reach Not Applicable
4.2.9 Minimize photosensitive seizure triggers Supports The Appian product does not include visual features with flashing that could trigger seizures
4.2.10 Usage with limited cognition Supports Appian uses a logical focus order, and provides capabilities for specifying error text for user interface components configured by application designers
4.2.11 Privacy Supports The Appian product does not impede usage of standard privacy controls alongside assistive technologies. For example, users can connect a headset for private listening to screen reader announcements.

Chapter 5: Generic Requirements

Notes: The Appian product supports standard assistive technologies and is therefore not subject to the Closed Functionality criteria described in this Chapter.

Chapter 6: ICT with Two-Way Voice Communication

Notes: The Appian product does not offer two-way voice communication and is therefore not subject to the requirements of this section.

Chapter 7: ICT with Video Capabilities

Notes: The Appian product does not include video content. However, application designers may choose to include video content in user interfaces that they design with Appian. Appian does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.

Criteria Conformance Level Remarks and Explanations
7.1 Caption processing technology Heading cell – no response required Heading cell – no response required
7.1.1 Captioning playback Does Not Support
7.1.2 Captioning synchronization Does Not Support
7.1.3 Preservation of captioning Does Not Support
7.2.1 Audio description playback Does Not Support
7.2.2 Audio description synchronization Does Not Support
7.2.3 Preservation of audio description Does Not Support
7.3 User controls for captions and audio description Does Not Support

Chapter 8: Hardware

Notes: The Appian product is a web software application and is not subject to the requirements of this section.

Chapter 9: Web (see WCAG 2.0 section)

Chapter 10: Non-web Documents

Notes: The Appian product does not include non-web documents and is therefore not subject to the requirements of this section.

Chapter 11: Software

Criteria Conformance Level Remarks and Explanations
11.2.1 Software success criteria (excluding closed functionality) See WCAG 2.0 section See information in WCAG section
11.2.2 Software success criteria (closed functionality) See WCAG 2.0 section See information in WCAG section
11.3 Interoperability with assistive technology Heading cell – no response required Heading cell – no response required
11.3.1 Closed functionality (informative) Heading cell – no response required Heading cell – no response required
11.3.2 Accessibility services Heading cell – no response required Heading cell – no response required
11.3.2.1 Platform accessibility service support for software that provides a user interface See 11.3.2.5 through 11.3.2.17 See information in 11.3.2.5 through 11.3.2.17
11.3.2.2 Platform accessibility service support for assistive technologies See 11.3.2.5 through 11.3.2.17 See information in 11.3.2.5 through 11.3.2.17
11.3.2.3 Use of accessibility services Supports Appian uses standard platform accessibility services.
11.3.2.4 Assistive technology Not Applicable The appian product is not itself an assistive technology.
11.3.2.5 Object information Supports The Appian product uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes.
11.3.2.6 Row, column, and headers Supports with Exceptions The Appian product uses standard HTML attributes to define table structure and relationships, including column headers, to Assistive Technologies.

Appian does not provide capabilities for designating row headers for designer-specified table content.

11.3.2.7 Values Supports
11.3.2.8 Label relationships Supports The Appian product uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes.
11.3.2.9 Parent-child relationships Supports
11.3.2.10 Text Supports
11.3.2.11 List of available actions Supports
11.3.2.12 Execution of available actions Supports
11.3.2.13 Tracking of focus and selection attributes Supports
11.3.2.14 Modification of focus and selection attributes Supports
11.3.2.15 Change notification Supports
11.3.2.16 Modifications of states and properties Supports
11.3.2.17 Modifications of values and text Supports
11.4 Documented accessibility usage Heading cell – no response required Heading cell – no response required
11.4.1 User control of accessibility features Not Applicable Appian is not considered platform software as defined by EN 301 549.
11.4.2 No disruption of accessibility features Supports
11.5 User preferences Supports The Appian product respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, Appian user interfaces will display with high contrast.