Voluntary Product Accessibility Template – PowerBroker for Unix & Linux

The VPAT (Voluntary Product Accessibility Template) product is a tool developed by ITIC (Information Technology Industry Council) and government GSA (Government Services Administration) to help facilitate the market research responsibilities of Federal IT professionals by enabling government requestors to compare vendor products. In recognition and support of the “Electronic and Information Accessibility Standards” defined by Section 508 of the Rehabilitation Act, BeyondTrust publishes accessibility self-assessments of our products using VPATs. BeyondTrust’s engineering teams update the VPATs for their products during each major release cycle to reflect accessibility improvements contained in the latest release.
Date: April 4, 2016
Product Name: PowerBroker for Unix & Linux
Version: 9x

Summary Table Section 508 Voluntary Product Accessibility Template

Criteria Supporting Features Remarks and explanations
Section 1194.21 Software Applications and Operating Systems Supported, PowerBroker for Unix & Linux Least Privilege and Auditing Tool for Unix and Linux
Section 1194.22 Web-based internet information and applications Supported, BeyondInsight 5.x provides reporting for PowerBroker for Unix & Linux Optional reporting consoles for PBUL
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 Supported, Attached VPAT PowerBroker for Unix & Linux

Section 1194.21 Software Applications and Operating Systems - Detail 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. Supported PowerBroker for Unix & Linux is fully command line driven
(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 PowerBroker for Unix & Linux will not alter the display or accessibility features in any way
(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 (If supported by connecting client) PowerBroker for Unix & Linux will not interfere with the capabilities provided by the client being used to access the system. However focus type functionality would have to be provided by the connecting client and not the operating system or PowerBroker for Unix & Linux running on that system.
(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 The solution uses a standard paradigm throughout the product to label interactive graphics and bitmaps for ease of use and adaptive technologies.
(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 PowerBroker for Unix & Linux is mostly command-line driven and will display feedback inline with whichever terminal emulator is being used. Most terminal emulators allow for a customized appearance to the users choosing.
(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. Supported The only animation in PowerBroker for Unix & Linux is session playback. Session data can be viewed statically or in an automated fashion using runtime switches in the pbreplay utility.
(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 PowerBroker for Unix & Linux will honor the terminal emulation and system display settings.
(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 PowerBroker for Unix & Linux will honor the terminal emulation and system display 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. Supported PowerBroker for Unix & Linux will honor the terminal emulation and system display settings.
(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 PowerBroker for Unix & Linux will honor the terminal emulation and system display settings.

Section 1194.22 Web-based Internet Information and 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). Supported with conditional exceptions. When possible, the solution uses tool tips and other methods to display text equivalents.
(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. Supported with conditional exceptions Color is not the only vehicle used to convey the disposition of data elements but is helpful in quickly identifying data items by design.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supported Data export to web based solutions does not require a style sheet either.
(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable The solution does not include the use of 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. Not Applicable The solution does not include the use of client-side image maps.
(g) Row and column headers shall be identified for data tables. Supported
(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. Supported
(i) Frames shall be titled with text that facilitates frame identification and navigation Not Applicable The solution does not use HTML Frames for rendering data
(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. Not Applicable There are no text only frames generated by the solution. All rendering is done through Adobe Flash or Microsoft Silverlight.
(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. Supported
(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). Supported with conditional exceptions The Adobe Flash plugin and MS Silverlight plugin are required to interpret page content. The application provides a link to the plugin if it is not installed and will not function unless it is downloaded and installed correctly.
(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. Supported Form fields are displayed in a logical tab order and all information necessary to properly complete the form is viewable on the page and can be navigate with a keyboard, mouse, and assistive technology.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supported The solution does not use a repetitive navigation section.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable The solution has no timed based response required input.

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. Supported with conditions – See explanation Must be provided/supported by the users’ terminal emulator and/or operating system. PowerBroker for Unix & Linux is primarily command-line driven and operates post logon to the native operating system, the operating system itself or terminal emulation program used to access the operating system would be required to support vision impaired users.
(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 with conditions – See explanation Must be provided/supported by the users’ terminal emulator and/or operating system. PowerBroker for Unix & Linux is primarily command-line driven and operates post logon to the native operating system, the operating system itself or terminal emulation program used to access the operating system would be required to support vision impaired users. For example, set the font size to a desired value for the visually impaired user.
(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 Not Applicable The solution does not contain any audible alerts
(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. Not Applicable
(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. Not Applicable The solution does not require any speech for normal operation
(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

Section 1194.41 Information, Documentation and Support - Detail 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 Supported with conditional exceptions Documentation can be provided in hard copy and electronic formats that are compatible with accessibility technology.
(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 with conditional exceptions This is supported to the extent that technical support can properly use diagnostic tools to support the solution.
Software Applications and Operating Systems (1194.21) Most of the specifications for software pertain to usability for people with vision impairments. For example, one standard requires alternative keyboard navigation, which is essential for people with vision impairments who cannot rely on pointing devices, such as a mouse. Overview of Software Application and Operating Systems standards:
  • Execute product functions from a keyboard, when software is designed to run on a system with a keyboard and the function or the result of performing the function can be discerned textually.
  • Do not disrupt or disable activated accessibility features of other products, where those features developed and documented according to industry standards. Do not disrupt or disable activated accessibility features of any operating system, where application-programming interface for those features has been documented by the operating system manufacturer and is available to the product developer.
  • Visual focus indicators. Provide well-defined and programmatically exposed visual focus indicator for interactive interface elements as input focus changes so assistive technology can track focus and focus changes.
  • User interface element. Provide information to enable assistive technology to understand the identify, operation, and state of the element. When an image represents a program element, information conveyed by the image must also be available in text.
  • Bitmap images. Must be assigned consistent meaning throughout application's performance when used to identify controls, status indicators, or other programmatic elements.
  • Textual information. Provide textual information through operating system functions for displaying text, including text content, text input caret location, and text attributes.
  • Display attributes. Do not override user-selected contrast and color selections and other individual display attributes.
  • Animation. Display information in at least one non-animated presentation mode at option of user when animation displayed.
  • Color coding. Do not use color coding as only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
  • Color and contrast settings. Provide variety of color selections capable of producing a range of contrast levels when a product permits a user to adjust color and contrast settings.
  • Flashing or blinking text. Do 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.
  • Electronic forms. Provide a format that allows access via assistive technology to information, field elements, and functionality required for completion and submission of the form, including directions and cues.