Adobe Accessibility Conformance Report
VPAT® Version 2.0 – November 2017
Product Information
Name of Product/Version: Adobe Behance
Product Description: Adobe Behance is an online platform to showcase and discover creative work.
Date: May 2018
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 Behance 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.
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:
2017 Section 508
|
Web: Supports with Exceptions Authored Content (HTML): Does Not Support |
Web: Exceptions Include:
Authored Content (HTML): Authors are not able to define textual alternatives for content they upload. |
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
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not provide prerecorded audio-only or video-only content. Authored Content (HTML): Authors can provide a media alternative for uploaded audio-only and video-only content. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports with Exceptions Authored Content (HTML): Supports with Exceptions |
Web: The product provides auto-generated captions for most audio information in previously aired Adobe Live content. Exceptions include:
Authored Content (HTML): Authors can provide captioned audio in third-party hosted videos. However, authors cannot provide captions for audio in uploaded video content. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The product does not provide audio description for previously aired Adobe Live content. Authored Content (HTML): Authors can provide a media alternative for uploaded video 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
|
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: Visual proximity is used within the project editor to convey connection between content and their respective edit buttons. Visually displayed tabs, such as the product’s Gallery tabs, use visual presentation alone to convey meaning. Authored Content (HTML): Exceptions include:
|
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product presents content in a meaningful sequence. Authored Content (HTML): The product allows authors the ability to present content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
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.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Exceptions include:
Authored Content (HTML): Authored Content does not contain audio that plays automatically. |
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
|
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: The product relies exclusively on clicking and dragging for major functionality, including when rearranging content within a project, or adjusting how to display a profile’s social media accounts. Some controls, such as those to edit previously added project content, will only display on mouse hover. Authored Content (HTML): Exceptions include:
|
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not include keyboard traps. Authored Content (HTML): Authored Content does not include keyboard traps. |
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
|
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
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports with Exceptions |
Web: The product does not include elements which move, blink, scroll, or auto-update. Authored Content (HTML): Exceptions include:
|
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
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content meets this criterion. |
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
|
Web: Supports Authored Content (HTML): Supports |
Web: The content provides a mechanism to bypass repeated blocks of content. Authored Content (HTML): No repeated blocks of content are present within the content. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Authored Content (HTML): Authors can ensure that content meets this criterion. Page titles for Authored Content are automatically generated from project titles. |
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Components receive focus in a meaningful order. Authored Content (HTML): Components receive focus in a meaningful order. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Authored Content (HTML): Authors can ensure that content meets this criterion. |
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
|
Web: Supports Authored Content (HTML): Supports |
Web: The product identifies the language of the page programmatically. Authored Content (HTML): Authored Content identifies the language of the page programmatically. |
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
|
Web: Supports Authored Content (HTML): Supports |
|
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Changes of context that occur automatically on user input are clearly indicated to the user before invoking them. Authored Content (HTML): Changes of context that occur automatically on user input are clearly indicated to the user before invoking them. |
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
|
Web: Does Not Support Authored Content (HTML): Supports |
Authored Content (HTML): Authored Content does not detect input errors that will be displayed to users. |
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Labels are provided for input fields. Authored Content (HTML): Authored Content does not provide controls for user input. |
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
|
Web: Supports Authored Content (HTML): Supports |
Authored Content: Authors can ensure that content meets this criterion. |
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: When creating a project, most functions require the use of controls which lack name or role information. Authored Content: Authors can ensure that content meets this criterion. |
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
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The product does not provide captions for Adobe Live content. Authored Content (HTML): The product does not include the ability to present live media. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The product does not provide audio description for previously aired Adobe Live content. 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.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Most text meets minimum contrast requirements. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
|
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria .
2017 Section 508
|
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): Authors can ensure that content meets this criterion. |
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
|
Web: Supports Authored Content (HTML): Supports |
|
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Headings and labels are descriptive. 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
2017 Section 508
|
Web: Does Not Support Authored Content (HTML): Does Not Support |
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
|
Web: Supports Authored Content (HTML): Does Not Support |
Web: Content is only presented in one language at a time. Authored Content (HTML): The product does not allow users to select the language for individual phrases within Authored Content. |
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
|
Web: Supports Authored Content (HTML): Supports |
|
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
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
|
Web: Supports Authored Content (HTML): Supports |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not process legal commitments or financial transactions. Changes to user-controllable data can be confirmed before finalizing and are reversible. Authored Content (HTML): Authored Content does not contain legal or financial data and does not modify user-controllable data. |
2017 Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
302.1 Without Vision |
Web: Does Not Support Authored Content (HTML): Does Not Support |
Web: Most content in the product is not functional for users without vision, owing primarily to insufficient element roles, text alternatives, and keyboard behaviors. As previously noted in 1.3.1 Info and Relationships and 2.1.1 Keyboard, the product relies on visual cues and mouse driven behavior for interacting with and creating content. Authored Content (HTML): Most authored HTML content is not functional for users without vision. As noted in 1.1.1 Non-text Content, cannot receive alternative text. Additionally, as noted in in 1.3.1 Info and Relationships, visually displayed headings are not programmatically defined. |
302.2 With Limited Vision |
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Most content in the product is functional for users with limited vision. As noted in 1.4.4 Resize text and 1.4.5 Images of Text, the product allows resizing of text, and does not include images of text. If users rely on the keyboard to navigate, some issues will be encountered, as noted in 2.1.1 Keyboard. Authored Content (HTML): Authors can ensure that users with limited vision can interact with their content. |
302.3 Without Perception of Color |
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Most content in the product will be functional for users without perception of color. As noted in 1.4.1 Use of Color, some exceptions, largely related to product navigation, exist. Authored Content (HTML): Authors can ensure that users without perception of color can interact with their content. |
302.4 Without Hearing |
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: The visual components of the product are functional for users without hearing, and as noted in 1.2.2 Captions (Prerecorded) the product provides auto-generated captions for most audio information in prerecorded videos. However, some media content is not understandable, and as noted in 1.2.4 Captions (Live) the product does not provide captions for live videos. Authored Content (HTML): The visual components of authored content are functional for users without hearing; however, as noted in 1.2.2 Captions (Prerecorded), authors cannot provide captions for some audio content. |
302.5 With Limited Hearing |
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: The visual components of the product are functional for users with limited hearing, and as noted in 1.2.2 Captions (Prerecorded) the product provides auto-generated captions for most audio information in prerecorded videos. However, some media content is not understandable, and as noted in 1.2.4 Captions (Live) the product does not provide captions for live videos. Authored Content (HTML): The visual components of authored content are functional for users with limited hearing; however, as noted in 1.2.2 Captions (Prerecorded), authors cannot provide captions for some audio content. |
302.6 Without Speech |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require user speech. Authored Content (HTML): Authored Content does not require user speech. |
302.7 With Limited Manipulation |
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: Most functions of the product are not functional for users with limited manipulation who rely on keyboard access. As noted in 2.1.1 Keyboard, controls either do not receive keyboard focus or, as noted in 2.4.7 Focus Visible, do not display a visual indication of keyboard focus. Authored Content (HTML): Users with limited manipulation who rely on keyboard access will be able to navigate through authored content; however, as noted in 2.4.7 Focus Visible, will not receive a visual indication of keyboard focus. |
302.8 With Limited Reach and Strength |
Web: Supports Authored Content (HTML): Supports |
Web: The product is functional with limited reach and limited strength. Authored Content (HTML): Using the product, authors can create HTML which is functional with limited reach and limited strength. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: Supports Authored Content (HTML): Supports |
Web: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product provides icons and supplements these with text, as well as providing the ability to change the interface language to 19 languages. Authored Content (HTML): Authors can ensure that users with limited language, cognitive, and learning abilities can interact with their content. |
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 |
The product does not disrupt platform accessibility features. |
502.3 Accessibility Services |
See 502.3.1-502.3.14 |
|
502.3.1 Object Information |
Does Not Support |
Most core functions of the product contain functional components which lack role, state, or accessible name information. All of the “Add Media” components when editing a project do not convey a programmatic role. Most icons used in place of text do not contain programmatic names. |
502.3.2 Modification of Object Information |
Does Not Support |
Most states and properties of objects, particularly within the project editor, cannot be set programmatically. Components to align, bold, italicize, or underline text contain no programmatic state. |
502.3.3 Row, Column, and Headers |
Not Applicable |
The product does not contain data tables. |
502.3.4 Values |
Supports |
The product allows users to programmatically determine values. |
502.3.5 Modification of Values |
Supports |
When the value of an input control in the product can be modified by users in general, the value can be modified by assistive technology. |
502.3.6 Label Relationships |
Does Not Support |
The product visually provides labels for components; however, the relationship between components and labels, such as those in the Preferences page, is not programmatically determinable. |
502.3.7 Hierarchical Relationships |
Supports with Exceptions |
The product relies on nested lists and programmatic headings to indicate hierarchical relationships between elements; however, some exceptions, such as the Project Editor’s in-line “Insert Media” controls, exist. |
502.3.8 Text |
Supports |
Text content, text attributes, and text boundaries are programmatically determinable. |
502.3.9 Modification of Text |
Supports |
The text content of text input controls in the product can be modified by assistive technology. |
502.3.10 List of Actions |
Does Not Support |
Most components do not contain a programmatic role, and therefore do not convey a list of actions that can be executed. |
502.3.11 Actions on Objects |
Supports |
Components allow assistive technologies to programmatically execute actions upon them. |
502.3.12 Focus Cursor |
Does Not Support |
The product does not provide a means to visually track the focus cursor. |
502.3.13 Modification of Focus Cursor |
Supports |
When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically. |
502.3.14 Event Notification |
Does Not Support |
When components in the product change their states and values, such as when filtering options are selected, notifications are not provided to assistive technologies. |
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 |
Not Applicable |
The product is a web application, which is isolated from its underlying platforms. |
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide an alternative user interface that functions as assistive technology. |
503.4 User Controls for Captions and Audio Description |
See 503.4.1-503.4.2 |
|
503.4.1 Caption Controls |
Supports |
Where the product displays video with synchronized audio and captions, it provides caption controls. |
503.4.2 Audio Description Controls |
Not Applicable |
The product does not provide controls for program selection. |
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 WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Does Not Support |
Accessibility features, such as closed captioning and audio description tracks embedded in a file, will be removed when multimedia content is uploaded to the product. |
504.2.2 PDF Export |
Not Applicable |
The product does not export PDF files. |
504.3 Prompts |
Does Not Support |
The product does not prompt users to create accessible content. |
504.4 Templates |
Not Applicable |
The product does not provide templates. |
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:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Web: Does Not Support Authored Content (HTML): Does Not Support |
Web: Most functions of the product are not functional for users without vision, owing primarily to insufficient element roles, text alternatives, and keyboard behaviors. As previously noted in 1.3.1 Info and Relationships and 2.1.1 Keyboard, the product relies on visual cues and mouse driven behavior for interacting with and creating content. Authored Content (HTML): Most authored HTML content is not functional for users without vision. As noted in 1.1.1 Non-text Content, cannot receive alternative text. Additionally, as noted in in 1.3.1 Info and Relationships, visually displayed headings are not programmatically defined. |
4.2.2 Usage with limited vision |
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Most content in the product is functional for users with limited vision. As noted in 1.4.4 Resize text and 1.4.5 Images of Text, the product allows resizing of text, and does not include images of text. If users rely on the keyboard to navigate some issues will be encountered, as noted in 2.1.1 Keyboard. Authored Content (HTML): Authors can ensure that users with limited vision can interact with their content. |
4.2.3 Usage without perception of colour |
Web: Supports with Exceptions Authored Content (HTML): Supports |
Web: Most content in the product will be functional for users without perception of color. As noted in 1.4.1 Use of Color, some exceptions, largely related to product navigation, exist. Authored Content (HTML): Authors can ensure that users without perception of color can interact with their content. |
4.2.4 Usage without hearing |
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: The visual components of the product are functional for users without hearing, and as noted in 1.2.2 Captions (Prerecorded) the product provides auto-generated captions for most audio information in prerecorded videos. However, some media content is not understandable, and as noted in 1.2.4 Captions (Live) the product does not provide captions for live videos. Authored Content (HTML): The visual components of authored content are functional for users without hearing; however, as noted in 1.2.2 Captions (Prerecorded), authors cannot provide captions for some audio content. |
4.2.5 Usage with limited hearing |
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: The visual components of the product are functional for users with limited hearing, and as noted in 1.2.2 Captions (Prerecorded) the product provides auto-generated captions for most audio information in prerecorded videos. However, some media content is not understandable, and as noted in 1.2.4 Captions (Live) the product does not provide captions for live videos. Authored Content (HTML): The visual components of authored content are functional for users with limited hearing; however, as noted in 1.2.2 Captions (Prerecorded), authors cannot provide captions for some audio content. |
4.2.6 Usage without vocal capability |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require user vocal capacity. Authored Content (HTML): Authored content does not require user vocal capacity. |
4.2.7 Usage with limited manipulation or strength |
Web: Does Not Support Authored Content (HTML): Supports with Exceptions |
Web: Most functions of the product are not functional for users with limited manipulation who rely on keyboard access. As noted in 2.1.1 Keyboard, controls either do not receive keyboard focus or, as noted in 2.4.7 Focus Visible, do not display a visual indication of keyboard focus. The product is functional with limited strength. Authored Content (HTML): Users with limited manipulation who rely on keyboard access will be able to navigate through Authored Content; however, as noted in 2.4.7 Focus Visible, will not receive a visual indication of keyboard focus. Authored Content will be functional with limited strength. |
4.2.8 Usage with limited reach |
Web: Supports Authored Content (HTML): Supports |
Web: The product is functional with limited reach. Authored Content (HTML): Using the product, authors can create HTML which is functional with limited reach. |
4.2.9 Minimize photosensitive seizure |
Web: Supports Authored Content (HTML): Supports |
Web: The product, as noted in 2.3.1 Three Flashes or Below Threshold, does not contain flashing content. Authored Content (HTML): Authors can design content to ensure that their designs minimize photosensitive seizure triggers. |
4.2.10 Usage with limited cognition |
Web: Supports Authored Content (HTML): Supports |
Web: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product provides icons and supplements these with text, as well as providing the ability to change the interface language to 19 languages. Authored Content (HTML): Authors can ensure that users with limited language, cognitive, and learning abilities can interact with their content. |
4.2.11 Privacy |
Web: Supports Authored Content (HTML): Supports |
Web: When using product features that are provided for accessibility, users can maintain privacy of information in the product. Authored Content (HTML): Using the product, authors can create HTML which conforms to this requirement. |
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 have accessibility features requiring activation. |
5.3 Biometrics |
Not Applicable |
The product does not rely on biological characteristics. |
5.4 Preservation of accessibility information during conversion |
Does Not Support |
In authored content, the product does not preserve captions or separate audio description tracks from author uploaded videos. |
5.5.1 Means of operation |
Not Applicable |
The product does not contain operable parts. |
5.5.2 Operable parts discernibility |
Not Applicable |
The product does not contain operable parts. |
5.6.1 Tactile or auditory status |
Not Applicable |
The product does not contain locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not contain 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 provide a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required. |
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 displays captions in third-party hosted prerecorded videos, but does not display captions in author uploaded videos. |
7.1.2 Captioning synchronization |
Supports |
Where the product displays captions, the product preserves synchronization between the audio and the corresponding captions. |
7.1.3 Preservation of captioning |
Supports with Exceptions |
In authored content, the product preserves and displays captions from third-party hosted prerecorded videos, but does not preserve captions from author uploaded videos. |
7.2.1 Audio description playback |
Does Not Support |
The product does not provide a mechanism to play audio description. |
7.2.2 Audio description synchronization |
Not Applicable |
The product does not play audio descriptions. |
7.2.3 Preservation of audio description |
Does Not Support |
In authored content, the product does not preserve separate audio description tracks from author uploaded videos. |
7.3 User controls for captions and audio description |
Does Not Support |
The product provides caption controls for third-party hosted prerecorded videos, but not for author uploaded videos. The product does not provide controls for audio descriptions. |
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:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.0 section |
See information in WCAG section |
11.2.2 Software success criteria (closed functionality) |
Not Applicable |
|
11.3.2.3 Use of accessibility services |
Supports |
The product uses accessibility services of the browser platform. |
11.3.2.4 Assistive technology |
Not Applicable |
The product is not assistive technology. |
11.3.2.5 Object information |
Does Not Support |
Most core functions of the product contain functional components which lack role, state, or accessible name information. All of the “Add Media” components when editing a project do not convey a programmatic role. Most icons used in place of text do not contain programmatic names. |
11.3.2.6 Row, column, and headers |
Not Applicable |
The product does not contain data tables. |
11.3.2.7 Values |
Supports |
The product allows users to programmatically determine values. |
11.3.2.8 Label relationships |
Does Not Support |
The product visually provides labels for components; however, the relationship between components and labels, such as those in the preferences page, is not programmatically determinable. |
11.3.2.9 Parent-child relationships |
Supports with Exceptions |
The product relies on nested lists and programmatic headings to indicate parent-child relationships between elements; however, some exceptions, such as the Project Editor’s in-line “Insert Media” controls, exist. |
11.3.2.10 Text |
Supports |
Text content, text attributes, and text boundaries are programmatically determinable. |
11.3.2.11 List of available actions |
Does Not Support |
Most components do not contain a programmatic role, and therefore do not convey a list of actions that can be executed. |
11.3.2.12 Execution of available actions |
Supports |
Components allow assistive technologies to programmatically execute actions upon them. |
11.3.2.13 Tracking of focus and selection attributes |
Does Not Support |
The product does not provide a means to visually track the focus cursor. |
11.3.2.14 Modification of focus and selection attributes |
Supports |
When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically. |
11.3.2.15 Change notification |
Does Not Support |
When components in the product change their states and values, such as when filtering options are selected, notifications are not provided to assistive technologies. |
11.3.2.16 Modifications of states and properties |
Does Not Support |
Most states and properties of objects, particularly within the project editor, cannot be set programmatically. Components to align, bold, italicize, or underline text contain no programmatic state. |
11.3.2.17 Modifications of values and text |
Supports |
When the value of an input control in the product can be modified by users in general, the value can be modified by assistive technology. The text content of text input controls in the product can be modified by assistive technology. |
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 |
The product does not disrupt platform accessibility features. |
11.5 User preferences |
Not Applicable |
The product is a web application, which is isolated from its underlying platforms. |
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section |
See information in WCAG section |
11.6.3 Preservation of accessibility information in transformations |
Does Not Support |
Accessibility features, such as closed captioning and audio description tracks embedded in a file, will be removed when multimedia content is uploaded to the product. |
11.6.4 Repair assistance |
Does Not Support |
The product does not provide repair suggestions when known accessibility violations could be detected. |
11.6.5 Templates |
Not Applicable |
The product does not provide templates. |
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
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)