Adobe Accessibility Conformance Report
VPAT® Version 2.0 – October 2017
Product Information
- Name of Product/Version: Adobe Connect Central 10.0.0
- Product Description: Online virtual classrooms, webinars, meetings, and conferences.
- Date: October 2018
- Contact information: access@adobe.com
- Notes: This report provides separate descriptions for the Adobe Connect Central component and its authored content.
- Web contains the administration functions of Adobe Connect Central.
- Authored Content (HTML) includes web pages, such as Adobe Connect events.
The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
- Evaluation Methods Used: Testing Adobe Connect involved extensive use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards/guidelines:
Level A - Yes
Level AA - Yes
Level AAA - No
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Supports with Exceptions: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.0 Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Section 1: Success Criteria, Level A
Notes:
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.1 (Web)
- 10.2.1 (non-web document)
- 11.2.1.1 (Software)
- 11.2.2.1 (Closed Functionality Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (HTML): Supports with Exceptions
Web: The product provides text equivalents for some non-text content, such as some images. However, text equivalents are missing in most product functions. Examples include:
Most images, including decorative images and images which represent content or functionality, are missing text alternatives.
Non-text content rendered using Flash, such as graphs in product dashboards, does not expose a text equivalent to screen readers.
States indicated using images, such as selection or sort direction, are missing text alternatives.
Authored Content (HTML): A text equivalent or descriptive name is provided for most non-text content, such as images and input fields. Exceptions include:
In the Event Registration page, after the user chooses a value of a select control with custom values, the accessible name of the control conveys the chosen value instead of the purpose of the control.
Guideline 1.2 Time-based Media
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.2 (Web)
- 10.2.2 (non-web document)
- 11.2.1.2 (Software)
- 11.2.2.2.1 and
- 11.2.2.2.2 (Closed Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not provide its own prerecorded media.
Authored Content (HTML): Authored content does not contain prerecorded media.
1.2.2 Captions (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.3 (Web) 10.2.3 (non-web document) 11.2.1.3 (Software) 11.2.2.3 (Closed Software) – Does not apply 11.6.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not provide its own prerecorded media that would require captions.
Authored Content (HTML): Authored content does not contain prerecorded media.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.4 (Web)
- 10.2.4 (non-web document)
- 11.2.1.4 (Software)
- 11.2.2.4 (Closed Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not provide its own prerecorded video content that would require audio description or a media alternative.
Authored Content (HTML): Authored content does not contain prerecorded media.
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.7 (Web)
- 10.2.7 (non-web document)
- 11.2.1.7 (Software)
- 11.2.2.7 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (HTML): Supports with Exceptions
Web: Authors can provide appropriate element semantics for most visual structure and relationships. Examples include:
Column headers for most data tables are not defined programmatically.
Most form field constraints, such as “Max length = 4000 characters” on the New Meeting page, are not programmatically associated with their form fields.
Programmatic relationships between group labels and the individual controls within each group are not defined.
Most headings are not defined programmatically.
On report pages and dashboard pages, most information in Flash content is not available to assistive technology.
Authored Content (HTML): Authors can provide appropriate semantics for content elements, with the following exceptions:
Page content is inside of a layout table which is not marked as “presentational”.
Most headings are not defined programmatically.
1.3.2 Meaningful Sequence (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.8 (Web)
- 10.2.8 (non-web document)
- 11.2.1.8 (Software)
- 11.2.2.8 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product presents content in a meaningful sequence.
Authored Content (HTML): The product allows authors to present content in a meaningful sequence.
1.3.3 Sensory Characteristics (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.9 (Web)
- 10.2.9 (non-web document)
- 11.2.1.9 (Software)
- 11.2.2.9 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: Instructions do not rely solely on sensory characteristics.
Authored Content (HTML): Authors can ensure that content meets this criterion.
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.10 (Web)
- 10.2.10 (non-web document)
- 11.2.1.10 (Software)
- 11.2.2.10 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most functions of the product do not convey information through color alone. Exceptions include:
In pages such as Admin, Content, Seminars, and Profile, the currently active tab is indicated through color alone.
Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include:
In page navigation tabs, active tabs are indicated through color alone.
1.4.2 Audio Control (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.11 (Web)
- 10.2.11 (non-web document)
- 11.2.1.11 (Software)
- 11.2.2.11 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: Audio content can be controlled by the user.
Authored Content (HTML): Authored content does not contain audio.
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.15 (Web)
- 10.2.15 (non-web document)
- 11.2.1.15 (Software)
- 11.2.2.15 (Closed Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most product functionality can be operated through a keyboard interface. Exceptions include:
Adding and removing members from groups cannot be performed from the keyboard.
The drag-and-drop functions within the Event Template Editor cannot be performed from the keyboard.
In the AEM panel, most elements cannot be operated from the keyboard.
Sort functions for reports displayed in tabular format cannot be performed from the keyboard.
Some functions, such as Information, Edit, and Open, are only displayed upon mouse hover and cannot be accessed from the keyboard.
In the Reports interface, some controls used for report creation cannot be reached using the keyboard.
Authored Content (HTML): Authors can ensure that most content can be operated through a keyboard interface. Exceptions include:
The Hints control cannot be activated using the keyboard.
2.1.2 No Keyboard Trap (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.16 (Web)
- 10.2.16 (non-web document)
- 11.2.1.16 (Software)
- 11.2.2.16 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: The product allows keyboard focus to be moved away from most components using only a keyboard interface. However, keyboard focus is trapped in the “Filter View” dialog.
Authored Content (HTML): Authored content does not include keyboard traps.
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to: EN 301 549 Criteria
9.2.17 (Web) 10.2.17 (non-web document) 11.2.1.17 (Software) 11.2.2.17 (Closed Software) – Does not apply 11.6.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs)
2017 Section 508
501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not include time limits.
Authored Content (HTML): Authored content does not include time limits.
2.2.2 Pause, Stop, Hide (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.18 (Web)
- 10.2.18 (non-web document)
- 11.2.1.18 (Software)
- 11.2.2.18 (Closed Software) – Does not apply 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not include elements which move, blink, scroll, or auto-update.
Authored Content (HTML): Authored content does not include elements which move, blink, scroll, or auto-update.
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.19 (Web)
- 10.2.19 (non-web document)
- 11.2.1.19 (Software)
- 11.2.2.19 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not contain flashing content.
Authored Content (HTML): Authors can ensure that content does not flash, or flashes below the required thresholds.
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.20 (Web)
- 10.2.20 (non-web document) – Does not apply
- 11.2.1.20 (Software) – Does not apply
- 11.2.2.20 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs) 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs
Web: Does Not Support
Authored Content (HTML): Does Not Support
Web: The product does not provide a mechanism to skip repeated navigation links at the top of each page.
Authored Content (HTML): The product does not allow authors to provide a mechanism to bypass repeated information at the top of each page.
2.4.2 Page Titled (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.21 (Web)
- 10.2.21 (non-web document)
- 11.2.1.21 (Software) - Does not apply
- 11.2.2.21 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Does Not Support
Web: The titles of web pages describe their purpose.
Authored Content (HTML): Authors can provide a single title for all pages, which does not describe the topic or purpose of each page.
2.4.3 Focus Order (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.22 (Web)
- 10.2.22 (non-web document)
- 11.2.1.22 (Software)
- 11.2.2.22 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: Components receive keyboard focus in a meaningful order.
Authored Content (HTML): Authors can ensure that components receive focus in a meaningful order.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.23 (Web)
- 10.2.23 (non-web document)
- 11.2.1.23 (Software)
- 11.2.2.23 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports with Exceptions
Web: The purpose of links in the product can be determined from the link text alone or from programmatic context of the link.
Authored Content (HTML): The purpose of most links in the authored content can be determined from the link text alone or from programmatic context of the link. Exceptions include:
In Event Info, the “Know More” link does not provide its purpose.
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.27 (Web)
- 10.2.27 (non-web document)
- 11.2.1.27 (Software)
- 11.2.2.27 (Closed Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (HTML): Supports
Web: The language cannot be programmatically determined.
Authored Content (HTML): The language is programmatically determinable within the product, based on the administrator’s choice.
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.29 (Web)
- 10.2.29 (non-web document)
- 11.2.1.29 (Software)
- 11.2.2.29 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: Components do not initiate a change of context when focused.
Authored Content (HTML): Components do not initiate a change of context when focused.
3.2.2 On Input (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.30 (Web)
- 10.2.30 (non-web document)
- 11.2.1.30 (Software)
- 11.2.2.30 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Within the Content area on the Set Permissions page, checking a radio button for the “Allow Public Viewing” option causes focus to move off of the control.
Authored Content (HTML): Changes of context do not occur automatically on user input.
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.33 (Web)
- 10.2.33 (non-web document)
- 11.2.1.33 (Software)
- 11.2.2.33 (Closed Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: Where input errors are automatically detected, the field in error is identified and an error message is provided as text.
Authored Content (HTML): Where an input error is automatically detected, such as in the Event Registration page, the field in error is identified and an error message is provided as text.
3.3.2 Labels or Instructions (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.34 (Web)
- 10.2.34 (non-web document)
- 11.2.1.34 (Software)
- 11.2.2.34 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Labels or instructions are provided for most situations where user input is required. Exceptions include:
Instructions for form field constraints, such as “* indicates required field,” are not in proximity to the applicable form fields.
Authored Content (HTML): Input controls have labels or instructions that describe their purpose.
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.37 (Web)
- 10.2.37 (non-web document)
- 11.2.1.37 (Software)
- 11.2.2.37 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most markup content is implemented according to the language specification. Exceptions include:
When creating a New Event, selections on the Email Options screen have duplicate id values.
Authored Content (HTML): Markup content is implemented according to the language specification.
4.1.2 Name, Role, Value (Level A)
Also applies to: EN 301 549 Criteria
- 9.2.38 (Web)
- 10.2.38 (non-web document)
- 11.2.1.38 (Software)
- 11.2.2.38 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (HTML): Supports with Exceptions
Web: Name and role information can be programmatically determined for some types of interface components, such as most links and buttons. However, most product functions have input fields without programmatically determinable names.
Authored Content (HTML): Most authored content has programmatically determined name, role, state, property, and value information. Exceptions include:
The Hints control does not have an accessible role.
The View button does not provide its “disabled” state programmatically.
Section 2: Success Criteria, Level AA
Notes:
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
1.2.4 Captions (Live) (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.5 (Web)
- 10.2.5 (non-web document)
- 11.2.1.5 (Software)
- 11.2.2.5 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not contain live synchronized media.
Authored Content (HTML): Authored content does not contain live media.
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.6 (Web)
- 10.2.6 (non-web document)
- 11.2.1.6 (Software)
- 11.2.2.6 (Closed Software) – Does not apply 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not provide its own prerecorded video content that would require an audio description.
Authored Content (HTML): Authored content does not contain prerecorded media.
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
1.4.3 Contrast (Minimum) (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.12 (Web)
- 10.2.12 (non-web document)
- 11.2.1.12 (Software)
- 11.2.2.12 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most text meets minimum contrast requirements. Exceptions include:
In most form pages, breadcrumb text, headings, some instructions, and indicators for required fields have insufficient contrast.
Most data tables have header cells with insufficient contrast.
Authored Content (HTML): Authors can ensure that authored content meets minimum contrast requirements.
1.4.4 Resize text (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.13 (Web)
- 10.2.13 (non-web document)
- 11.2.1.13 (Software)
- 11.2.2.13 (Closed Software)
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most text can be resized up to 200 percent without loss of content or functionality. Exceptions include:
On some pages, such as the Admin Home page, all table rows below the header row are hidden.
Authored Content (HTML): Text can be resized up to 200 percent without loss of content or functionality.
1.4.5 Images of Text (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.14 (Web)
- 10.2.14 (non-web document)
- 11.2.1.14 (Software)
- 11.2.2.14 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product uses text instead of images of text, except for branding elements that are considered essential.
Authored Content (HTML): The product uses text instead of images of text, except for branding elements that are considered essential.
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
2.4.5 Multiple Ways (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.24 (Web)
- 10.2.24 (non-web document) – Does not apply
- 11.2.1.24 (Software) – Does not apply
- 11.2.2.24 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs) 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (HTML): Supports
Web: Most pages can be reached from other pages and do not require the user to follow a particular path.
Authored Content (HTML): Most pages can be reached from other pages and do not require the user to follow a particular path.
2.4.6 Headings and Labels (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.25 (Web)
- 10.2.25 (non-web document)
- 11.2.1.25 (Software)
- 11.2.2.25 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most headings and labels describe topic or purpose. Exceptions include:
On the Event Administration page, when editing group membership information, labels for the “Possible Group Members” and “Current Group Members” form fields do not indicate that they have search functionality.
Authored Content (HTML): Authors can ensure that content meets this criterion.
2.4.7 Focus Visible (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.26 (Web)
- 10.2.26 (non-web document)
- 11.2.1.26 (Software)
- 11.2.2.26 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
On the Admin Home page, a visible keyboard focus indicator is missing on page tabs that act as navigation links.
On the Edit Template page, most elements in dialogs are missing a visible keyboard focus indicator.
Authored Content (HTML): Authors can ensure that focusable elements have a visible keyboard focus indicator.
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.2 Language of Parts (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.28 (Web)
- 10.2.28 (non-web document)
- 11.2.1.28 (Software) – Does not apply
- 11.2.2.28 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports with Exceptions
Web: Content is only presented in one language at a time.
Authored Content (HTML): When the language of pages is English, content is only presented in one language at a time. However, when the language of pages is not English, some English phrases are presented without programmatic indication of the language.
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.3 Consistent Navigation (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.31 (Web)
- 10.2.31 (non-web document) – Does not apply
- 11.2.1.31 (Software) – Does not apply 11.2.2.31 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (HTML): Supports
Web: Repeated navigation links occur in a consistent relative order.
Authored Content (HTML): Navigational mechanisms are repeated in a consistent relative order.
3.2.4 Consistent Identification (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.32 (Web)
- 10.2.32 (non-web document) – Does not apply
- 11.2.1.32 (Software) – Does not apply
- 11.2.2.32 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (HTML): Supports
Web: Components with the same functionality are identified consistently across the product.
Authored Content (HTML): Components with the same functionality are identified consistently.
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.3 Error Suggestion (Level AA)
Also applies to: EN 301 549 Criteria
9.2.35 (Web) 10.2.35 (non-web document) 11.2.1.35 (Software) 11.2.2.35 (Closed Software) – Does not apply 11.6.2 (Authoring Tool) 12.1.2 (Product Docs) 12.2.4 (Support Docs)
2017 Section 508
501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: When input errors are automatically detected, suggestions are usually provided to the user. Exceptions include:
On the Change My Password page, when too many invalid attempts are submitted, the user is returned to the Login page without a suggestion for correction.
Authored Content (HTML): Where input errors are automatically detected, most error messages provide suggestions for correction. Exceptions include:
In the Event Registration page, error messages such as “Please enter valid phone number” and “Please enter valid url” do not provide suggestions for correction.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to: EN 301 549 Criteria
- 9.2.36 (Web)
- 10.2.36 (non-web document)
- 11.2.1.36 (Software)
- 11.2.2.36 (Closed Software) – Does not apply
- 11.6.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
2017 Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (HTML): Supports
Web: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing.
Authored Content (HTML): Authored content does not cause legal or financial commitments. User-controllable data is automatically checked.
2017 Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Web: Does Not Support
Authored Content (HTML): Supports with Exceptions
Web: Most functions of the product are not usable without vision. Examples include:
As noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value, most input fields are not programmatically associated with the labels that identify their purpose.
As noted in 1.1.1 Non-text Content and 1.3.1 Info and Relationships, most Flash content cannot be interpreted or operated using screen readers.
As noted in 1.3.1 Info and Relationships, programmatically identified headers are missing for most data tables.
Sort information for sortable table headers is not available to screen readers, and sorting cannot be performed from the keyboard.
Throughout the product, operations involving the selection of users, groups, files or folders do not allow these items to be selected from the keyboard.
Authored Content (HTML): Authors can create content in which most functions are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, in the Event Registration page, after the user chooses a value of a select control with custom values, the accessible name of the control conveys the chosen value instead of the purpose of the control.
As noted in 1.3.1 Info and Relationships, page content is inside of a layout table which is not marked as “presentational”.
As noted in 1.3.1 Info and Relationships, most headings are not defined programmatically.
As noted in 2.4.4 Link Purpose (In Context), in Event Info, the “Know More” link does not provide its purpose.
The Hints control does not have an accessible role and cannot be activated using the keyboard.
In page navigation tabs, active tabs are indicated through color alone.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most product functions can be used with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (Minimum), the color contrast of instructions within the template editor is insufficient.
Breadcrumb links within wizards have insufficient contrast.
The color contrast for the headers in most tables is insufficient.
As noted in 1.4.4 Resize Text, tables on the Admin home page, such as the “My Meetings” and “My Recordings” tables, do not display the rows below the table headers when resizing the page to 200 percent zoom.
Authored Content (HTML): Authors can create content in which most functions are usable with limited vision. Exceptions include:
As noted in 1.4.1 Use of Color, in page navigation tabs, active tabs are indicated through color alone.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most of the product can be used without perception of color. However, as noted in 1.4.1 Use of Color, color is used to indicate the currently active page within a set of pages throughout the product.
Authored Content (HTML): Authors can create content in which most functions are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color, in page navigation tabs, active tabs are indicated through color alone.
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most functions of the product are usable without hearing. However, when a user views an uploaded video in a Content page, the product does not display closed captions. This is a function not addressed by the technical requirements for web products and content.
Authored Content (HTML): Authors can create content which is functional for users without hearing.
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most functions of the product are usable with limited hearing. However, when a user views an uploaded video in a Content page, the product does not display closed captions. This is a function not addressed by the technical requirements for web products and content.
Authored Content (HTML): Authors can create content which is functional for users with limited hearing.
Web: Supports
Authored Content (HTML): Supports
Web: The product does not require the use of speech.
Authored Content (HTML): Authored content does not require the use of speech.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most functions of the product can be used with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, components which involve the addition and removal of users, groups, files and folders do not allow these actions to be performed from the keyboard.
Functions within the Event Template Editor cannot be performed using the keyboard. When tables contain sortable table headers, the sort functions cannot be performed from the keyboard.
As noted in 2.4.7 Focus Visible, most elements within the Event Template Editor are missing a visible indication of keyboard focus.
On the Admin Home page, the tabs are missing a visible indication of keyboard focus.
Authored Content (HTML): Authors can create content in which most functions are usable with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, the Hints control cannot be activated using the keyboard.
As noted in 2.4.1 Bypass Blocks, the product does not allow authors to provide a mechanism to bypass repeated information at the top of each page.
Web: Supports
Authored Content (HTML): Not Applicable
Web: The product is functional with limited reach and strength.
Authored Content (HTML): Authors can create content which is functional for users with limited reach and strength.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most functions of the product can be used with limited language, learning, and cognitive abilities. Exceptions include:
As noted in 3.2.2 On Input, selecting an option from the Allow Public Viewing radio buttons on the My Content page causes focus to shift.
Authored Content (HTML): Authors can create content in which most functions are usable with limited language, cognitive, and learning abilities. Exceptions include:
In the Event Registration page, error messages such as “Please enter valid phone number” and “Please enter valid url” do not provide suggestions for correction.
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes:
501 General
502 Interoperability with Assistive Technology
502.1 General. Software shall interoperate with assistive technology and shall conform to 502.
503 Applications
503.1 General. Applications shall conform to 503.
504 Authoring Tools
504.1 General. Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.
The product prompts administrators for some accessibility information, such as text alternatives for images in HTML templates. However, most authoring functions do not prompt authors to create content which conforms to WCAG 2.0 Levels A and AA. Examples include:
The product does not prompt attendees to provide accessibility information in documents or prerecorded video.
In HTML template editing, there are no prompts for most WCAG criteria that depend on the author’s input, such as link purpose, images of text, and color contrast.
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
EN 301 549 Report
Notes:
Chapter 4: 4.2 Functional Performance Statements (FPS)
Notes:
Web: Does Not Support
Authored Content (HTML): Supports with Exceptions
Web: Most functions of the product are not usable without vision. Examples include:
As noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value, most input fields are not programmatically associated with the labels that identify their purpose.
As noted in 1.1.1 Non-text Content and 1.3.1 Info and Relationships, most Flash content cannot be interpreted or operated using screen readers.
As noted in 1.3.1 Info and Relationships, programmatically identified headers are missing for most data tables.
Sort information for sortable table headers is not available to screen readers, and sorting cannot be performed from the keyboard.
Throughout the product, operations involving the selection of users, groups, files or folders do not allow these items to be selected from the keyboard.
Authored Content (HTML): Authors can create content in which most functions are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, in the Event Registration page, after the user chooses a value of a select control with custom values, the accessible name of the control conveys the chosen value instead of the purpose of the control.
As noted in 1.3.1 Info and Relationships, page content is inside of a layout table which is not marked as “presentational”.
As noted in 1.3.1 Info and Relationships, most headings are not defined programmatically.
As noted in 2.4.4 Link Purpose (In Context), in Event Info, the “Know More” link does not provide its purpose.
The Hints control does not have an accessible role and cannot be activated using the keyboard.
In page navigation tabs, active tabs are indicated through color alone.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most product functions can be used with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (Minimum), the color contrast of instructions within the template editor is insufficient.
Breadcrumb links within wizards have insufficient contrast.
The color contrast for the headers in most tables is insufficient. As noted in 1.4.4 Resize Text, tables on the Admin home page, such as the “My Meetings” and “My Recordings” tables, do not display the rows below the table headers when resizing the page to 200 percent zoom.
Authored Content (HTML): Authors can create content in which most functions are usable with limited vision. Exceptions include:
As noted in 1.4.1 Use of Color, in page navigation tabs, active tabs are indicated through color alone.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most of the product can be used without perception of color. However, as noted in 1.4.1 Use of Color, color is used to indicate the currently active page within a set of pages throughout the product.
Authored Content (HTML): Authors can create content in which most functions are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color, in page navigation tabs, active tabs are indicated through color alone.
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most functions of the product are usable with limited hearing. However, as noted in 7.1.1 Captioning Playback, when a user views an uploaded video in a Content page, the product does not display closed captions.
Authored Content (HTML): Authors can create content which is functional for users without hearing.
Web: Supports with Exceptions
Authored Content (HTML): Supports
Web: Most functions of the product are usable with limited hearing. However, as noted in 7.1.1 Captioning Playback, when a user views an uploaded video in a Content page, the product does not display closed captions.
Authored Content (HTML): Authors can create content which is functional for users with limited hearing.
Web: Supports
Authored Content (HTML): Supports
Web: The product does not require speech for use.
Authored Content (HTML): Authored content does not require the use of speech.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most of the product is functional with limited manipulation and strength. Exceptions include:
As noted in 2.1.1 Keyboard, components which involve the addition and removal of users, groups, files and folders do not allow these actions to be performed from the keyboard.
Functions within the Event Template Editor cannot be performed using the keyboard. When tables contain sortable table headers, the sort functions cannot be performed from the keyboard.
As noted in 2.4.7 Focus Visible, most elements within the Event Template Editor are missing a visible indication of keyboard focus.
On the Admin Home page, the tabs are missing a visible indication of keyboard focus.
Authored Content (HTML): Authors can create content in which most functions are usable with limited manipulation or strength. Exceptions include:
As noted in 2.1.1 Keyboard, the Hints control cannot be activated using the keyboard.
As noted in 2.4.1 Bypass Blocks, the product does not allow authors to provide a mechanism to bypass repeated information at the top of each page.
Web: Supports
Authored Content (HTML): Supports
Web: The product is functional with limited reach.
Authored Content (HTML): Authors can create content which is functional for users with limited reach.
Web: Supports
Authored Content (HTML): Supports
Web: The product does not contain flashing content.
Authored Content (HTML): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.
Web: Supports with Exceptions
Authored Content (HTML): Supports with Exceptions
Web: Most functions of the product can be used with limited language, learning, and cognitive abilities. Exceptions include:
As noted in 3.2.2 On Input, selecting an option from the Allow Public Viewing radio buttons on the My Content page causes focus to shift.
Authored Content (HTML): Authors can create content in which most functions are usable with limited language, cognitive, and learning abilities. Exceptions include:
In the Event Registration page, error messages such as “Please enter valid phone number” and “Please enter valid url” do not provide suggestions for correction.
Web: Supports
Authored Content (HTML): Supports
Web: The product does not contain accessibility components that compromise the privacy of the user.
Authored Content (HTML): Authored content does not contain accessibility components that compromise the privacy of the user.
Chapter 5: Generic Requirements
Notes:
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: See WCAG 2.0 section.
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not applicable to this product.
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)