Accessibility for Confluence VPAT for Section 508 compliance

Voluntary Product Accessibility Template™ (VPAT™) Version 1.3 (July 12, 2016)

The purpose of the Voluntary Product Accessibility Template, or VPAT^™, is to assist Federal contracting officials and other buyers in making preliminary assessments regarding the availability of commercial “Electronic and Information Technology” products and services with features that support accessibility. It is assumed and recommended that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template 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. The second column describes the supporting features of Accessibility for Confluence or refers you to the corresponding detailed table, e.g., “equivalent facilitation." The third column contains any additional remarks and explanations regarding the product.

In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.

Date: September 7, 2018

Name of Product: Accessibility for Confluence Version 2.1.1 (January 2018)

Contact for more Information: Create a support request

Coverage:

This document covers the following areas of Confluence:

Area

Login

Dashboard

Viewing pages

Creating/editing pages

Creating/editing comments

At this time, other areas of functionality are not in the scope of this document and should be interpreted as "Does not support".

Summary

Criteria	Supporting Features by Accessibility for Confluence	Remarks and explanations
Section 1194.21 Software Applications and Operating Systems	Not applicable
Section 1194.22 Web-based Internet Information and Applications	Supports with exceptions	See below
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	See below
Section 1194.41 Information, Documentation and Support	Supports

Section 1194.22 Web-based Internet information and applications – Detail

Criteria	Supporting Features by Accessibility for Confluence	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 with exceptions	Some icons do not offer a text equivalent: progress spinner session expired warning checkboxes Macro Images in editor mode table sorting symbols keyboard shortcuts dialog missing text equivalent for emoticons You can use screen reader mode for an optimized view with reduced amount of non-text equivalents. By using High Contrast Mode all icons are automatically replaced with text to help users operate the editor.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	Not applicable	Content producers can include various types of media like audio and video files inside a confluence site. These media may not be fully accessible. The content producer is responsible to offer alternatives like synchronized captions and audio descriptions.
(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 with exceptions	Some functions, such as the change history, use color differentiation as an explanation. The color picker available in the editor does not provide a tooltip when focusing/hovering over a color. Instead markup can be used to make text colorful in text areas.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.	Supports	Content is still readable and understandable, even if the style sheet is turned off.
(e) Redundant text links shall be provided for each active region of a server-side image map.	Not applicable	Accessibility for Confluence does not make use of 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	Accessibility for Confluence does not make use of image maps.
(g) Row and column headers shall be identified for data tables.	Supports	Row and column headers are correctly identified in data tables by using the <th> element.
(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.	Not applicable	No data tables discovered with more than one level of headers.
(i) Frames shall be titled with text that facilitates frame identification and navigation	Supports	Each frame is assigned a title that adequately describes the purpose of the frame.
(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	The product does not contain any flickering content.
(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.	Supports	Accessibility for Confluence offers a screen reader mode to display a simplified text version of the actual page. In order to be able to edit pages in screen reader mode, they must first have been created with a template specially optimized for the screen reader . The content producer is responsible for providing text-only content for pages.
(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 with exceptions	Most of the content and interface elements can be can be reached with tab control and can be read with screen reader software. Exceptions are: tooltips for user icons are not keyboard/screen reader operable the space tools menu is not keyboard/screen reader operable date picker is not keyboard/screen reader operable mention menu not screen reader operable Suggestions from input fields in some macros are not read to screen reader users most checkboxes are not keyboard or screen reader operable
(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).	Not applicable	Accessibility for Confluence is an app for Atlassian Confluence and does not require any applets, plugins or other applications other than Confluence to be present on the client system in order to display the page content.
(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 with exceptions	Most forms and buttons are accessible to assistive technologies with exception of: Login page has no text alternative for error dialog after entering incorrect login data If no matches could be found via the user search field of a macro, this information only appears visually. The Information is not read to screen reader users Entered labels in Create how to article are not read to screen reader users most checkboxes are not keyboard or screen reader operable date picker is not keyboard/screen reader operable
(o) A method shall be provided that permits users to skip repetitive navigation links.	Supports	Accessibility for Confluence provides links to skip the navigation, both in standard mode and in screen reader mode.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.	Not applicable	Accessibility for Confluence does not require a timed response for its functionality.

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

Criteria	Supporting Features by Accessibility for Confluence	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.	Supports with exceptions	Accessibility for Confluence can be used with a screen reader such as JAWS, NVDA or macOS VoiceOver. Exceptions where screen reader are not operable are shown in Section 1194.22 (l)
(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.	Supports	Accessibility for Confluence can be used with a screen reader such as JAWS, NVDA or macOS VoiceOver.
(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	Hearing is not required to operate or retrieve information.
(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	Audio information is not required for the use of the product.
(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	Speech is not required as an input or user interface control method.
(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.	Supports	A keyboard can be used for navigation and text input.

Section 1194.41 Information, Documentation and Support – Detail

Criteria	Supporting Features by Accessibility for Confluence	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	Electronic versions of product documentation are available online. Alternate formats available upon request.
(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	Accessibility for Confluence features listed in product documentation online. Alternate formats available upon request.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities.	Supports	Support for Communardo products is available in a variety of formats.

Communardo Knowledge Base