Voluntary Product Accessibility Template (VPAT)

This articles covers the following sections:

Template Details

Apty is compliant with VPAT user interface requirements for all releases starting with version 2.5.x and higher:

The following document covers the requirements of the Section 508 Standards, Safe Harbor, and FAR Council:

  • Revised 508 Standards: Information and communication technology (ICT) developed, maintained, or used by Federal agencies must satisfy the scoping and technical requirements in the Revised 508 Standards.
  • Safe Harbor: This safe harbor applies on an element-by-element basis to each component or portion of the existing ICT, with each component or portion assessed separately.
  • FAR (Federal Acquisition Regulation) Council: While FAR Council is within the ongoing process of updating the requirements, Federal Agencies must, at minimum, ensure that their ICT requirements comply with Revised 508 Standards as of January 18, 2018.

SOURCE: http://www.section508.gov/blog/Revised-508-Standards-Safe-Harbor-and-FAR-Update

VPAT compliance testing of Apty was performed considering the standards from the provisions listed above. The initial versions of the product have been updated to fit the requirements, while new features, user interface and functionality changes for releases 2.5.x and higher have been designed to follow the VPAT standards on the ongoing basis. Current version (3.0) of Apty is compliant with the software applications and operating system, performance, and documentation requirements listed below.

Supporting Features (Second Column on VPAT)

Supports

Use this language when you determine the product fully meets the letter and intent of the Criteria.

Supports with exceptions

Use this language when you determine the product does not fully meet the letter and intent of the Criteria but provides some level of access relative to the Criteria.

Supports through equivalent facilitation

Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.

Supports when combined with compatible AT

Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).

Does not Support

Use this language when you determine the product does not meet the letter or intent of the Criteria.

Not Applicable

Use this language when you determine that the Criteria do not apply to the specific product.

Not Applicable - Fundamental alteration exception applies

Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").

VPAT Summary Table

NOTE: This VPAT documents the results of testing procedures updated for the Section 508-refresh/WCAG 2.0 harmonization criteria. Test results for these additional criteria are documented in Results of Testing to Section 508-REFRESH/WCAG Harmonization Criteria.

Criteria

Supporting Features

Remarks and explanations

Section 1194.21 Software Applications and Operating Systems

Supports with exceptions

Apty is a digital user engagement platform that works as an overlay on hosting web applications. Apty versions starting with 2.5.x have and higher are compliant with the requirements for the accessibility mode and have been tested against the criteria in both Sections 1194.21 and 1194.22 for Mozilla Firefox, Chrome, and Internet Explorer.

See details in Section 1194.21.

Section 1194.22 Web-based internet information and applications

 

Supports with exceptions

Apty is a digital user engagement platform that works as an overlay on hosting web applications. Apty versions starting with 2.5.x and higher are compliant with the requirements for the accessibility mode and have been tested against the criteria in both Sections 1194.21 and 1194.22 for Mozilla Firefox, Chrome, and Internet Explorer.

See details in Section 1194.21.

Section 1194.23 Telecommunications Products

Not applicable

Section 1194.24 Video and Multimedia Products

Not applicable

Section 1194.25 Self-Contained, Closed Products

Not applicable

Section 1194.26 Desktop and Portable Computers

Not applicable

Section 1194.31 Functional Performance Criteria

Supports with exceptions

See details in Section 1194.31.

Section 1194.41 Information, documentation, and support

Supports with exceptions

See details in Section 1194.41.

SECTION 1194.21 Software Applications and Operating Systems – Detail

Criteria

Supporting Features

Remarks and explanations

(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.

Supports

All Apty functions can fully be used in a mouse less, keyboard-only mode.

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.

Supports

When implemented in another web application, Apty does not block or disable any of hosting app features, as well as operating system functionality. Application supports the following OS accessibility features:

  • StickyKeys,
  • FilterKeys,
  • ToggleKeys,
  • MouseKeys,
  • High Contrast.

(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.

Supports

When using the application’s Admin panel / Assist Studio or Clie, it is clearly visually indicated where the focus is by the means of standard browser functions (caret inside of a focused element, an outline around focused buttons / links, etc.)

(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.

Supports with exceptions

User interface is provided with the sufficient information identifying system elements and the state they are in. Name, value and state of the majority of interface elements can be accessed from the screen reader.

(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.

Supports

Bitmap images, which are used within the system or added as a part of instructional content to the hosting application, are used consistently and have unambiguous meaning.

For example, a question mark icon provides hint text with short description of an element upon hovering over it; this image is used consistently throughout the system.

(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.

Supports

Textual information is provided throughout the operating system. Text content, input caret location, and text attributes made available.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Supports

The product inherits user selected settings for color and contrast (4.5:1 or greater).

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

Not applicable

None of the system elements use animation; however, some of the functions allow linking to or embedding animation. Any external content provided by the user is considered to be out of scope of Apty responsibility due to the absence of the ability of verifying and testing it.

(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.

Supports

Color coding is used to indicate system response and providing information, but it is used in combination with the text / icons and other elements. For example, when a user attempts to submit a form with the missing data, a warning message is shown at the top of the form in yellow color with the text indicating the changes that should be made to proceed with the form submission.

(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.

Supports through equivalent facilitation

Apty provides the ability to change UI color theme options. Contrast settings are inherited from the operating system.

(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.

Supports with exceptions

An application is using flashing / blinking elements with the flashing rate within the allowed range.

(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.

Supports

Apty’s process of creating instructional content is based on the logic of form submission. All the required (and non-required) fields can be accessed and completed by Assistive Technology users.

SECTION 1194.22 Web-Based Internet Information and Applications – Detail

Criteria

Supporting Features

Remarks and explanations

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

Support with exceptions

Text equivalents are provided for most of non-text elements of the system.

System elements are constantly reviewed and updated to meet this criterion, also known as a best practice of User Experience design.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Not applicable

None of the system elements use multimedia presentations; however, some of the functions allow linking to or embedding presentations. Any external content provided by the user is considered to be out of scope of Apty responsibility due to the absence of the ability of verifying and testing it.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Supports

Color coding is used to indicate system response and providing information, but it is used in combination with the text / cons and other elements. For example, when a user attempts to submit a form with the missing data, a warning message is shown at the top of the form in yellow color with the text indicating the changes that should be made to proceed with the form submission.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Supports

All documents are organized in a way, so that they are readable without associated style sheets.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not applicable

Server-side image maps are not used.

(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

Server-side image maps are not used.

(g) Row and column headers shall be identified for data tables.

Supports when combined with compatible AT

Row and column headers are identified in data tables.

(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.

Supports

Markup is used to associate data cells and header cells in multi-level data tables.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Supports

The product uses iFrames. iFrame titles are specified with the title attribute and can be identified by Assistive Technology.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supports with exceptions

An application is using flashing / blinking elements with the flashing rate within the allowed range.

(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.

Not applicable

Apty does not require text-only pages for equivalent functionality.

(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.

Supports

Information provided by scripts is not displayed when the associated scripts are disabled; however, ATs are able to interpret scripts when scripts are enabled.

(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

The product requires no plug-ins, applets, or other applications.

(n) When electronic forms are designed to be completed on- line, 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.

Supports

Apty’s process of creating instructional content is based on the logic of form submission. All the required (and non-required) fields can be accessed and completed by Assistive Technology users.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports

The product permits users to skip repetitive navigation links by the means of coded HTML headers in hierarchical order.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Not applicable

According to the system design, there are no operations that can be timed out.


SECTION 1194.23 Telecommunication Products - Detail

Criteria

Supporting Features

 

(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use.

Not applicable

(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols.

Not applicable

(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs.

Not applicable

(d) Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required.

Not applicable

(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays.

Not applicable

(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided.

Not applicable

(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use.

Not applicable

(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.

Not applicable

(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product.

Not applicable

(j) Products that transmit or conduct information or communication, shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery.

Not applicable

(k)(1) Products which have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be tactilily discernible without activating the controls or keys.

Not applicable

(k)(2) Products which have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be operable with one hand and shall not require tight grasping, pinching, twisting of the wrist. The force required to activate controls and keys shall be 5 lbs. (22.2N) maximum.

Not applicable

(k)(3) Products which have mechanically operated controls or keys shall comply with the following: If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character.

Not applicable

(k)(4) Products which have mechanically operated controls or keys shall comply with the following: The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound.

Not applicable

SECTION 1194.24 Video and Multimedia Products - Detail

Criteria

Supporting Features

 

(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals.

Not applicable

(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry.

Not applicable

(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned.

Not applicable

(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described.

Not applicable

(e) Display or presentation of alternate text presentation or audio descriptions shall be user- selectable unless permanent.

Not applicable

SECTION 1194.25 Self Contained, Closed Products - Detail

Criteria

Supporting Features

(a) All mechanically operated controls and keys shall comply with §1194.23 (k) (1) through (4).

Not applicable

(b) If a product utilizes touch screens or touch-operated controls, an input method shall be provided that complies with §1194.23 (k) (1) through (4).

Not applicable

(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided.

Not applicable

(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards

Not applicable

SECTION 1194.31 Functional Performance Criteria

Criteria

Supporting Features

Remarks and explanations

(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.

Supports with exceptions

The product supports the use of screen readers by blind and visually impaired users with minor exceptions stated in Sections 1194.21 and 1194.22.

(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.

Supports with exceptions

The product supports the use of screen magnifiers for visually impaired users. However, there are exceptions for screen reader support.

(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.

Not applicable

This application does not use audio information.

(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

This application does not use audio information.

(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

This application does not require user speech.

(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.

Supports with exceptions

Apty application can fully be used in a mouseless, keyboard-only mode (see 1194.21(a)). The product supports OS motor control features (see 1194.21(b)).

SECTION 1194.41 Information, Documentation, and Support

Criteria

Supporting Features

Remarks and explanations

(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge

Supports with exceptions

Apty support documentation is available in 508-compliant HTML version and PDF format (upon request).

 

(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.

Supports with exceptions

Product documentation includes a description of the accessibility and compatibility features of products in 508-compliant HTML version and PDF format (upon request).

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Supports through equivalent facilitation

Support services are available in the following variations:

  • Online and email support for customers with hearing disabilities.
  • Phone support for customers with visual disabilities.

Results of Testing to Section 508-REFRESH/WCAG 2.0 Harmonization Criteria

Criteria

Supporting Features

Remarks and explanations

WCAG2.0: 1.3.1 Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

Supports

Headings, lists and paragraphs are programmatically identifiable by the means of the respective tags and are marked up correctly throughout the application.

WCAG2.0: 2.4.2 Web pages have titles that describe the topic or purpose. (Level A)

Supports with exceptions

Web page titles provide accurate description of the topic or purpose.

Some system elements and pages of the tool have no unique titles.

WCAG2.0: 2.4.4 The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)

Supports with exceptions

The purpose of most of the links can be determined by link text alone.

System elements are constantly reviewed and updated to meet this criterion, also known as a best practice of User Experience design.

WCAG 2.0: 2.4.5 More than one way is available to locate a Web page within a set of Web pages except where the Web page is a result of, or a step in, a process. (Level AA)

Supports with exceptions

Core functions of the of the Apty application are based on the logic of following precise steps for reaching the expected result; therefore, on multiple occasions locating a page is done through completing the specific steps of the process.

WCAG2.0: 2.4.6 Headings and labels describe topic or purpose. (Level AA)

Supports with exceptions

The application provides headings and labels that identify content purpose.

WCAG2.0: 3.1.1 The default human language of each document or Web page can be programmatically determined. (Level A)

Supports

The default language of the application is correctly identified.

The screen reader reads all text in the default language.

WCAG2.0: 3.1.2 The default human language of each passage or phrase can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)

Supports

The application content can be changed in user settings.

WCAG2.0: 3.2.2 Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)

Supports

Repeated navigational mechanisms always appear in the same relative order each time they are repeated.

WCAG2.0: 3.2.4 Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

Supports

Components are labeled consistently each time they appear in the application.

WCAG2.0: 4.1.1 In content implemented using markup language, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)

Supports

No validation errors were found for the application.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.