KB-2106 How to report accessibility violations


Appian allows designers to build applications that are accessible to all users, and validates its product features against the requirements of leading accessibility standards:

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:

  • Visually compromised users who rely on screen readers or require resized text
  • Manually compromised users who rely on keyboards to tab through each page


For each violation, provide:

  1. Impacted browser(s) and accessibility tool version(s).
  2. The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
  3. Appropriate verification of the experienced behavior:
    1. For screen reader related issues, provide a video capture (with audio) of the screen reader interacting with the object. One of the following recommended combinations must be used:
      1. JAWS for Internet Explorer 11
      2. NVDA for Firefox
    2. For HTML-related issues, provide the HTML of the page containing the object.
    3. For issues related to Appian object configurations, provide the SAIL for the page containing the object, including the SAIL inside any custom variables or rules. Remove sensitive information from the objects before providing the verification.
  4. Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
  5. (Self-managed-only) The version and hotfix for the affected site, since some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2020