AMP VPAT

SSB BART Group (“SSB”) is dedicated to providing high quality information technology that is accessible to people with disabilities. In particular, SSB is committed to ensuring full compliance with the Section 508 accessibility standards. To this end, SSB has worked to ensure that the Accessibility Management Platform (“AMP”) is accessible.

The information contained within this Voluntary Product Accessibility Template (“VPAT”) is a result of an internal audit performed by SSB. This assessment fully tested the compliance of the web-based AMP reporting system, Infocus Toolbar for Internet Explorer, and InFocus, the Java-based automated testing product included with the AMP system. This testing included, but was not limited to: automated testing of the web portions, extensive manual testing on the web portions and of InFocus, and testing by users who are blind and low-vision with leading assistive technologies such as the JAWS screen reader, the ZoomText screen magnification software, and Dragon Naturally Speaking for compliance with the Section 508 standards.

Compliance Summary

Summary Table
Voluntary Product Accessibility Template
Criteria Supported
Section 1194.21 Software Applications and Operating Systems Supports with exceptions
Section 1194.22 Web-based Internet Information and Applications Supports
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 Supports with exceptions
Section 1194.41 Information, Documentation and Support Supports

Return to the top of the page.

Support Levels
Support Level Description
Supports AMP fully meets the letter and intent of the Criteria.
Supports with Exceptions/Minor Exceptions AMP does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
Supports through Equivalent Facilitation AMP provides an alternate way to meet the intent of the Criteria.
Supports when combined with Compatible AT AMP fully meets the letter and intent of the Criteria when used in combination with Compatible AT.
Does Not Support AMP does not meet the letter or intent of the Criteria.
Not Applicable The Criteria does not apply.
Not Applicable – Fundamental Alteration Exception Applies A Fundamental Alteration of AMP is required to meet the Criteria.

Return to the top of the page.

Section 1194.21 Software Applications and Operating Systems
Voluntary Product Accessibility Template
Note: This section covers all AMP components including the AMP web UI, the Infocus Java application and the InFocus Toolbar for Internet Explorer.
Criteria Support Level 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. AMP Web: Supports AMP Provides full keyboard support by avoiding the use of device dependent event handlers and using standard html elements. AccessKeys are also provided some functions such as “make it happen” button found on most pages.
AMP InFocus: Supports InFocus and the InFocus Toolbar provide keyboard shortcuts for major functions and support standard keyboard commands.
AMP InFocus Toolbar: Supports with Exceptions The InFocus Toolbar provides some functionality which requires the use of the mouse such as the selection of elements from the browser window and the colour contrast eye dropper. There alternative options to navigation the document object model by element and enter the colour value manually into the foreground and background color fields.
(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. AMP Web: Supports The web portion of AMP does not disrupt accessibility features and employs accessibility enhancements such as ARIA to improve accessibility over standard HTML. Additionally, AMP follows high contrast mode of the Windows OS when viewed in a browser that support high contrast settings.
AMP InFocus: Supports with Exceptions InFocus supports the Java Accessibility API however not all portions of the UI work correctly with all assistive technologies such as VoiceOver on the Macintosh. These problems are confined to the older InFocus desktop UI.
AMP InFocus Toolbar: Supports The InFocus Toolbar supports operating system and assistive technologies feature such as sticky keys, filter keys, mouse keys, and high contrast.
(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. AMP Web: Supports AMP provides standard focus indication provided by the browser. In addition, visual focus events that are triggered by mouse hover are also triggered by keyboard focus.
AMP InFocus: Supports InFocus focus indication is set and tracked using the Java Accessibility API.
AMP InFocus Toolbar: Supports Infocus Toolbar focus indication is set and tracked using standard Windows functions.
(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. AMP Web: Supports AMP Web provides alternate and equivalent text providing additional state and role information where needed. Form fields provide explicit labels or title attributes, groups of controls are properly grouped with fieldsets and legends.
AMP InFocus: Supports
AMP InFocus Toolbar: Supports
InFocus and InFocus Toolbar use standard UI elements supported by assistive technologies. These elements provide accessible names, states, values, roles, and descriptions.
(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. AMP Web: Supports
AMP InFocus: Supports
AMP InFocus Toolbar: Supports
All bitmap images are used in a consistent fashion.
(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. AMP Web: Supports AMP Web provides textual information through standard HTML elements.
AMP InFocus: Supports InFocus provides all textual information through the appropriate Java Accessibility API text functions.
AMP InFocus Toolbar: Supports InFocus Toolbar provides all textual information through the appropriate Windows API text functions.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. AMP Web: Supports AMP screens do not override selected contrast and color selections or display attributes of a user’s operating system when viewed in a browser that supports using OS color settings including high contrast.
AMP InFocus: Supports with Exceptions InFocus does not fully support custom colors in the review panel. All other screens provide support for the users’ default settings.
AMP InFocus Toolbar: Supports with minor exception InFocus Toolbar follows the OS color settings with one exception – the highlighted text in the code pane if a fixed yellow background.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. AMP Web: Supports AMP Web does not display animation.
AMP InFocus: Supports Animated progress bars are used in the InFocus installers; however, a textual description of progress is also included.
AMP InFocus Toolbar: Supports The Infocus Toolbar does not use animation.
(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. AMP Web: Supports AMP Web does not use color alone to convey information. Any instance where color is used to convey meaning or supply context the color is combined with equivalent text and/or visual indication.
AMP InFocus: Supports InFocus does not use color coding.
AMP InFocus Toolbar: Supports with Exceptions The InFocus Toolbar use color to emphasize elements in HTML code however this functionality is not required for successful operation of the toolbar.
(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. Not Applicable AMP does not permit users to change color and contrast settings.
(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 blinking or flashing elements 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. AMP Web: Supports All form elements within AMP Web are properly labeled and all forms are designed to be completed and submitted with accessibility in mind. For example, the tab order is logical, required field notation is includes in the accessible label, and forced focus changes are avoided.
AMP InFocus: Supports All electronic forms within InFocus software utilize the appropriate Java Accessibility API properties.
AMP InFocus Toolbar: Supports with Exceptions Most electronic forms within InFocus Toolbar utilize the appropriate .NET Accessibility features however some fields such as the username and password fields are missing accessible names.

Return to the top of the page.

Section 1194.22 Web-based Internet information and applications
Voluntary Product Accessibility Template
Note: This section covers the main AMP web UI only. Adobe Captivate based training courses and wiki based reference materials are not covered.
Criteria Support Level 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 All images throughout AMP have appropriate alt attributes. All non-textual elements such as visual selection, sections, etc. provide textual equivalents through text markup and HTML structure.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports AMP does not contain multimedia. *Training courses are not covered by this VPAT — however, the Captivate based training courses provide closed captioning and textual equivalents.
(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 AMP does not use color alone to convey information. Any instance where color is used to convey meaning or supply context, that use of color is combined with text and other visual indicators.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports AMP uses CSS to dictate layout and presentation. All content, interfaces, and system functionality work and are readable without style sheets. The reading order of content is correct when reviewed with screen readers.
(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable ` There are no server-side image maps within AMP.
(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 There are no image maps within AMP.
(g) Row and column headers shall be identified for data tables. Supports Column headers are identified for all data tables within AMP and their scope is defined to dictate relationships between header cells and data cells. Row headers are not defined on data tables within AMP. In the majority of cases, the table structure is simple and the lack of row headers should not significantly reduce usability for assistive technology users. The majority of data tables in AMP are designed with visual column headers and do not visually indicate row headers.
(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 In all cases where header cells are identified, the association between data cells and header cells are created through the use of the ‘scope’ attribute.
(i) Frames shall be titled with text that facilitates frame identification and navigation Supports There are no frames in use within AMP.
(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 No elements exist within AMP which would cause flicker of any kind.
(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. Not Applicable Text-only alternatives are not used.
(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 All elements that use scripting are keyboard accessible and provide textual equivalents.
(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 The AMP platform provides links to launch the InFocus companion application via Java Webstart. Launching of InFocus requires Java 1.6. Instructions for downloading and installing Java can be found in AMP’s reference Wiki located with the Learning Center tab of AMP. If Java is not found, a message is displayed directing the user to a link where Java can be downloaded.
(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 All form elements within AMP are properly labeled and all forms are designed to be completed and submitted with accessibility in mind. Form fields have explicit labels or title attributes. These labels also include notation for required fields and other constraint information. Error and instruction messages are displayed prior to the form. Form fields are laid out in an intuitive manner.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports A “Skip Navigation” hyperlink is present on every screen within AMP. This link allows users to navigate to the main content area.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable Timed responses are not required by AMP.
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
Voluntary Product Accessibility Template
Criteria Support Level 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
(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols. Not Applicable
(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs. Not Applicable
(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
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
(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
(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
(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
(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
(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
(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
(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
(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
(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

Return to the top of the page.

Section 1194.24 Video and Multi-media Products
Voluntary Product Accessibility Template
Note: Adobe Captivate based training courses are covered here.
Criteria Support Level 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
(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. Not Applicable
(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
(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
(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. Not Applicable

Return to the top of the page.

Section 1194.25 Self-Contained, Closed Products
Voluntary Product Accessibility Template
Criteria Support Level 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
(b) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable
(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
(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
(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
(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
(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
(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
(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
(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
(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
(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
(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

Return to the top of the page.

Section 1194.26 Desktop and Portable Computers
Voluntary Product Accessibility Template
Criteria Support Level Remarks and Explanations
(a) All mechanically operated controls and keys shall comply with §1194.23 (k) (1) through (4). Not Applicable
(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
(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
(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards. Not Applicable

Return to the top of the page.

Section 1194.31 Functional Performance Criteria
Voluntary Product Accessibility Template
Note: This section covers all AMP components including the AMP web UI, the Infocus Java application and the InFocus Toolbar for InternetExplorer.
Criteria Support Level 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. AMP Web: Supports AMP Web supports the technical requirements of Section 508 and allows full access for users with no vision. Users without vision typically rely on keyboard access, textual equivalents, form fields that provide explicit labels/title, and other structural markup such as correct data table, list, and heading elements.
AMP InFocus: Supports with Exceptions The InFocus companion application utilizes the Java Accessibility API to ensure compatibility with assistive technologies such as screen readers and braille devices. However some UI elements such as the InFocus Desktop UI may not function correctly with all assistive technologies such as VoiceOver on the Macintosh. Screen reader users rely on keyboard access and properly label user interface elements for accessibility. Full keyboard access is provided in InFocus.
AMP InFocus Toolbar: Supports with Exceptions The InFocus toolbar provides accessibility via Microsoft Active Accessibility (MSAA) and UIA interfaces however a small number of controls lack accessible names. Screen reader users rely on keyboard access and properly label user interface elements for accessibility. Full keyboard access is provided in the InFocus toolbar with two exceptions, the color contrast eye dropper tool and the select from mouse DOM node selector.
(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. AMP Web: Supports AMP Web, InFocus, and the InFocus toolbar provide support for low vision users by following high contrast mode set in the OS, by honoring browser color settings, supporting zooming in the browser, and being compatible with screen magnification software. These settings and assistive technologies are often used by people with low vision.
AMP InFocus: Supports with Exceptions InFocus provides support for custom color schemes on most screens however in some cases this support is incomplete resulting in only partial color changes which may render text unreadable. InFocus is compatible with screen magnification and works with the speech components of screen enlargement software like ZoomText.
AMP InFocus Toolbar: Supports InFocus toolbar provides full support for custom color schemes such as high contrast, is compatible with magnification software, and provides features to enlarge the code area text and change the font.
(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 Sound is not utilized or required for any features within AMP.
(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 Sound is not utilized or required for any features within AMP.
(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 AMP does not require user speech in any way.
(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. AMP Web: Supports All AMP Web functionality is possible without fine motor control or simultaneous action. AMP Web can be used completely with voice recognition software, on-screen keyboards, and from the keyboard. AccessKeys are provided for common features, skip navigation links are present and AMP web is compatible with assistive technology used by people with mobility impairments.
AMP InFocus: Supports InFocus is fully keyboard accessible and works with assistive technology used by people with mobility impairments. Many people with mobility impairments use the keyboard or assistive technology that simulates the keyboard.
AMP InFocus Toolbar: Supports with Exceptions Nearly all InFocus toolbar functionality can be access via the keyboard. It provides some functionality such as the element selection tool and the color contrast eye dropper that requires the use of the mouse This functionality however is supplemental to the overall use of the product and not required to capture the document object model, screen shots, and JavaScript/CSS. Color contrast information can be entered manually using RGB hexadecimal values.

Return to the top of the page.

Section 1194.41 Information, Documentation and Support
Voluntary Product Accessibility Template
Criteria Support Level 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 Upon request, alternate, accessible formats of any documentation will be supplied by SSB at no additional charge. Please contact for additional information:contact@ssbbartgroup.com.
(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 Upon request, alternate, accessible formats of any documentation will be supplied by SSB at no additional charge. Please contact for additional information:contact@ssbbartgroup.com.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports SSB provides support services in multiple accessible formats. For example, phone, web based forms, email, instant message, and TTY relay methods are provided as support options. Please contact for additional information:contact@ssbbartgroup.com

Put yourself on the path to complete accessibility!

Just fill out the form below and we’ll contact you to set up your free consultation with an expert specializing in your industry.

If you need more immediate assistance, please send an email to info@ssbbartgroup.com or call (800) 889-9659. We look forward to helping you!