|
|
Voluntary Product Accessibility Template
Version 1.2*
May 6, 2004
The purpose of the Voluntary Product Accessibility Template, or VPAT, is to assist 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. It is assumed and recommended that offerers will provide additional contact information to facilitate more detailed inquiries.
The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.
* Changes: added Section 1194.41
Date: 5/31/2005
Name of Product: Initiate Software Developers Kits (SDK)
Contact for More Information: Ron Martin
Initiate Identity Hub™ software, the underlying technology for our industry-leading customer data integration applications, instantly finds and accurately links all the records about a person, corporate entity or object across all of your data sources. This provides the most accurate, complete, up-to-date information to all point-of-service applications, business intelligence platforms and back office systems. For developers who wish to connect to, interact with or embed all of the components of the Initiate Identity Hub™ software, Initiate offers the Initiate Identity Hub™ SDK. We also offer other SDKs that provide subsets of the full Initiate Identity Hub™ software capabilities for integrating specific pieces of Initiate's functionality into your applications.
With an Initiate Identity Hub SDK, you can tap into the full power of Initiate Identity Hub software, giving your application the ability to turn any volume of data into the clean, complete personal profiles you need to drive better, more cost-effective and responsible interactions with customers, patients, business partners or other interested organizations.
Initiate offers several SDK packages to meet your needs: scoring APIs only, scoring and searching APIs, and finally the full set of APIs. This packaging enables you to select the right level of functionality for your organization today with the capability to expand your SDK package over time.
- Initiate Scoring SDK – Provides simple access to the acclaimed scoring function of Initiate Identity Hub™ software. Your application sends two records of interest to the Initiate Scoring SDK, which standardizes and compares the records using our powerful algorithm, and then returns a comparison score indicating the likelihood that the two records represent the same person. Your application processes the score as appropriate for your needs. You get the benefit of an industry-leading scoring function embedded into your own application; you save time and money and get better results.
- Initiate Searching SDK – This SDK maintains a database of your customers. Users enter the search criteria from your third-party application screens; Initiate Identity Hub SDK standardizes the entry, finds likely matching candidates then returns the results of the search. Initiate Searching SDK achieves better search results by using the same renowned scoring function as Initiate Identity Hub to compare and match records. Better searching capability leads to better quality customer data, since users are not likely to enter duplicate customer records if they easily find the entry already in the database. And, customer satisfaction improves when your users always find complete information about each customer and his interactions with your enterprise.
- Initiate Identity Hub SDK – This package further expands your capabilities by including scoring and searching along with all other Initiate Identity Hub™ software API interactions. As with our other SDK packages, the scoring function compares two records and returns a comparison score; the searching function then finds all the record or records that match user-defined search criteria. Additionally, the Initiate Identity Hub SDK package maintains a database for storing information about linked records and potential "tasks" related to ambiguous links. Initiate Identity Hub SDK offers extensive user configuration options for tailoring the comparison and candidate selection functions. Security features are also available for controlling record privacy and users’ access to areas of the application. With Initiate Identity Hub SDK, you can embed any Initiate Identity Hub software function into your own applications, providing sophisticated identity management at a lower cost, more quickly and with better results than with self-developed code.
Return to the top of the page
Section 1194.21 Software Applications and Operating Systems – Detail
Voluntary Product Accessibility Template
|
|
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 with Exceptions |
Initiate™ SDKs is a programmable layer that allows Initiate Systems customers to integrate the features and functions of the Initiate Identity Hub into their own applications, third party applications or new applications. As such, the Initiate SDKs allows our customers to be completely Section 508 compliant by building the application of their choosing or integrating with existing compliant applications. |
|
(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 with Exceptions |
The Initiate SDKs leverage industry standard development languages and can be implemented without disrupting or disabling the feature and functions of the client operating system or database. |
|
(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 with Exceptions |
Support for screen focus and navigational techniques are part of the development of an application. Initiate SDKs do not limit nor deter the creation of a well-defined on-screen indication of focus nor navigational capabilities. |
|
(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 |
Exposing Initiate Identity Hub functionality via Initiate SDKs allows developer the ability to create all the appropriate information about and operation or function. |
|
(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 with Exceptions |
Initiate SDKs do not prohibit the invocation of any functionality via the use of icons or bit map images. With Initiate SDKs the developer has full control of API invocations by what ever means deemed appropriate. |
|
(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 with Exceptions |
Because the Initiate SDKs are programmable environment, developers can choose to provide users with Graphical User Interfaces or command line driven interfaces. Each can then adjust the information provided to the end user for execution. |
|
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. |
Supports with Exceptions |
The use of animation is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
Return to the top of the page
Section 1194.22 Web-based Internet Information and Applications – Detail
Voluntary Product Accessibility Template
|
|
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). |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Supports with Exceptions |
Synchronization is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Supports with Exceptions |
Initiate Systems™ does not utilize server side image maps for the use of the Initiate™ Auditor. |
|
(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. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(g) Row and column headers shall be identified for data tables. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 |
Initiate Systems™ does not design information presentation with a specific display frequency in mind. |
|
(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. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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 with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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). |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(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. |
Supported with Exception |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports with Exceptions |
The graphical user interface is typically controlled by the developer. Initiate SDKs do not prohibit nor place any undo requirements on the display of information. |
|
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. |
Return to the top of the page
Section 1194.23 Telecommunications Products – Detail
Voluntary Product Accessibility Template
|
|
Criteria |
Supporting Features |
Remarks and Explanations |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(k)(1) Products which have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be tactilely discernible without activating the controls or keys. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a telecommunication product. |
Return to the top of the page
Section 1194.24 Video and Multi-media Products – Detail
Voluntary Product Accessibility Template
|
|
Criteria |
Supporting Features |
Remarks and Explanations |
|
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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Video or Multi-media product. |
|
(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Video or Multi-media product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Video or Multi-media product. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Video or Multi-media product. |
|
(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Video or Multi-media product. |
Return to the top of the page
Section 1194.25 Self-Contained, Closed Products – Detail
Voluntary Product Accessibility Template
|
|
Criteria |
Supporting Features |
Remarks and Explanations |
|
(a) Self contained products shall be usable by people with disabilities without requiring an end-user to attach Assistive Technology to the product. Personal headsets for private listening are not Assistive Technology. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(b) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(c) Where a product utilizes touchscreens or contact-sensitive controls, an input method shall be provided that complies with §1194.23 (k) (1) through (4). |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(d) 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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(e) When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at anytime. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(f) When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45 dB, a volume gain of at least 20 dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(g) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(h) When a product permits a user to adjust color and contrast settings, a range of color selections capable of producing a variety of contrast levels shall be provided. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(i) Products shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(j) (1) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(j)(2) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(j)(3) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
|
(j)(4) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Operable controls shall not be more than 24 inches behind the reference plane. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Self-Contained or Closed product. |
Return to the top of the page
Section 1194.26 Desktop and Portable Computers – Detail
Voluntary Product Accessibility Template
|
|
Criteria |
Supporting Features |
Remarks and Explanations |
|
(a) All mechanically operated controls and keys shall comply with §1194.23 (k) (1) through (4). |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Desktop or Portable Computer. |
|
(b) If a product utilizes touchscreens or touch-operated controls, an input method shall be provided that complies with §1194.23 (k) (1) through (4). |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Desktop or Portable Computer. |
|
(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 |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Desktop or Portable Computer. |
|
(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards. |
Not Applicable |
Initiate SDKs is a programmable development environment designed to interact with the Initiate Identity Hub and not designed as a Desktop or Portable Computer. |
Return to the top of the page
Section 1194.31 Functional Performance Criteria – Detail
Voluntary Product Accessibility Template
|
|
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 |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions for the visually impaired or blind user. |
|
(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 |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions for the visually impaired or blind user. |
|
(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. |
Supports with Exceptions |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions for the deaf or hard of hearing user. |
|
(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. |
Supports with Exceptions |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions for the deaf or hard of hearing user. |
|
(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. |
Supports with Exceptions |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions for the users of different disabilities. |
|
(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 |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions for the users of different disabilities. |
Return to the top of the page
Section 1194.41 Information, Documentation and Support – Detail
Voluntary Product Accessibility Template
|
|
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 |
Initiate Systems™ provides documentation for the Initiate SDKs in two formats; hardcopy and electronic. Additional types of documentation could be generated from these sources (i.e. brail or audio). |
|
(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 |
Initiate SDKs can be used with Assistive Technologies to build new compliant alternate solutions for the users of different disabilities. |
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supports with Exceptions |
Initiate SDKs can be used with Assistive Technologies to build new compliant solutions addressing the communication needs users with different disabilities. |
Return to the top of the page
|