Appian allows designers to build applications that are accessible to all users, and validates its product features against the requirements of leading accessibility standards:
US Federal Government's Section 508 of the Rehabilitation Act of 1973 (January 2017 Refresh)
World Wide Web Consortium (W3C)'s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA
Given Appian's established accessibility conformance (with some exceptions), all submitted violations must be validated by the assessor prior to submission. Appian does not accept unvalidated results or direct output from automated scanners without additional validation. After the violation behavior has been manually tested, appropriate verification must be provided in a support case as specified in the Instructions section below. This ensures Appian has a thorough understanding of the violation being encountered so that we can compare it to expected behavior and determine the platform changes (if any) that need to be made to meet accessibility standards.
Note that for issues involving accessibility tools like screen readers, the issue MUST be encountered when using a screen reader. Many automated tests report accessibility violations based on the HTML code. However, an issue with the HTML does not always cause an issue with the screen reader.
When in doubt about whether a violation is valid, consider whether it impacts the understanding of the page for the following accessibility user groups:
For each violation, provide:
This article applies to all versions of Appian.
Last Reviewed: May 2020
© 2020 Appian. All rights reserved.