Note: Nintex Apps data centers are located in West US and Australia (AUS). In-region processing of Nintex Apps data is only available in these regions.
Nintex Apps VPAT for v2
The Voluntary Product Accessibility Template ( VPAT ) assists Federal contracting officials and other buyers in making preliminary assessments regarding the availability of commercial "Electronic and Information Technology" products and services with features that support accessibility.
Date: June 25, 2019
Version: 2.0
Name of Product: Nintex Apps API version 2 ( This VPAT covers runtime/user-facing applications built with the product. )
Contact for more Information: Jackson Alexander, Sr. Director of Product Experience
Summary Table
Section 1194.21 Software Applications and Operating Systems (Detail)
| Criteria | Supporting Features | Remarks |
|---|---|---|
| (a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. | Supported | Components are keyboard accessible, including navigation menus, links, and buttons. |
| (b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. | Supported | Skuid does not disable features of other applications. |
| (c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. | Supported | |
| (d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. | Supported | Application elements have associated "alt text" or "title metadata" and ARIA labels/descriptions, which can be accessed by Assistive Technology |
| (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. | Supported | |
| (f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. | Supported | Product supports standard text functions. |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported | Skuid application is rendered as a web page and responds as any web page in the operating system. |
| (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Supported | When developing with Skuid, builders can use alternatives to animation. |
| (i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Supported | Must be configured as part of the theme. |
| (j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. | Supported | Administrative customization supports the use of any RGB color. |
| (k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. | Not applicable | There are no flashing or blinking objects in product. |
| (l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | Supported |
Section 1194.22 Web-based Internet Information and Applications (Detail)
| Criteria | Supporting Features | Remarks |
|---|---|---|
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Supported | |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Supported | When developing with Skuid, builders can use alternatives to animation. |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Supported. | Themes allow full customization of color, font, underlining, etc. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supported | Document structure is enforced. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Supported | When developing with Skuid, builders can use alternative image map presentation options. |
| (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | Not applicable | Client-side image maps are not included in the product. |
| (g) Row and column headers shall be identified for data tables. | Supported | Columns are labeled, row headers are not. |
| (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | Not supported | |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | Supported | When developing with Skuid, builders can add titles and navigation for any elements added using frames. |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Supported | Product does not generate screen flicker. |
| (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. | Supported | When developing with Skuid, builders can include and link to accessible, text-only pages when necessary for compliance. |
| (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. | Supported | |
| (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l). | Not applicable | Currently, product does not require applets or plug-ins to function. |
| (n) When electronic forms are designed to be completed online, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | Supported | |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Not supported. | |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Not applicable | Product does not included timed activities. |
Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.
Section 1194.31 Functional Performance Criteria (Detail)
| Criteria | Supporting Features | Remarks |
|---|---|---|
| (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. | Supported | Screen readers are supported with embedded ARIA markups. |
| (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. | Supported | |
| (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided | Supported | Builders can use alternative audio presentation options when developing with Skuid. |
| (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. | Not applicable | Audio cues or content are not included in product. |
| (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. | Not applicable | Speech input is not required to use product. |
| (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. | Supported with exceptions | Users can navigate application menus, links, and most buttons, using keyboard keys. |
Section 1194.41 Information, Documentation, and Support (Detail)
| Criteria | Supporting Features | Remarks |
|---|---|---|
| (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge | Supported | Skuid's documentation is available online. Developers of applications built with Skuid are responsible for documentation for those applications. |
| (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. | Supported | The VPAT for Skuid API version 2 is available online. Developers of applications built with Skuid are responsible for VPATS for those applications. |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. | Unknown | Skuid employs Get Satisfaction for community support. Developers of applications built with Skuid are responsible for support services for those applications. |