|
Voluntary Product Accessibility Template TM
|
Summary Table: Voluntary Product Accessibility Template TM
|
|
Criteria
|
Supporting Features
|
Remarks and explanations
|
|
Section 1194.21 Software Applications and Operating Systems
|
See section 1194.21 below
|
|
|
Section 1194.22 Web-based Internet Information and Applications
|
See section 1194.22 below.
|
ButterflyNetRender Scene and Render Node information can be viewed from a web browser using the HTML Viewer feature.
|
|
Section 1194.23 Telecommunications Products
|
Not Applicable
|
ButterflyNetRender is not considered a telecommunications product
|
|
Section 1194.24 Video and Multi-media Products
|
Not Applicable
|
ButterflyNetRender does not use multimedia except as covered in section 1194.21
|
|
Section 1194.25 Self-Contained, Closed Products
|
Not Applicable
|
ButterflyNetRender is not a self-contained product.
|
|
Section 1194.26 Desktop and Portable Computers
|
Not Applicable
|
ButterflyNetRender is software as defined in section 1194.21.
|
|
Section 1194.31 Functional Performance Criteria
|
See section 1194.31 below.
|
|
|
Section 1194.41 Information, Documentation and Support
|
See section 1194.41 below.
|
|
|
Return to Top of page
|
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.
|
Supported with minor exceptions
|
Some Screens may require the use of a mouse. By using Windows ‘MouseKeys’ this movement of the mouse can be controlled by the num-lock keypad.
|
|
(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
|
|
|
(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
|
|
|
(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
|
|
|
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.
|
Supported
|
|
|
(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
|
|
|
(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
|
|
|
(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
|
|
|
(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 Supported
|
When the Scenes are Active the Icon next to the scene name will Flash Green. To display active scenes running without any flash text – you can use the HTML Viewer.
|
|
(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 with minor exceptions
|
Some Screens may require the use of a mouse. By using Windows ‘MouseKeys’ this movement of the mouse can be controlled by the num-lock keypad.
|
|
Return to Top of page
|
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).
|
Supported with exceptions
|
The HTML Viewer does not display non-text elements – so this is not required.
|
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
|
Not Applicable
|
|
|
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
|
Not Supported
|
The Text colors can not be changed
|
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet.
|
Supported
|
|
|
(e) Redundant text links shall be provided for each active region of a server-side image map.
|
Not Applicable
|
|
|
(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
|
|
|
(g) Row and column headers shall be identified for data tables.
|
Supported with exceptions
|
The Tables used to display the Scene and Render node information does not display grid lines
|
|
(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
|
Not Applicable
|
|
|
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
|
Not Applicable
|
|
|
(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 with exceptions
|
The HTML Viewer pages are already displayed in text – a text only page is not required.
|
|
(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.
|
Not Applicable
|
|
|
(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
|
|
|
(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.
|
Not Applicable
|
|
|
(o) A method shall be provided that permits users to skip repetitive navigation links.
|
Supported
|
|
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
|
Supported
|
|
|
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 Top of page
|
Section 1194.23 Telecommunications Products –
ButterflyNetRender is not considered a telecommunication product.
|
|
|
Section 1194.24 Video and Multi-media Products –
ButterflyNetRender does not use multimedia except as covered in section 1194.21.
|
|
|
Section 1194.25 Self-Contained, Closed Products –
ButterflyNetRender is not considered a self-contained product.
|
|
|
Section 1194.26 Desktop and Portable Computers –
ButterflyNetRender is software as defined in section 1194.21.
|
|
Return to Top of page
|
Section 1194.31 Functional Performance Criteria – Detail
|
|
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.
|
Supported with minor exceptions
|
This will require 3rd party screen reader utility that is compatible with ButterflyNetRender. Users of assistive technology should contact their assistive technology vendor to assess the compatibility.
|
|
(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
ButterflyNetRender does not require user hearing for access to application functionality.
|
|
|
(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
ButterflyNetRender does not require user hearing for access to application functionality.
|
|
|
(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.
|
Supported
ButterflyNetRender does not require user hearing for access to application functionality.
|
|
|
(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.
|
Supported
ButterflyNetRender does not require speech recognition.
|
|
|
(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 minor exceptions
|
This will require 3rd party screen reader utility that is compatible with ButterflyNetRender. Users of assistive technology should contact their assistive technology vendor to assess the compatibility.
|
|
Return to Top of page
|
Section 1194.41 Information, Documentation and Support – Detail
|
|
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
|
Supported
|
The documentation is provided in HTML and PDF formats.
|
|
(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
|
|
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities.
|
Supported
|
We can provide support by phone and email.
|
|
Return to Top of page
|
