KB-2106 How to report accessibility violations

Elly Meng — Wed, 21 Jun 2023 21:54:53 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 6/21/2023 9:54:53 PM

Purpose

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.1 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 reported violations involving HTML, it MUST cause issues with the end user in some way (e.g. screen readers cannot announce a component correctly) in order to be an accessibility violation. Note that 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

Instructions

For each violation, please provide:

Impacted browser and (if applicable) screen reader version.
The number of the specific WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL for the page and a screenshot of the affected HTML element(s).
3. For issues related to Appian component configurations, provide the SAIL for the page containing the component, including the SAIL inside any custom rules (with sensitive information removed).
Justification for why the success criterion is being violated based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Mon, 20 Feb 2023 21:55:00 GMT

Revision 19 posted to Appian Knowledge Base by Elly Meng on 2/20/2023 9:55:00 PM

Purpose

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.1 Level AA

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

Instructions

For each violation, please provide:

Impacted browser and (if applicable) screen reader version.
The number of the specific WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL for the page and a screenshot of the affected HTML element(s).
3. For issues related to Appian component configurations, provide the SAIL for the page containing the component, including the SAIL inside any custom rules (with sensitive information removed).
Justification for why the success criterion is being violated based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Wed, 09 Feb 2022 17:15:26 GMT

Revision 18 posted to Appian Knowledge Base by Elly Meng on 2/9/2022 5:15:26 PM

Purpose

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.1 Level AA

When in doubt about whether a violation is valid, consider whether it impacts the understanwding 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

Instructions

For each violation, please provide:

Impacted browser and (if applicable) screen reader version.
The number of the specific WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL for the page and a screenshot of the affected HTML element(s).
3. For issues related to Appian component configurations, provide the SAIL for the page containing the component, including the SAIL inside any custom rules (with sensitive information removed).
Justification for why the success criterion is being violated based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Mon, 07 Feb 2022 16:20:26 GMT

Revision 17 posted to Appian Knowledge Base by Elly Meng on 2/7/2022 4:20:26 PM

Purpose

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

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

Instructions

For each violation, please provide:

Impacted browser and (if applicable) screen reader version.
The number of the specific WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL for the page and a screenshot of the affected HTML element(s).
3. For issues related to Appian component configurations, provide the SAIL for the page containing the component, including the SAIL inside any custom rules (with sensitive information removed).
Justification for why the success criterion is being violated based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Mon, 07 Feb 2022 16:05:28 GMT

Revision 16 posted to Appian Knowledge Base by Elly Meng on 2/7/2022 4:05:28 PM

Purpose

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

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

Instructions

For each violation, please provide:

Impacted browser and (if applicable) accessibility tool version.
The number of the specific WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL for the page and a screenshot of the affected HTML element(s).
3. For issues related to Appian component configurations, provide the SAIL for the page containing the component, including the SAIL inside any custom rules (with sensitive information removed).
Justification for why the success criterion is being violated based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Mon, 07 Feb 2022 16:04:07 GMT

Revision 15 posted to Appian Knowledge Base by Elly Meng on 2/7/2022 4:04:07 PM

Purpose

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

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

Instructions

For each violation, please provide:

Impacted browser and accessibility tool version.
The number of the WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL for the page and a screenshot of the affected HTML element(s).
3. For issues related to Appian component configurations, provide the SAIL for the page containing the component, including the SAIL inside any custom rules (with sensitive information removed).
Justification for why the success criterion is being violated based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Mon, 07 Feb 2022 15:56:38 GMT

Revision 14 posted to Appian Knowledge Base by Elly Meng on 2/7/2022 3:56:38 PM

Purpose

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

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

Instructions

For each violation, please provide:

Impacted browser and accessibility tool version.
The number of the WCAG success criterion being violated.
Appropriate verification of the experienced behavior.
1. For screen reader issues, provide a video capture (with audio) of what the screen reader announces. One of the following browser and screen reader combinations documented here must be used.
2. For HTML issues, provide the SAIL and the HTML for the affected component.
3. For issues related to Appian component configurations, provide the SAIL for the full page containing the component, including the SAIL inside any custom variables or rules (sensitive information may be removed).
An explanation for whether the violation is a requirement or a recommendation (advisory) based on the success criterion details.
(Self-managed-only) The version and hotfix for the affected site, as some issues have been resolved in specific hotfixes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2022

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Elly Meng — Tue, 16 Nov 2021 15:53:18 GMT

Revision 13 posted to Appian Knowledge Base by Elly Meng on 11/16/2021 3:53:18 PM

Purpose

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

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
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 Google Chrome
  2. JAWS for Microsoft Edge
  3. JAWS for Internet Explorer 11
  4. 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.
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(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

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

James Lee — Sun, 03 May 2020 16:52:53 GMT

Revision 12 posted to Appian Knowledge Base by James Lee on 5/3/2020 4:52:53 PM

Purpose

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

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
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.
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(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

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

KB-2106 How to report accessibility violations

Parmida Borhani — Thu, 09 Apr 2020 01:19:11 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 4/9/2020 1:19:11 AM

Purpose

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

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

DRAFT SP-4176 How to report accessibility violations

Parmida Borhani — Thu, 09 Apr 2020 01:18:12 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 4/9/2020 1:18:12 AM

Purpose

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

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

DRAFT SP-4176 How to report accessibility violations

Elly Meng — Wed, 08 Apr 2020 16:21:00 GMT

Revision 9 posted to Appian Knowledge Base by Elly Meng on 4/8/2020 4:21:00 PM

Purpose

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

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

SP-4176 How to report accessibility violations

Elly Meng — Wed, 08 Apr 2020 15:20:27 GMT

Revision 8 posted to Appian Knowledge Base by Elly Meng on 4/8/2020 3:20:27 PM

Purpose

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

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

SP-4176 How to report accessibility violations

Elly Meng — Wed, 08 Apr 2020 15:01:19 GMT

Revision 7 posted to Appian Knowledge Base by Elly Meng on 4/8/2020 3:01:19 PM

Purpose

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

As Appian is a WCAG 2.0 Level AA compliant platform (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.

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

SP-4176 How to report accessibility violations

Parmida Borhani — Tue, 07 Apr 2020 04:26:42 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 4/7/2020 4:26:42 AM

Purpose

Appian 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

As Appian is a WCAG 2.0 Level AA compliant platform, 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.

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

Instructions

For each violation, provide:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: reporting, How To, user interface, WCAG, 508, how-to, accessibility

SP-4176 How to report accessibility violations

Elly Meng — Mon, 06 Apr 2020 22:39:19 GMT

Revision 5 posted to Appian Knowledge Base by Elly Meng on 4/6/2020 10:39:19 PM

Purpose

Appian 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

As Appian is a WCAG 2.0 Level AA compliant platform, we ask that 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.

Please keep in mind 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, please 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

Instructions

For each violation, please provide the following:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: How To, user interface, accessibility

SP-4176 How to report accessibility violations

Elly Meng — Mon, 06 Apr 2020 17:31:31 GMT

Revision 4 posted to Appian Knowledge Base by Elly Meng on 4/6/2020 5:31:31 PM

Purpose

Appian 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

As Appian is a WCAG 2.0 Level AA compliant platform, we ask that when reporting an accessibility issue for a current feature, you must manually test the behavior of each violation and provide appropriate verification as specified in the Instructions section below. Appian needs a thorough understanding of the exact behavior encountered on your end so that we can compare it to the expected behavior and determine the necessary changes (if any) to meet accessibility standards.

Please keep in mind that for issues involving accessibility tools like screen readers, the issue MUST be encountered when using the screen reader. Many automated tests check for 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, please 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

Instructions

For each violation, please provide the following:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: accessibility

SP-4176 How to report accessibility violations

Elly Meng — Mon, 06 Apr 2020 17:31:02 GMT

Revision 3 posted to Appian Knowledge Base by Elly Meng on 4/6/2020 5:31:02 PM

Purpose

Appian 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

Please keep in mind that for issues involving accessibility tools like screen readers, the issue MUST be encountered when using the screen reader. Many automated tests check for accessibility violations using 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, please 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

Instructions

For each violation, please provide the following:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: accessibility

SP-4176 How to report accessibility violations

Elly Meng — Mon, 06 Apr 2020 17:30:12 GMT

Revision 2 posted to Appian Knowledge Base by Elly Meng on 4/6/2020 5:30:12 PM

Purpose

Appian 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

Please keep in mind that for issues involving accessibility tools like screen readers, the issue must be encountered when using the screen reader. Many automated tests check for accessibility violations using 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, please 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

Instructions

For each violation, please provide the following:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: accessibility

SP-4176 How to report accessibility violations

Elly Meng — Mon, 06 Apr 2020 17:28:35 GMT

Revision 1 posted to Appian Knowledge Base by Elly Meng on 4/6/2020 5:28:35 PM

Purpose

Appian 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

As Appian is a WCAG 2.0 Level AA compliant platform, we ask that when reporting an accessibility issue for a current feature, you must manually test the behavior of each violation and provide appropriate verification as specified in the Instructions section below. Appian needs to understand the exact behavior encountered on your end so that we can compare it to the expected behavior and determine the necessary changes (if any) to meet accessibility standards.

When in doubt about whether a violation is valid, please 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

Instructions

For each violation, please provide the following:

Impacted browser(s) and accessibility tool version(s).
The specific WCAG success criterion that is being violated in the Web Content Accessibility Guidelines linked above.
At least one of the following based on applicability:
1. A video capture (with audio) of the screen reader interacting with the object. Since it is not realistic for Appian to conform to all screen readers on the market, the following must be used:
  1. JAWS for Internet Explorer 11
  2. NVDA for Firefox
2. The HTML of the page containing the object
3. The SAIL of the page containing the object
Whether the violation is a requirement or an advisory (recommendation) based on the success criterion details.
(On-premise-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: April 2020

Tags: accessibility