Salesforce Lightning App Builder

Transcription

1 Voluntary Product Accessibility Template (VPAT) December 2015 This Voluntary Product Accessibility Template, or VPAT, is a tool that helps officials and decision-makers to evaluate Salesforce Lightning Experience design conformance with the accessibility standards under Section 508 of the Rehabilitation Act. The scope of this VPAT includes user interface. The features includes creating new and editing app builder view for the application. Salesforce Lightning Experience and Service Cloud features are captured in the different VPAT. Name of the Product: Version: Last Release Date: 10/17/2015 Point of Contact Name/ accessibility@salesforce.com The first table of the VPAT document 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. Summary Table Applicable Compliance Section Software Applications and Operating Systems Applicable Section Web-based internet information and applications Applicable with exceptions Section Telecommunications Products Section Video and Multi-media Products Section Self-Contained, Closed Products Section Desktop and Portable Computers Section Functional Performance Applicable with exceptions Section Information, through equivalent Applicable Documentation, and Support facilitation Page 1 of 9

2 Section Software Applications and Operating Systems Detail (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. (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 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. (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. (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. features and user interface controls are reachable by using the keyboard alone. They may be executed using the Tab key and other keys, as required by the criteria. user interface and controls do not disrupt, deactivate, or interfere with the accessibility features of the Windows operating system such as filter keys, toggle keys or sticky keys. A clear visual indication of the current focus for all of the interactive interface elements is provided within the Salesforce Lightning App Builder user interface and controls. user interface and interactive elements do contain proper information related to WAI-ARIA identity, role, operation and state to help assistive technology. Images that support programmatic elements are used consistently within the Salesforce Lightning App Builder functionality to represent certain functions or identify interactive controls. Page 2 of 9

3 (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. (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. (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. Textual information is available to assistive technology within the functionality. user interface and controls remains visible in Windows operating system High Contrast mode. has no core features or functionality that utilize animation for interactivity. user interface does not use color alone as a means of conveying information or to indicating any action. The user is not allowed or permitted to adjust color and contrast settings in the Salesforce Lightning App Builder functionality user interface. user interface has no flashing or blinking text, objects or other elements greater than 2Hz and lower than 55Hz. Electronic form controls in the user interface can be operated with the keyboard and provide proper reading information with the use of assistive technology. Page 3 of 9

4 Section Web-based Internet information and applications Detail (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (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. (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 exceptions Most of the images in the user interface have meaningful alternative (alt) text descriptions. Non-relevant or decorative images have null alt attributes or are inserted as a background image, with the following exceptions: The Information and Delete icons that are displayed on the Lightning App Builder main edit page right panel area does not contain informative alternative textual information to help assistive technology users. does not include or have any multimedia videos/presentations. does not use color alone to distinguish the importance of a visual element. Lightning App Builder user interface is provided with sufficient color contrast between foreground and background text colors for easy and clear legibility for people with moderately low vision. The Salesforce Lightning App Builder is a web-based application (not a document). To work correctly, its user interface and controls require the use of associated style sheets. does not use any server-side image maps. does not use any client-side image maps. Page 4 of 9

5 (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. (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. (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 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. does not use any data tables to display information. Currently, there are no data table within the Salesforce Lightning App Builder that contain data tables with more than one logical level of either column or row headers. Iframes within the Salesforce Lightning App Builder user interface contains the proper title attributes to support assistive technology. does not cause the screen to flicker with a frequency greater than 2Hz and lower than 55Hz. Text only pages are not required because the Salesforce Lightning App Builder user interface and its features have been coded to meet applicable standards, to the extent specified. All core Salesforce Lightning App Builder functionality relies on scripting technology, WAI-ARIA and the other modern HTML5 techniques to interact with different UI elements. This allows assistive technology such as screen readers to read and transmit information back to the user. The Salesforce Lightning App Builder functionality does not require any applet or plug-in to work with its default functionality. Electronic form controls in the user interface can be operated with the keyboard and provide proper reading information with the use of assistive technology. Page 5 of 9

6 (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. pages does not contain traditional Skip to navigation link but instead alternative navigation method is provided in the form of different keystrokes such as Alt+ 1, 2, 3, 4 and 5 to allow users navigate and bypass to different section of the page. Users are alerted within the pages with time response modal window and provided options to select additional time for continuing the login session. Page 6 of 9

7 Section Functional Performance Detail (a) At least one mode of operation and 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 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 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. with exceptions Most of the features and user interface controls within the are reachable by using the keyboard alone or provide support for assistive technology. However, there are an exceptions to this, including the following: The tooltip information available on the Information icon displayed within the Lightning App Builder right panel area are not announced by the assistive technology. List items displayed within the Object modal window are not announced by assistive technology when it s navigated using up and down arrow keys. user interface supports screen magnification and browserprovided zoom functionality. The Salesforce Lightning App Builder functionality does not rely on sound alone or user hearing to access any of its core functionality. functionality does not rely on audio to present information. Page 7 of 9

8 (e) At least one mode of operation and 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 fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. functionality does not require user speech. The Salesforce Lightning App Builder functionality does not require fine motor control or simultaneous actions. Lightning App Builder user interface and controls have large target areas that do not cause problems for people who have limited fine motor control or limited reach and strength. Page 8 of 9

9 Section Information, Documentation and Support Detail (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge (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. (c) Support services for products shall accommodate the communication needs of end-users with disabilities. with equivalent facilitation Salesforce provides electronic versions of all product support documentation related to Lightning App Builder. Users with disabilities can request additional product support documentation by opening a new case at Salesforce provides information on the Salesforce accessibility features in the documentation. Accessibility related documentation can be access by going to Support service related to the Salesforce Lightning App Builder functionality can be found at the Salesforce.com website. Currently, telephone communication provision does not support TTY or relay services. Users with disabilities can open support request directly at Page 9 of 9