Community Templates for Self-Service

Transcription

1 Voluntary Product Accessibility Template (VPAT) February 2016 This Voluntary Product Accessibility Template, or VPAT, is a tool that helps officials and decision-makers to evaluate design conformance the accessibility standards under Section 508 of the Rehabilitation Act. The scope of this VPAT includes the, which includes: Koa, Kokua and Napili. Community templates for self-service are custom branded by community powered users to meet the communities business need. Name of the Product: Version: Last Release Date: 2/16/2016 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 Criteria Compliance Section Software Applications and Operating Systems Section Web-based internet information and applications Section Telecommunications Products Section Video and Multi-media Products Section Self-Contained, Closed Products Section Desktop and Portable Computers Section Functional Performance Criteria Section Information, through equivalent Documentation, and Support facilitation Page 1 of 10

2 Section Software Applications and Operating Systems Detail Criteria (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. All core features and user interface controls in the Community Templates for Self-Service such as Kokua, Koa and Napili are reachable by using the keyboard alone when accessed desktop and touch events whenever accessed mobile devices (ios and Android). They may be executed using the Tab key and other touch events/keys, as required by the criteria. However, there is an exception to this, including the following: In Android devices TalkBack enabled, list view detail information displayed in My Cases, Accounts, Contacts and Records List page for the Napili, Kokua and Koa template screens are not reachable by using on-screen touch methods and announced by assistive technology. user interface and controls do not disrupt, deactivate, or interfere the accessibility features of the Windows, ios and Android operating systems such as filter keys, toggle keys or sticky key, inverse colors and Zoom. A clear visual indication of the current focus or touch event for all of the interactive interface elements is provided in the Community Templates for Self-Service user interface and controls. Page 2 of 10

3 Criteria (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. (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. user interface and interactive elements do contain proper information related to WAI-ARIA identity, role, operation and state to help assistive technology. Functional images in the community templates have proper alternative text following exception: Selected items that are depicted visually the Check icon in menus are not announced by assistive technology whenever accessed desktop and mobile devices (ios and Android) in the Feeds, Topics pages. Images that support programmatic elements are used consistently in the Community Templates for Self- Service functionality to represent certain functions or identify interactive controls. Textual information is available to assistive technology in the functionality. user interface and controls remains visible in Windows operating system High Contrast mode and respects the ios and Android operating system inverse color settings and does not override any default contrast settings. has no core features or functionality that utilize animation resulting in moving, blinking, or scrolling information for interactivity. Animation is only used in the form of loading image which does not contain any textual information available to assistive technology. Page 3 of 10

4 Criteria (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. user interface does not use color alone as a means of conveying information or to indicating any action. The community templates powered users are allowed and permitted to customize, apply and brand variety of different color themes to their site template. user interface has no flashing or blinking text, objects or other elements greater than 2Hz and lower than 55Hz. The electronic form controls in the user interface can be operated and accessible by using assistive technology. The form label elements in the community templates are properly associated and placed in-line for the form fields. Page 4 of 10

5 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). (b) Equivalent alternatives for any multimedia presentation shall be synchronized the presentation. (c) Web pages shall be designed so that all information conveyed color is also available out color, for example from context or markup. (d) Documents shall be organized so they are readable out requiring an associated style sheet. Support Images used in the Community Templates for Self-Service user interface have meaningful alternative (alt) text descriptions. Non-relevant or decorative images have null alt attributes or are inserted as a CSS background image. does not include or have any multimedia videos/presentations. does not use color alone to distinguish the importance of a visual element. The core user interface and functionality for Community Templates for Self-Service are provided sufficient color contrast between foreground and background text colors for easy and clear legibility for people moderately low vision, except for some textual information presented in the Login, Password Reset, Articles and New Case pages do not meet the minimum standards. e: The community site powered users are allowed and permitted to customize, apply and brand variety of different color themes to their site template. The changes in the community template theme colors and style made by powered users has the potential to produce negative impact on color contrast settings as required by the criteria. is a web-based application (not a document). To work correctly, its user interface and controls require the use of associated style sheets. Page 5 of 10

6 Criteria (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 an available geometric shape. (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 text that facilitates frame identification and navigation (j) Pages shall be designed to avoid causing the screen to flicker a frequency greater than 2 Hz and lower than 55 Hz. (k) A text-only page, equivalent information or functionality, shall be provided to make a web site comply 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. does not use any server-side image maps. does not use any client-side image maps. Data tables header column in the core functionality are properly identified using the <th> and scope element. Currently, there are no pages or screens in the Community Templates for Self-Service core functionality and features that contain data tables more than one logical level of either column or row headers. core features and user interface does not contain and use frames to deliver content for interactivity. functionality and user interface does not cause the screen to flicker a frequency greater than 2Hz and lower than 55Hz. Text only pages are not required because the Community Templates for Self-Service core user interface and its features have been coded to meet applicable standards, to the extent specified. Page 6 of 10

7 Criteria (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified 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 (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. The Community Templates for Self- Service core functionality and its features relies on scripting technology, WAI-ARIA and the other modern HTML5 techniques to interact different UI elements. This allows assistive technology such as screen readers to read and transmit information back to the user an exception. The hidden underneath content are accessible the use assistive technology that display other information whenever Search Filter and Select Files screen is accessed ios and Android devices in the Kokua and Koa self-service template which makes it difficult for users to understand the screen information. core functionality and its features does not require any applet or plug-in to work its default functionality. The electronic form controls in the user interface can be operated and accessible by using assistive technology. Some of the form labels elements in the community templates are associated and placed in-line for the form fields. does not include traditional skip repetitive navigation link method. But, contains headings to allow assistive technology users navigate and bypass to different sections of the page. does not require a timed response as part of its core functionality. Page 7 of 10

8 Section Functional Performance Criteria Detail Criteria (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. Most of the core features and user interface controls in the such as Kokua, Koa and Napili sites functionality are reachable by using the keyboard alone when accessed desktop and touch events whenever accessed mobile devices (ios and Android) and/or provide support for assistive technology. However, there are an to this, including the following: The Mention menu items functionality displayed in the Post section are not announced by screen reader. The menu items are accessible use of keyboard (up and down arrow keystrokes), but the same menu information is not announced by assistive technology. The tooltip information available on the Information icon displayed in the Napili community template My Settings page in the profile visibility section is not announced by the assistive technology whenever it s accessed Internet Explorer browser and Android device. Alerts and form error messages used in Community Templates for Self- Service are not announced by assistive technology. Refer to the following sections for more details regarding other : (a), (d); (l) Page 8 of 10

9 Criteria (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 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 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 limited reach and strength shall be provided. user interface supports screen magnification and browser and mobile device (ios and Android) provided zoom functionality. 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. functionality does not require user speech. functionality does not require fine motor control or simultaneous actions. Community templates 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 9 of 10

10 Section Information, Documentation and Support Detail Criteria (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 disabilities. equivalent facilitation Salesforce provides electronic versions of all product support documentation related to. Users disabilities can request additional product support documentation by opening a new case at Salesforce provides information on the features in the documentation by going to HelpDoc?id=networks_overview.htm&lan guage=en_us. Accessibility related documentation related to Salesforce and can be access by going to Support service related to Community Templates for Self-Service functionality can be found at the Salesforce.com website. Currently, telephone communication provision does not support TTY or relay services. Users disabilities can open support request directly at Page 10 of 10