Adobe Accessibility Conformance Report
VPAT® Version 2.0 – October 2017
Product Information
Name of Product/Version: Adobe Captivate 2017
Product Description: Adobe Captivate is an authoring tool used to create e-learning content in Small Web and HTML5 formats.
Date: November 2017
Contact information: access@adobe.com
Notes: The information contained in this report applies to the product itself. Information about product help and support documentation related to 602.3 (Support Docs) for Section 508 as published in 2017 is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe Captivate involved extensive use of leading assistive technologies 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:
Standard/Guideline |
Included In Report |
---|---|
Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ |
Level A - Yes Level AA - Yes Level AAA - No |
Section 508 as published in 2017, at http://www.Section508.gov |
Yes |
EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at http://mandate376.standards.eu/standard |
Yes |
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
Sections 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.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most images are used within input controls, and are accompanied with on-screen text, fully describing their functionality. Additionally, many stand-alone icons, contain textual descriptions. However, a rating of Supports with Exceptions has been given as some images do not contain fully descriptive textual alternatives, including the following: The Slide Layout Button, Tab Order and Accessibility Menu items do not contain appropriate textual alternatives for icons that are used as the sole means of identifying a control. Authored Content (HTML): Images that have had defined textual alternatives will expose these accurately to users. |
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product includes features allowing content creators to add audio tracks that fully describe any visually displayed content. Authored Content (HTML): When video-only content is provided, any text displayed on the page will be exposed through programmatic text to users. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: The product includes features allowing content creators to add closed captioning to synchronized media that will display when previewing content. Multiple font and color choices are provided within the caption settings. However, when previewing individual slides, there is no method to view included closed captions. Authored Content (HTML): Authors are capable of providing captions for all prerecorded audio content in synchronized media. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product includes features allowing content creators to add audio tracks that fully describe any visually displayed content. Authored Content (HTML): Authors can include audio description for prerecorded video in exported content. |
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions |
Software: Most relationships are expressed programmatically, rather than implicitly. However, some controls such as the Shadow radio buttons or the new project tabs are only grouped visually. Nested checkboxes, found within Preferences do not expose their grouping programmatically. Authored Content (HTML): Most relationships are available programmatically, however within slides heading contents are not programmatically identified as headings. |
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most content is presented within a meaningful sequence. However, some areas, such as the Insert Questions windows, do not present content in an order that preserves the visually supplied meaning. Authored Content (HTML): Reading order is defined within slide templates, which provides an informative sequence of text. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most content does not rely on sensory characteristics to imply meaning. However, the Rotate and RotateTo effects rely exclusively on visual cues to imply if content will be rotated clockwise or counterclockwise. Authored Content (HTML): Authors can create content that does not rely solely on shape, size, visual location, orientation, or sound to imply meaning. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The user interface does not use color as the only means of conveying information. Authored Content (HTML): Authors can create presentations where color is not used as the sole means of conveying information. |
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include audio that plays automatically for more than 3 seconds. Authored Content (HTML): Exported content will automatically play when a page is loaded. Controls to play and pause content, as well as mute content, are provided. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Software: Some controls, such as the menu functionality and tools that have keyboard shortcuts, are accessible solely through the keyboard. However, many functions, including moving between panes, hiding or locking sections of slides in the Timeline window, and interacting with the Filmstrip’s context menu, cannot be accessed through the keyboard alone. Authored Content (HTML): Interactive content, including the buttons controlling playback, form fields, and interactive quiz content can be activated solely through the use of the keyboard. |
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Where the software allows users to place focus on a component, keyboard focus can be moved away from that component. Authored Content (HTML): No keyboard traps are present within the HTML output. |
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include time-based limits. Authored Content (HTML): Authors can choose to create content that does not present time limits to users. A feature is provided to supply time limits, in instances where they are essential to the activity. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Authors can make content move, blink, or scroll through animation; however, these are not required to be utilized. Authored Content (HTML): Authors are not required to include any scrolling, blinking, or other transitions. If implemented, Authors can choose to implement these transitions in a way that conforms to this requirement. |
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): No repeated blocks of content are present within the exported HTML content. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Does Not Support |
Software: The main application window contains a programmatic title, and individual modal dialogs spawned by the software, such as Preferences, also contain explicit titles. Authored Content (HTML): A blank title is provided for all slides in the HTML export. |
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions |
Software: Most focusable components receive focus in a meaningful order. However, some areas, such as the insert quiz questions modal dialog, do not have a meaningful focus order. Authored Content (HTML): The navigation sequence of items can be adjusted by authors within the software, ensuring the focus order or authored content is meaningful. However, the playback controls will always appear within the navigation sequence before exported content, and cannot have their focus order adjusted. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The purpose of link text can be determined in context. Authored Content (HTML): Authors can create links, the purpose of which can be determined in context. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports with Exceptions |
Software: The language is programmatically determinable within the product. The language of the product is set based on the version installed by the user. Authored Content (HTML): The language of the software determines the language that HTML context will be exported with. If authors are creating pages in different languages, there is no way within the software to declare a different page language. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: User interface components do not initiate a change of context when a control or input field receives focus. Authored Content (HTML): Authors can design forms that do not initiate a change of context when components receive focus. |
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most user interface components do not cause changes of context when settings are changed, unless users are alerted. However, some checkboxes within Preferences dialogs will cause changes of context without authors being alerted. Authored Content (HTML): Authors can design content so that changing a user interface component’s setting does not automatically cause a change of context. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: The product helps prevent user errors by disabling controls which are not relevant. However, some controls such as an interface element’s Opacity, or Width, contain predefined maximum and minimum values. If an author enters a value outside of these ranges, the form field automatically adjusts to the last valid value without alerting authors. Authored Content (HTML): Input errors are detected when users submit quiz questions. Authors can ensure feedback is automatically provided regarding if a question was answered correctly or not. |
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions. Authored Content (HTML): Supports |
Software: The majority of input controls contain labels or instructions. However, some controls, such as the effects type dropdown, contains no label or instructions. Authored Content (HTML): Labels are provided for all submitted questions, and icons and tooltips are provided for all player interface buttons. |
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: A user agent is not used to parse a markup language. Authored Content (HTML): Required elements include start and end tags, ID attributes are not duplicated, and all elements are nested according to specification. |
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions |
Software: Many elements contain programmatically defined names and roles. States and values are likewise programmatically set. However, some elements such has the Size spin box, and Image combo box within the Style Manager window do not contain programmatic names. Additionally, other elements, including icons in the initial window used to select a presentation type do not contain programmatically defined roles. Authored Content (HTML): Most controls within the HTML export contain appropriate roles and values. However, some elements, such as the submit buttons do not contain appropriate roles. Additionally, the state of buttons within the player’s controls are not provided to users. |
Section 2: Success Criteria, Level AA
Notes:
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not provide live media that requires captions. Authored Content (HTML): No Live content is provided within exported content. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product includes features allowing content creators to add audio tracks that fully describe any visually displayed content. Authored Content (HTML): Authors can include audio description for prerecorded video content. |
|
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most text meets minimum contrast requirements. However, page tabs, such as the ‘Closed Captioning’ tab within the Slide Audio dialog, and Help links within modal dialogs have insufficient color contrast. Authored Content (HTML): The default player control templates contain sufficient color contrast. Additionally, authors can create slide content that contains sufficient luminosity color contrast ratios. |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Does Not Support |
Software: Only some content will be resized when native Windows magnification features are provided. The native menu controls and scroll bars will expand with the increase in text size, but many other components, including the Library and Properties panes. The product supports macOS Zoom. Authored Content (HTML): Built-in browser zoom functionality will not increase text size within exported HTML content. |
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Does Not Support |
Software: The product does not contain images of text. Authored Content (HTML): All observed text on is displayed as images. within the output were images of text. Equivalent programmatic text is available off-screen, but will not be displayed unless CSS is disabled. |
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): Exported HTML content is contained within one page. Questions added as part of a quiz are part of a series of steps. |
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Observed headings and labels were informative and descriptive. Authored Content (HTML): Exported HTML content is contained within one page. Content within quizzes are steps within a process. |
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Does Not Support |
Software: The product provides a highly visual blue outline for most buttons, combo boxes, and text inputs. However, some controls such as those in the Advanced Action and Variables windows, do not have a highly visual indication of focus. Authored Content (HTML): No visual displays of keyboard focus were encountered within exported content. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Does Not Support |
Software: The language is set based on the version installed by the user. If parts of the page within authored content are in another language, this cannot be programmatically set. Authored Content (HTML): The language of the software determines the language of exported HTML content. Authors are cannot specify parts of content to be programmatically identified in a different language. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): No repeated navigational mechanisms are present within the exported HTML content. |
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): All controls within the HTML player content are consistently identified. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Authored Content (HTML): Authors are capable of providing customized messages when users submit incorrect answers to questions |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not process legal commitments or financial transactions. Changes to user-controllable data can be reversed. Authored Content (HTML): The exported HTML content does not process legal commitments or financial transactions. |
2017 Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
302.1 Without Vision |
Software: Does Not Support Authored Content (HTML): Supports with Exceptions |
Software: The product does not support operation without user vision. As noted in 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value, users without vision will encounter issues interacting with content. Authored Content (HTML): As noted within in 1.1.1 Non-text Content, 1.2.5 Audio Description (Prerecorded), 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value, most content can be designed to be accessible to users without vision. However, some exceptions are noted in the Success Criteria. |
302.2 With Limited Vision |
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions |
Software: The product supports the use of screen magnification software. However, as noted in 502.2.2 No Disruption of Accessibility Features, native OS high contrast modes are not supported on the Windows OS. Authored Content (HTML): Most exported HTML content will be accessible to users with low vision. This content supports the use of screen magnification software. However, as noted in 1.4.4 Resize text, native browser zoom features are not fully supported. |
302.3 Without Perception of Color |
Software: Supports Authored Content (HTML): Supports |
Software: As noted in 1.4.1 Use of Color, the product does not rely on perception of color to use the software. Authored Content (HTML): Authors can design content exported from the product in ways that do not rely on the perception of color to use. |
302.4 Without Hearing |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Closed captioning can be added for all user generated audio content. However, users without hearing will be unable to view captions when previewing individual slides. Authored Content (HTML): Authors are able to supply captions for all audio content, so that this content is usable by people without hearing. |
302.5 With Limited Hearing |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Closed captioning can be added for all user generated audio content. However, users with limited hearing will be unable to view captions when previewing individual slides. Authored Content (HTML): Authors are able to supply captions for all audio content, so that this content is usable by people with limited hearing. |
302.6 Without Speech |
Software: Supports Authored Content (HTML): Supports |
Software: Speech is not required to use the product. Authored Content (HTML): Exported HTML content does not include any features requiring user speech. |
302.7 With Limited Manipulation |
Software: Does Not Support Authored Content (HTML): Supports with Exceptions |
Software: Users with limited manipulation who use speech recognition software will have difficulty navigating to controls due to the exceptions noted in 2.1.1 Keyboard and 4.1.2 Name, Role, Value. Authored Content (HTML): Users with limited manipulation will be able to access most content through the use of speech recognition software. However, as noted in 2.4.3 Focus Order and 4.1.2 Name, Role, Value, some exceptions exist that will prevent users from calling controls by their name, or tabbing through the interface. |
302.8 With Limited Reach and Strength |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Strength is not required to operate the product’s components. However, a rating of Supports with Exceptions has been given as users with limited reach who utilize keyboards may find the application difficult to use, as noted previously in 2.1.1 Keyboard. Authored Content (HTML): Strength is not required to operate the exported components. Users with limited reach who utilize keyboards will be able to access the content solely using the keyboard. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports Authored Content (HTML): Supports |
Software: The user interface provides options to use icons, text, or a combination of both for controls. The user interface also provides multiple options for configuring the layout or controls and panes. In addition, visible labels are used to communicate the purpose of input fields, and standard system dialogs are used consistently to communicate error messages. Authored Content (HTML): Authors can design content in such a way that questions include features to assist users with limited language, cognitive, and learning abilities. |
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes:
501 General
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.0 section |
See information in the WCAG section |
502 Interoperability with Assistive Technology
502.1 General. Software shall interoperate with assistive technology and shall conform to 502.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
502.2 Documented Accessibility Features |
See 502.2.1-502.2.2 |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is not platform software. |
502.2.2 No Disruption of Accessibility Features |
Supports with Exceptions |
The product does not disable or disrupt some activated accessibility features of the platform such as Sticky keys and Toggle Keys However, the application does not follow High Contrast settings within the Windows OS. |
502.3 Accessibility Services |
See 502.3.1-502.3.14 |
|
502.3.1 Object Information |
Supports with Exceptions |
As stated in 1.3.1 Info and Relationships, 2.4.4 Link Purpose, and 4.1.2 Name, Role, Value, most objects contain appropriate programmatic information. However, some exceptions are noted within the above Success Criteria. |
502.3.2 Modification of Object Information |
Supports |
Programmatic states of controls, such as radio buttons and checkboxes, can be programmatically set and updated by users, including those using assistive technologies. |
502.3.3 Row, Column, and Headers |
Not Applicable |
The product does not include tabular content. |
502.3.4 Values |
Supports with Exceptions |
Values for fields, including text inputs for names, number values for sizing, and combo boxes for can all be determined. However, some controls, such as the width and height fields, have maximum and minimum values that are not programmatically exposed to users. |
502.3.5 Modification of Values |
Supports |
The values of controls, including text input and number fields, radio buttons and checkboxes, can be modified programmatically. |
502.3.6 Label Relationships |
Supports with Exceptions |
Most Controls as noted in 4.1.2 Name, Role, Value, are appropriately labelled. However, in some area, such as the Object Styles manager and the preferences dialog, visual labels are not programmatically connected to controls. |
502.3.7 Hierarchical Relationships |
Supports with Exceptions |
Most hierarchical relationships are programmatically identifiable. However, in areas such as the Preferences dialog, hierarchical relationships that are only enabled conditionally are not always explicitly identified. |
502.3.8 Text |
Supports |
The product exposes text content to assistive technologies. |
502.3.9 Modification of Text |
Supports |
The product allows assistive technologies to modify text content. |
502.3.10 List of Actions |
Supports with Exceptions |
Most controls users with appropriate roles, and thus a list of actions. However, those controls without roles, noted in 4.1.2 Name, Role, Value, will not provide a list of actions. |
502.3.11 Actions on Objects |
Supports with Exceptions |
Most controls can be actionable. However, controls listed in 2.1.1 Keyboard as not providing keyboard focus to users will not be able to be accessed by keyboard-only, screen reader, and other AT users. |
502.3.12 Focus Cursor |
Supports with Exceptions |
The product exposes information to track text insertion point, and selection attributes of user interface components for all observed Controls. As noted in 2.4.7 Focus Visible, most components expose information necessary to track focus. |
502.3.13 Modification of Focus Cursor |
Supports with Exceptions |
Using the mouse, it is possible to modify focus programmatically to all controls. However, as noted in 2.1.1 Keyboard, focus cannot be placed on all controls using the keyboard interface alone. |
502.3.14 Event Notification |
Supports with Exceptions |
All observed changes in a focused component’s state and value were exposed to users, including through the use of assistive technology. However, changes in the state of non-focused components in the preferences pane, and the display of the preferences pane when activating slides in the filmstrip are not announced to assistive technology. |
502.4 Platform Accessibility Features |
Not Applicable |
The product is not platform software. |
503 Applications
503.1 General. Applications shall conform to 503.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
503.2 User Preferences |
Supports with Exceptions |
The MacOS version supports a user’s platforms preferences. The Windows version of the software largely supports platform preferences. However, when color contrast, or increased font sizes are chosen, only the menu controls will respect the platform settings. |
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide alternative user interfaces. |
503.4 User Controls for Captions and Audio Description |
See 503.4.1-503.4.2 |
|
503.4.1 Caption Controls |
Supports |
When video content is previewed within the product, the software supports the playback of closed captions. |
503.4.2 Audio Description Controls |
Supports |
The product does not require video content to be present. Where it does, sufficient description can be embedded within an audio track’s content. |
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.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section |
See information in the WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Supports |
Closed captions are provided, if present, when content is exported. |
504.2.2 PDF Export |
Not Applicable |
The product does not export PDF files. |
504.3 Prompts |
Does Not Support |
The product provides a feature to check that content is supported within HTML5 before exporting, but contains no prompts to ensure content will conform to WCAG A and AA. |
504.4 Templates |
Supports with Exceptions |
Most templates will assist authors in creating content, such as questions, with appropriate labels and roles. However, multiple templates provided do not contain sufficient color contrast. |
Chapter 6: Support Documentation and Services
Notes: Conformance information for Support Documentation and Services is available in the Adobe Accessibility Conformance Report for HelpX documentation.
EN 301 549 Report
Notes:
Chapter 4: 4.2 Functional Performance Statements (FPS)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Software: Does Not Support Authored Content (HTML): Supports with Exceptions |
Software: The product does not support operation by users without vision. As noted in 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value, users without vision will encounter issues interacting with content. Authored Content (HTML): As noted within in 1.1.1 Non-text Content, 1.2.5 Audio Description (Prerecorded), 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value, most content can be designed to be accessible to users without vision. However, some exceptions are noted in the Success Criteria. |
4.2.2 Usage with limited vision |
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions |
Software: The product supports the use of screen magnification software. However, as noted in 502.2.2 No Disruption of Accessibility Features , native OS high contrast modes are not supported on the Windows OS. Authored Content (HTML): Most exported HTML content will be accessible to users with low vision. This content supports the use of screen magnification software. However, as noted in 1.4.4 Resize text, native browser zoom features are not fully supported. |
4.2.3 Usage without perception of colour |
Software: Supports Authored Content (HTML): Supports |
Software: As noted in 1.4.1 Use of Color, the product does not rely on perception of color to use the software. Authored Content (HTML): Authors can design exported content in ways that do not rely on the perception of color to use. |
4.2.4 Usage without hearing |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Closed captioning can be added for all user generated audio content. However, users without hearing will be unable to view captions when previewing individual slides. Authored Content (HTML): Authors are able to supply captions for all audio content, so that this content is usable by people without hearing. |
4.2.5 Usage with limited hearing |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Closed captioning can be added for all user generated audio content. However, users with limited hearing will be unable to view captions when previewing individual slides. Authored Content (HTML): Authors are able to supply captions for all audio content, so that this content is usable by people with limited hearing. |
4.2.6 Usage without vocal capability |
Software: Supports Authored Content (HTML): Supports |
Software: Speech is not required to use the product. Authored Content (HTML): Speech is not required to use any features of the exported HTML content. |
4.2.7 Usage with limited manipulation or strength |
Software: Does Not Support Authored Content (HTML): Supports with Exceptions |
Software: Users with limited manipulation who use speech recognition software will have difficulty navigating to controls due to the exceptions noted in 2.1.1 Keyboard and 4.1.2 Name, Role, Value. Strength is not required to operate any of the exported components. Authored Content (HTML): Users with limited manipulation will be able to access most content through the use of speech recognition software. However, as noted in 2.4.3 Focus Order and 4.1.2 Name, Role, Value, some exceptions exist that will prevent users from calling controls by their name, or tabbing through the interface. Strength is not required to operate any of the products components. |
4.2.8 Usage with limited reach triggers |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: However, a rating of Supports with Exceptions has been given as users with limited reach who utilize keyboards may find the application difficult to use, as noted previously in 2.1.1 Keyboard. Authored Content (HTML): Users with limited reach who utilize keyboards will be able to access the content solely through the use of the keyboard. |
4.2.9 Minimize photosensitive seizure |
Software: Supports Authored Content (HTML): Supports |
Software: By default the product does not blink or flash in ways that would potentially trigger photosensitive seizures. Authored Content (HTML): Authors can design blinking or flashing content which does not trigger photosensitive seizures. |
4.2.10 Usage with limited cognition |
Software: Supports Authored Content (HTML): Supports |
Software: The user interface provides options to use icons, text, or a combination of both for controls. The user interface also provides multiple options for configuring the layout or controls and panes. In addition, visible labels are used to communicate the purpose of input fields, and standard system dialogs are used consistently to communicate error messages. Authored Content (HTML): Authors can design content such that questions include features to assist users with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not ask for legal, financial, or personal data. Authored Content (HTML): Exported HTML content relies upon platform software to ensure that privacy is maintained when using content. |
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed Functionality |
Not Applicable |
5.1.2.2-5.1.6.2 are not applicable for this product. |
5.2 Activation of accessibility features |
Not Applicable |
The product does not contain documented accessibility features, and relies upon |
5.3 Biometrics |
Not Applicable |
The product does not rely on biological characteristics. |
5.4 Preservation of accessibility information during conversion |
Supports |
Closed captioning that is imported to the product can be preserved during conversion. |
5.5.1 Means of operation |
Not Applicable |
The product does not have operable parts. |
5.5.2 Operable parts discernibility |
Not Applicable |
The product does not have operable parts. |
5.6.1 Tactile or auditory status |
Not Applicable |
The product does not have locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not have locking or toggle controls. |
5.7 Key repeat |
Not Applicable |
The product relies on platform software to supply key repeat functionality. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not, by itself, supply a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product supports platform sticky keys features that allows users who cannot press keys that need to be pressed simultaneously to activate the same features when keys are pressed individually. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
7.1.1 Captioning playback |
Supports with Exceptions |
The product includes features allowing content creators to add closed captioning to synchronized media that will display when previewing presentations. Multiple font and color choices are provided within the caption settings. However, when previewing individual slides, there is no method to view included closed captions. |
7.1.2 Captioning synchronization |
Supports |
Captions can be synchronized between audio and the corresponding captions. |
7.1.3 Preservation of captioning |
Supports |
When converting formats, the product can preserve and re-export caption content. |
7.2.1 Audio description playback |
Supports |
Audio tracks are provided by authors. Authors are able to supply audio content that contains audio description features. |
7.2.2 Audio description synchronization |
Supports |
Authors are capable of providing audio description that is synchronized with the audio/visual content displayed. |
7.2.3 Preservation of audio description |
Supports |
When converting formats, author-supplied audio, including audio descriptions is preserved. |
7.3 User controls for captions and audio description |
Supports with Exceptions |
Authors are able to control audio descriptions supplied in the same manner that they control playback of audio content. However, as noted in 7.1.1 Captioning playback, closed captioning will not always display at with the same level of interaction as audio content when previewing slides. |
Chapter 8: Hardware
Notes: Not applicable to this product.
Chapter 9: Web
Notes: See WCAG 2.0 section.
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.0 section. |
See information in the WCAG section |
11.2.2 Software success criteria (closed functionality) |
Not Applicable |
|
11.3.2.3 Use of accessibility services |
Supports |
The product supports the UI Automation accessibility API on Windows 7, and the macOS Accessibility Protocol (AX API), allowing use of accessibility services which are part of these respective platforms. |
11.3.2.4 Assistive technology |
Not Applicable |
The product is not assistive technology. |
11.3.2.5 Object information |
Supports with Exceptions |
As stated previously in 1.3.1 Info and Relationships, 2.4.4 Link Purpose, and 4.1.2 Name, Role, Value, most objects contain appropriate programmatic information. However, some exceptions are noted within the above Success Criteria. |
11.3.2.6 Row, column, and headers |
Not Applicable |
The product does not include tabular content. |
11.3.2.7 Values |
Supports with Exceptions |
Values for fields, including text inputs for names, number values for sizing, and combo boxes for can all be determined. However, some controls, such as the width and height fields, have maximum and minimum values that are not programmatically exposed to users. |
11.3.2.8 Label relationships |
Supports with Exceptions |
Most Controls as noted in 4.1.2 Name, Role, Value, are appropriately labelled. However, in some area, such as the Object Styles manager and the preferences dialog, visual labels are not programmatically connected to controls. |
11.3.2.9 Parent-child relationships |
Supports with Exceptions |
Most parent-child relationships are programmatically identifiable. However, in areas such as the Preferences dialog, hierarchical relationships that are only enabled conditionally are not always explicitly identified. |
11.3.2.10 Text |
Supports |
The product exposes text content to assistive technologies. |
11.3.2.11 List of available actions |
Supports with Exceptions |
Most controls provide users with appropriate roles, and thus a list of actions. However, those controls without roles, noted in 4.1.2 Name, Role, Value, will not provide a list of actions. |
11.3.2.12 Execution of available actions |
Supports with Exceptions |
Most controls can be actionable. However, controls listed in 2.1.1 Keyboard as not providing keyboard focus to users will not be able to be accessed by keyboard-only, screen reader, and other AT users. |
11.3.2.13 Tracking of focus and selection attributes |
Supports with Exceptions |
The product exposes information to track text insertion point, and selection attributes of user interface components for all observed Controls. As noted in 2.4.7 Focus Visible, most components expose information necessary to track focus. |
11.3.2.14 Modification of focus and selection attributes |
Supports with Exceptions |
Using the mouse, it is possible to modify focus programmatically to all controls. However, as noted in 2.1.1 Keyboard, focus cannot be placed on all controls using the keyboard interface alone. |
11.3.2.15 Change notification |
Supports with Exceptions |
All observed changes in a focused component’s state and value were exposed to users, including through the use of assistive technology. However, changes in the state of non-focused components in the preferences pane, and the display of the preferences pane when activating slides in the filmstrip are not announced to assistive technology. |
11.3.2.16 Modifications of states and properties |
Supports |
Programmatic states of controls, such as radio buttons and checkboxes, can be programmatically set and updated by users, including those using assistive technologies. |
11.3.2.17 Modifications of values and text |
Supports |
The values of controls, including text input and number fields, radio buttons, and checkboxes, as well as text can be modified programmatically. |
11.4.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
11.4.2 No disruption of accessibility features |
Supports with Exceptions |
The product does not disable or disrupt some activated accessibility features of the platform such as Sticky keys and Toggle keys However, the application does not follow High Contrast settings within the Windows OS. |
11.5 User preferences |
Supports with Exceptions |
The MacOS version of the software will support a user’s platforms preferences. The Windows version of the software largely supports platform preferences. However, when color contrast, or increased font sizes are chosen, only the menu controls will respect the platform settings. |
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section. |
See information in the WCAG section |
11.6.3 Preservation of accessibility information in transformations |
Supports |
The product provides closed captioning, if present, when content is exported. |
11.6.4 Repair assistance |
Does Not Support |
The product provides a feature to check that content is supported within HTML5 before exporting, but contains no prompts to ensure content will conform to WCAG A and AA. |
11.6.5 Templates |
Supports with Exceptions |
Most template will assist authors in creating content, such as questions, with appropriate labels and roles. However, multiple templates provided do not contain sufficient color contrast. |
Chapter 12: Documentation and Support Services
Notes: Conformance information for Documentation and Support Services is available in the Adobe Accessibility Conformance Report for HelpX documentation.
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)