Surfer Voluntary Product Accessibility Template (VPAT)

Surfer VPAT

Voluntary Product Accessibility Template®

Version 2.4

The purpose of the Voluntary Product Accessibility Template® (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. More information on the specific standards used can be found here: https://www.access-board.gov/ict/#501-general and https://www.w3.org/TR/WCAG20/

Date: 1 February 2023
Name of Product: Surfer 25
Product Description: Golden Software's Surfer software is a full-function 3D visualization, contouring and surface modeling package that runs under Microsoft Windows. Surfer is used extensively for terrain modeling, landscape visualization, surface analysis, contour mapping, 3D surface mapping, gridding, volumetrics, and more.
Contact for more Information: 1-303-279-1021 or sales@goldensoftware.com

The following three tables follow the VPAT™ template to provide a summary of the Web Content Accessibility Guidelines (WCAG) 2.1 and Section 508 Standards that pertain to software products:

Web Content Accessibility Guidelines
Section 508 Chapter 5: Software
Section 508 Chapter 6: Support

Important Note About This Analysis
Golden Software's Surfer application is a data and mapping visualization tool. Many aspects of how users interact with the application are through dialogs that set parameters and define properties. These have a high degree of accessibility, and users can build simple to complex maps using the settings in these dialogs. The maps that are built in Surfer are user-dependent, meaning that a user can add any number of objects to a map, such as points, legends, layers, scales, etc... Most objects that can be added to a map do not have a high degree of accessibility. For example, you cannot tab thru objects in a map. You can access each object from a list of map objects in a contents window that holds and allows users to manage objects in a map. The refinement of the objects in the map, for example their placement or sizing, does not have a high degree of accessibility.

Guidelines (WCAG) 2.0

(Level A and AA, Level AAA is not evaluated)

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content (Level A)

Does not support

Surfer contains three sets of help documentation, and one of them, the online HTML help, does not contain alt text for most images. Many images, such as buttons,
are evident by their context in specific steps or instructions, and the images of dialogs and other important references have image captions.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A

Not applicable

 

1.2.2 Captions (Prerecorded) (Level A)

Not applicable

 

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Not applicable

 

1.2.4 Captions (Live) (Level AA)

Not applicable

 

1.2.5 Audio Description (Prerecorded) (Level AA)

Not applicable

 

1.3.1 Info and Relationships (Level A)

Does not support

Component labels for another component are frequently not discernible using assistive technology.

1.3.2 Meaningful Sequence (Level A)

Partially supports

When meaning is affected by the sequence of elements in context, Surfer usually presents a sequentially meaningful context; however some information sequences are dependent on a functional complexity that programmatic approaches may not be able to predict.

1.3.3 Sensory Characteristics (Level A)

Supports

 

1.3.4 Orientation (Level AA)

Supports

 

1.3.5 Identify Input Purpose (Level AA)

Supports

 

1.4.1 Use of Color (Level A)

Partially supports

The vast majority of times that color references are used, other methods, such as the text name of the color, are used. However, there are some features in Surfer as a data visualization and mapping tool that use colors as colors, without a text references or other accessibility option.

1.4.2 Audio Control (Level A)

Not applicable

 

1.4.3 Contrast (Minimum) (Level AA)

Partially supports

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

1.4.4 Resize text (Level AA)

Partially supports

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

1.4.5 Images of Text (Level AA)

Supports

The application does not use images of text

1.4.7 Low or No Background Audio

Supports

 

1.4.10 Reflow (Level AA)

Supports

 

1.4.11 Non-text Contrast (Level AA)

Supports

 

1.4.12 Text Spacing (Level AA)

Supports

 

1.4.13 Content on Hover or Focus (Level AA)

Supports

 

2.1.1 Keyboard (Level A)

Supports

 

2.1.2 No Keyboard Trap (Level A)

Supports

 

2.2.2 Pause, Stop, Hide

Supports

 

2.1.4 Character Key Shortcuts (Level A)

Does not support

 

2.2.1 Timing Adjustable (Level A)

Not applicable

 

2.2.2 Pause, Stop, Hide (Level A)

Supports

 

2.3.1 Three Flashes or Below Threshold (Level A)

Supports

 

2.4.1 Bypass Blocks (Level A)

Not applicable

 

2.4.2 Page Titled (Level A)

Supports

 

2.4.3 Focus Order (Level A)

Supports

 

2.4.4 Link Purpose (In Context)(Level A)

Supports

 

2.4.5 Multiple Ways (Level AA)

Not applicable

 

2.4.6 Headings and Labels (Level AA)

Supports

 

2.4.7 Focus Visible (Level AA)

Supports

 

2.5.1 Pointer Gestures (Level A)

Supports

 

2.5.2 Pointer Cancellation (Level A)

Supports

 

2.5.3 Label in Name (Level A)

Does not support

There are dialogs in the Surfer user interface that do not clearly associate a label name with a related object or component

2.5.4 Motion Actuation (Level A)

Not applicable

 

3.1.1 Language of Page (Level A)

Not applicable

The only human language in Surfer's user interface and web based information is English.

3.1.2 Language of Parts (Level AA)

Not applicable The only human language in Surfer's user interface and web based information is English.

3.2.1 On Focus (Level A)

Supports  

3.2.2 On Input (Level A)

Supports  

3.2.3 Consistent Navigation (Level AA)

Does not support  

3.2.4 Consistent Identification (Level AA)

Supports  

3.3.1 Error Identification (Level A)

Supports  

3.3.2 Labels or Instructions (Level A)

Supports  

3.3.3 Error Suggestion (Level AA)

Supports  

3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)

Not applicable Surfer has no financial transactions or opportunities to enter into legal agreements. Potential Surfer upgrades and changes in licensing occur in a different application

4.1.1 Parsing (Level A)

Supports  

4.1.2 Name, Role, Value (Level A)

Partially supports Surfer web-based help supports this requirement. Most of Surfer's user interface elements' information is available programmatically thru assistive technology. Some object's states or other information is not discernible programmatically, such as the object type.

4.1.3 Status Messages (Level AA)

Does not support  

 

Section 508 Chapter 5: Software

Criteria

Conformance Level

Remarks and explanations

502 Interoperability with Assistive Technology

See WCAG 2.0 section

See the WCAG section for web related components of this software.

502.2.1 User Control of Accessibility Features

Supports  

The user has full control over all accessibility features.  

502.2.2 No Disruption of Accessibility Features

Supports  

There is no disruption of accessibility features.  

502.3 Accessibility Services

 

 

502.3.1 Object Information

Partially supports  

Most user interface elements' information is available programmatically thru assistive technology. Some object's states or other information is not discernible programmatically, such as the object type.

502.3.2 Modification of Object Information

  Partially supports

Users can set the values of and engage in the manipulation of most user interface elements. Some user interface elements cannot be set programmatically.

502.3.3 Row, Column, and Headers

Does not support  

 

502.3.4 Values

Partially supports  

Values for objects can be determined programmatically, but not all objects' value ranges can be determined programmatically  

502.3.5 Modification of Values

Partially supports  

The values of most user interface elements can be set programmatically.  

502.3.6 Label Relationships

Does not support  

Component labels for another component are frequently not discernible using assistive technology.

502.3.7 Hierarchical Relationships

Partially supports  

Most hierarchical relationships can be determined using assistive technology  

502.3.8 Text

Partially supports  

Most text objects contents and locations are accessible information.  

502.3.9 Modification of Text

  Partially supports

Most text values than can be set, can be set using assistive technology.  

502.3.10 List of Actions

Does not support  

Lists of actions that can be performed on an object are often not programmatically determinable, and the object type (e.g. button, check box) may not be available to assistive technology.

502.3.11 Actions on Objects

Partially supports

Most actions that can be taken on objects can be done using assistive technology. However some objects' actions cannot be accessed via assistive technology.

502.3.12 Focus Cursor

Partially supports  

Where, applicable, cursor location shows a visual focus and a name focus if using assistive technology. However, the object type (e.g. button, check box) may not available to assistive technology.

502.3.13 Modification of Focus Cursor

Partially supports  

For most applicable cursor locations, Surfer shows a visual focus and a name focus if using assistive technology.

502.3.14 Event Notification

Partially supports  

For events that are notification worthy, assistive technology can assess those events. Not all events, such as updating a value in a dialog, have notifications. A user could use assistive technology to verify these types of events.

502.4 Platform Accessibility Features

Not applicable  

Surfer is not platform software.  

503 Applications

 

 

503.2 User Preferences

Partially supports  

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

503.3 Alternative User Interfaces

Not applicable  

No alternative user interface provided.  

503.4 User Controls for Captions and Audio Description

Not applicable

No audio included in the software

503.4.1 Caption Controls

Not applicable

No audio included in the software

503.4.2 Audio Description Controls

Not applicable

No audio included in the software

504 Authoring Tools

Not applicable

Not applicable

504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”)

Not applicable

Not applicable

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not applicable

Not applicable

504.2.2 PDF Export

Not applicable

Not applicable

504.3 Prompts

Not applicable

Not applicable

504.4 Templates

Not applicable

Not applicable

 

Section 508 Chapter 6: Support

Criteria

Supporting Features

Remarks and explanations

601.1 Scope

   

602 Support Documentation

Supports

Digital documentation is available within Surfer. This documentation is also available through the Golden Software website

602.2 Accessibility and Compatibility Features

See WCAG 2.0 section

A help topic describing accessibility features is being developed for the next release.

602.3 Electronic Support Documentation

Partially supports

Some web-based and self service support, such as HTML-based help, does not have fully accessible alternative text for images or other object when using read-out-loud assistive tools.

602.4 Alternate Formats for Non-Electronic Support Documentation

Supports

Provided by calling technical support

603 Support Services

 

 

603.2 Information on Accessibility and Compatibility Features

Does not yet support

A help topic describing accessibility features is being developed for the next release.

603.3 Accommodation of Communication Needs

Supports

Support services is provided directly to the user over the telephone or via email.

 

 

Was this article helpful?
4 out of 4 found this helpful

Comments

0 comments

Please sign in to leave a comment.