Follow

Surfer Voluntary Product Accessibility Template (VPAT)

Surfer v14 VPAT

Voluntary Product Accessibility Template®

Version 1.3

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

Date: 14 February 2017
Name of Product: Surfer 14
Contact for more Information (name/phone/email): 1-303-279-1021 or sales@goldensoftware.com

Download PDF version

Summary Table

VPAT

Voluntary Product Accessibility Template®

Criteria

Applicability

Compliance

Section 1194.21 Software Applications and Operating Systems

 Applicable

Supports with exceptions

Section 1194.22 Web-based Internet Information and Applications

Not applicable

 

Section 1194.23 Telecommunications Products

Not applicable

 

Section 1194.24 Video and Multi-media 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

 Applicable

Supports with exceptions

Section 1194.41 Information, Documentation and Support

 Applicable

Supports with exceptions

 

Section 1194.21 Software Applications and Operating Systems – Detail

VPAT

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.

Plot: Supports with exceptions

Worksheet: Supports

Grid Editor: Supports

 

Nearly all commands and functions are keyboard accessible through the application menu or customizable shortcuts. See Keyboard Commands and Customize Keyboard.

Some controls, such as the Measure and Grid Info window cannot be accessed via the keyboard.

Additionally, some dialog controls, such as colormap anchor node selection, are not operable with a keyboard alone.

(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

Our products do not disrupt the operating system functionality as a rule.

(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

We use standard Windows focus behavior for all our application windows and dialogs.

(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

The identity, operation, and state is available for many elements. However identity, operation, and state information is not available for some critical items, such as objects in the plot window.

(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

All controls are standardized across the Golden Software product suite.

(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

We use the standard windows API calls to display text.

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

Supports

Applications do not override user display attributes at any time.

Our products respect the High Contrast Themes.

(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

 Animations are not used.

(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 sparingly used, user customizable, and always accompanied by other descriptive 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

Regarding the user interface, we offer Microsoft user interface schemes.

Regarding application output, we offer all the colors.

(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

No flashing objects are used.

(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

We use standard Windows API controls for our input from users that work with Windows assistive technology by default.

 

Section 1194.31 Functional Performance Criteria – Detail

VPAT

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.

 Does not support

Sufficient descriptive information is not available for objects in the plot window. 

(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

The use of screen magnifiers is 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

 Supports

The application user interface does not require user hearing.

(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

The application user interface does not require user hearing.

(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

The 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

Some dialog controls, such as the colormap anchor node operation, require the use of a mouse. 

 

Section 1194.41 Information, Documentation and Support – Detail

VPAT

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

Electronic documentation is provided in the application and on the web.

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

 Does not support

Accessibility and compatibility features are not documented. 

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

 Supports

Various support formats, including phone, email, web, and LiveChat support, are available. 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.