Voluntary Product Accessibility Template: Unicorn 2003 iBistro/iLink


Date: June 30, 2003
Name of Product: SirsiDynix Unicorn 2003 iBistro/iLink Public Access Clients
Contact for more Information: Berit Nelson, VP Product Management, 1-800-325-0888

The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed 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.

Summary Table
Voluntary Product Accessibility Template
Criteria Supporting Features Remarks and explanations
Section 1194.21 Software Applications and Operating Systems Not applicable Not applicable
Section 1194.22 Web-based internet information and applications See detail See detail
Section 1194.23 Telecommunications Products Not applicable Not applicable
Section 1194.24 Video and Multi-media Products Not applicable Not applicable
Section 1194.25 Self-Contained, Closed Products Not applicable Not applicable
Section 1194.26 Desktop and Portable Computers Not applicable Not applicable
Section 1194.31 Functional Performance Criteria See detail See detail

Section 1194.22
Web-based Internet information & 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 iBistro/iLink utilizes the "alt", "id", "title" attributes accordingly.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports iBistro/iLink does not use online multimedia presentations.
(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 iBistro/iLink only utilizes color for aesthetics and is not used to convey any meaningful information.
(d) Documents shall be organized so they are readable without requiring an associated stylesheet. Supports iBistro/iLink utilizes style sheet elements (CSS) that degrade well and are not required to render the pages in a meaningful manner.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supports iBistro/iLink does not use server-side image maps.
(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 iBistro/iLink does not use client-side image maps.
(g) Row and column headers shall be identified for data tables. Supports iBistro/iLink primarily uses tables for positioning elements on the screen. When data tables are used, they utilize the <th> tag to identify headers for columns/rows.
(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 iBistro/iLink primarily uses tables for positioning elements on the screen. When data tables are used, they utilize the <th> tag to identify headers for columns/rows.
(i) Frames shall be titled with text that facilitates frame identification and navigation Supports iBistro/iLink does not use 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. Supports iBistro/iLink does not utilize any elements or technology that affects the viewers current monitor refresh rate or screen flicker frequency.
(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 Compliance has been accomplished without use of text-only pages.
(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 iBistro/iLink utilizes scripting language on both the server and client side. Server-side scripting generates valid HTML. Client-side scripting is JavaScript, and is required to view the full range of features offered by iBistro/iLink. A user can still access core functions without the use of JavaScript. The <noscript> tag has been utilized to notify users who do not have JavaScript enabled of this 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 &#sect;1194.21(a) through (l). Supports iBistro/iLink does not utilize applets, plug-ins or require any other application to be present on the client system to interpret content.
(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 when combined with Compatible AT iBistro/iLink utilizes HTML coding that allows Assistive Technology to access information, field elements, and functionality required for completion and submission of the form.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports iBistro/iLink includes HTML code that will allow a user to skip repetitive navigational links.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Supports iBistro/iLink only times out after a user's session has been idle for a prescribed period of time.

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
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 when combined with Compatible AT iBistro/iLink has been re-engineered to meet Section 508 Compliance, and it takes advantage of coding specifications that are geared to properly integrate with accessibility features and Assistive Technology.
(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 when combined with Compatible AT iBistro/iLink has been re-engineered to meet Section 508 Compliance, and it takes advantage of coding specifications that are geared to properly integrate with accessibility features and Assistive Technology.
(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 iBistro/iLink does not rely on audio to present 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. Supports iBistro/iLink does not rely on audio to present 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. Supports iBistro/iLink does not rely on user speech to present information.
(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 iBistro/iLink does not rely on fine motor control to present information.