Serena Software Voluntary Product Accessibility Report. Summary Table

Transcription

1 Serena Software Voluntary Product Accessibility Report Date: October 22, 2015 Name of Product: Serena Business Manager Contact for more Information (name/phone/ ): Dave Easter / [email protected] Summary Table Criteria Section Software Applications and Operating Systems Section Web-based Internet Information and Applications Section Functional Performance Criteria Section Information, Documentation and Support Supporting Features Remarks and explanations Return to the top of the page. Section 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 The Accessible Interface supports executing all product functions from a keyboard. Please refer to Serena Business Manager User's Guide for more details

2 function itself or the result of performing a function can be discerned textually. (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. (c) A well-defined onscreen 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. (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 regarding how to enable the Accessible Interface. We are not aware of any such disruptions within any of the SBM components. The Accessible Interface supports this functionality as provided by the web browser. For example, HTML elements in focus are highlighted with a "dashed box outline", blinking cursors within a text entry field, etc. In the Accessible Interface, we provide text for user interface elements, as outlined by web standards. For example, we supply text values in the alt, title, value, summary, label and other appropriate attributes for a given element.

3 information conveyed by the image must also be available in text. (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. (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. (g) Applications shall not override user selected contrast and color selections and other individual display attributes. (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. with with Note: Images are not used in SBM Accessible Web Interface. Bitmap images are not initially provided or displayed in SBM components The Accessible Interface utilizes the Windows standards for the browser interface. For example, in the listed components, text input areas display the text that is being input and also displays a text caret when as you enter the text. The Accessible Interface does not override user s specified display attributes. For the Standard Interface, the color and font values can overridden by most browsers (for example Firefox and IE) through optional settings. Animations are provided during the initial presentation of some graphical components like charts or transitioning between UI states, however the animation does not convey information not available through other means.

4 (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. (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. (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. with with Color is used to designate required fields, status of items in views and sections within graphs, however the accompanying text is provided to explicitly convey this same information. Color is used for warning/error messages, however the text itself communicates meaning clearly. The Serena Business Manager Standard Web Interface allows users to select different colors for thresholds for distribution reports, but the color choices may not meet this criterion. Report creation is not provided via the Accessible Interface, and certain report types such as distribution reports are not available within the Accessible Interface. No such elements are initially provided or displayed in the various SBM components.

5 (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. with For the Accessible Interface, keyboard navigation is provided for all forms and form elements. All form elements are labeled appropriately with text that is accessible by Assistive Technologies. There may be a few nonstandard control types, such as the date picker and multiselection fields, within forms for the Standard Interface. Return to the top of the page. Section Web-based Internet information and applications Detail Criteria (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Supporting Features with Remarks and explanations All non-text elements have text equivalents.

6 (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. (d) Documents shall be organized so they are readable without requiring an associated style sheet. (e) Redundant text links shall be provided for each active region of a server-side image map. with with No multimedia is initially provided or displayed in the various SBM components. Color is used to designate required fields, status of items in views and sections within graphs, however the accompanying text is provided to explicitly convey this same information. Color is used for warning/error messages, however text communicates meaning clearly on its own. The Accessible Interface is coded to meet the standards for this criterion. No server-side images maps are initially provided or displayed in any of the various SBM components.

7 (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. with No client-side images are used within the Accessible Interface. Within the Standard Interface, text links are provided for images maps used in rich graphical reports (FusionCharts). Exceptions: (g) Row and column headers shall be identified for data tables. (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. (i) Frames shall be titled with text that facilitates frame identification and navigation. (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. N/A N/A N/A N/A No data tables are used within the Accessible Interface. No data tables are used within the Accessible Interface. No frames are used within the Accessible Interface. No flickering elements are displayed within any of the various SBM components.

8 (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 textonly page shall be updated whenever the primary page changes. (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. (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 N/A SBM is compliant out of the box, but if customers choose, they can create process apps and add content to custom SBM s standard interface is compliant, but as an extra measure, SBM additionally provides text-based Accessible Interface pages as an option from the Standard Web Interface User Profile page. The Accessible Interface is coded to meet the standards for this criterion. Plugins are not utilized within the Accessible Interface.

9 with (a) through (l). (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. (o) A method shall be provided that permits users to skip repetitive navigation links. (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. "Label for" attributes are generated for field labels. Id" attributes are generated for their corresponding field values. The Accessible Interface provides simple navigation and refrains from repeating unnecessary navigation links based on the content of the page. For the Standard Interface, users can bookmark reports, items, forms that can be accessed outside of the application. Users can also access Quicklinks (Favorites) that can be used to skip repetitive navigation links inside the Standard Interface application. No timed response is required in any of the SBM components. Note to : 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 ) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1,

10 (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) , (j) - 7.1, (k) Return to the top of the page. Section 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. (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. (c) At least one mode of operation and information retrieval with with We provide an alternate set of text-based Accessible Interface pages as an option from the Standard Web Interface User Profile page. Please refer to Serena Business Manager User's Guide for more details regarding how to access the Accessible Interface. Both the standard and accessible modes for the SBM Web interface support text resizing via browser user preferences. The Accessible mode of SBM Web Interface supports Assistive Technology. The Editable Grid in the Standard Interface does not meet this criterion for the classic SBM User Interface. However, the Editable Grid for SBM Work Center is fully compliant. SBM does not require user hearing.

11 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. (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. (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. (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. with with SBM does not require user hearing. SBM does not require user speech. The Accessible Interface can be run with simple keystrokes (e.g., tab, space, alpha keys, ALT) and does not require fine motor controls or simultaneous actions.

12 Return to the top of the page. Section Information, Documentation and Support Detail Criteria Supporting Features Remarks and explanations (a) Product support documentation provided to endusers shall be made available in alternate formats upon request, at no additional charge. with Product documentation is available as online help files in HTML format. Documentation is accessible to end-users from the browser UI. There is a help icon on top of the browser interface that takes end-users to the online documentation. (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. with Product documentation is also available in PDF format. The PDF versions are not accessible. End-user documentation is available as online help files in HTML format. Documentation is accessible to end-users from the browser UI. There is a help icon on top of the browser interface that takes end-users to the online documentation. (c) Support services for products shall accommodate the communication End-user documentation is also available in PDF format. The PDF versions are not accessible. Serena provides technical support for all of its products through , voice

13 needs of end-users with disabilities. (telephone), fax, and documentation. Phone number for Support in the US is Support can also be contacted during work week hours at Up-to-date product news and answers to many questions can be found on the Serena support website at In addition, support cases can be created online at Return to the top of the page.