Adobe Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Product Information
Name of Product/Version: Behance iOS
Product Description: Behance is the leading online platform to showcase & discover creative work. The creative world updates their work in one place to broadcast it widely and efficiently. Companies explore the work and access talent on a global scale.
Date: September 2022
Contact information: access@adobe.com
Notes: 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 Behance 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 standard/guidelines:
Standard/Guideline |
Included in Report |
---|---|
Level A: Yes |
|
Level A: Yes |
|
Yes |
|
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.
- Partially Supports: 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.x Report
All WCAG sections also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation.
- 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.x 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.
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)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Does Not Support |
Software (iOS): The product provides sufficient text alternatives for most instances of images. Exceptions include:
Authored Content (HTML): The product does not allow authors to provide text alternatives for images. |
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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain prerecorded audio-only or video-only media. Authored Content (HTML): Authors can provide audio description for what would otherwise be video-only media. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain prerecorded synchronized media. Authored Content (HTML): Authors can provide open captions for audio content in video. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain prerecorded video content that would require audio description or a media alternative. Authored Content (HTML): Using embedded content, authors can provide open audio description for video. Additionally, using text features, authors could provide a transcript. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Users can provide open captions along with their live streamed content. Authored Content (HTML): Authored content does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain prerecorded video content that would require audio description. Authored Content (HTML): Using embedded content, authors can provide open audio description for video. |
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)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most visual structure and relationship information, such as headings, is provided through object information. Exceptions include:
Authored Content (HTML): Authors can provide appropriate object information for visual structure and relationships. |
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): 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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Instructions do not rely solely on sensory characteristics. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Does Not Support Authored Content (HTML): Supports |
Software (iOS): The product restricts its view to portrait orientation. Authored Content (HTML): Authored content is embedded in a web application container. Responding to the display orientation is a function of the container, not the authored content. |
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product’s technology does not have support for programmatic identification of input purpose. Authored Content (HTML): Authored content does not contain input fields that collect information about the user. |
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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not convey information through color alone. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.2 Audio Control (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain audio that plays automatically. Authored Content (HTML): Authored content does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most text meets minimum contrast requirements. Exceptions include:
Authored Content (HTML): Authors can ensure that text meets contrast requirements |
1.4.4 Resize text (Level AA)
Revised Section 508
|
Software (iOS): Does Not Support Authored Content (HTML): Supports |
Software (iOS): The product does not provide its own text resizing function. When text is resized using operating system display scaling, content and functionality is lost in most product functions. Authored Content (HTML): Authors can ensure that content meets this criterion to the extent allowable by the user’s viewer application. |
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product uses text instead of images of text. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): At the required width of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Authored Content (HTML): At the required width of 320 CSS pixels, authored content is presented without loss of information or functionality. |
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most meaningful non-text content elements have sufficient contrast. Exceptions include:
Authored Content (HTML): DAuthors can ensure that content meets this criterion. |
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (Android): The product is not implemented using markup languages. Authored Content (HTML): Authors can ensure that content meets this criterion to the extent allowable by the user’s viewer application. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain elements triggered by hover or focus. Authored Content (HTML): Authored content does not contain elements triggered by hover or focus. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most product functionality can be operated through alternative input methods or keyboard interface. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most of the product does not include keyboard traps. Exceptions include:
Authored Content (HTML): Authored content does not include keyboard traps. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not provide character key shortcuts. Authored Content (HTML): Authored content does not provide character key shortcuts. |
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)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most functions of the product do not include time limits. Exceptions include:
Authored Content (HTML): Authored content does not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not include elements which move, blink, scroll, or auto-update. Authored Content (HTML): Authors can ensure that content meets this criterion. |
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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content does not flash. |
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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): This criterion does not apply to non-web software. Authored Content (HTML): Authored content does not contain repeated blocks that would require a skip mechanism. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The title of the software describes its purpose. Authored Content (HTML): The product allows authors to customize the page title. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most components receive focus in a meaningful order. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. Authored Content (HTML): Authors can provide the purpose of links through link text alone or through programmatic context. |
2.4.5 Multiple Ways (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): This criterion does not apply to non-web software. Authored Content (HTML): The product is a single-page web application. It does not contain functional components that appear repeatedly within a set of web pages. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most headings and labels are descriptive. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): In those elements that can receive keyboard focus, focus is indicated visually. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not rely on multipoint or path-based gestures. Authored Content (HTML): Authored content does not rely on multipoint or path-based gestures. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:
Authored Content (HTML): Authors can ensure that the accessible names of controls contain the text of their visible labels. |
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not have functionality operated by device motion or user motion. Authored Content (HTML): Authored content does not have functionality operated by device motion or user motion. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Does Not Support |
Software (iOS): The product relies on the features of the underlying operating system to set and indicate the language of the user interface. Authored Content (HTML): The product does not allow authors to set the language of the document. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Does Not Support |
Software (iOS): Content is only presented in one language at a time. Authored Content (HTML): The product does not allow authors to set the language for individual phrases within content. |
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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Components do not initiate a change of context when focused. Authored Content (HTML): Authors can ensure that content meets this criterion. |
3.2.2 On Input (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Changes of context do not occur automatically on user input. Authored Content (HTML): Authors can ensure that content meets this criterion. |
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): This criterion does not apply to non-web software. Authored Content (HTML): Authored content does not contain a navigational mechanism that is repeated on multiple web pages. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): This criterion does not apply to non-web software. Authored Content (HTML): The product is a single-page web application. It does not contain functional components that appear repeatedly within a set of web pages. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Where input errors are automatically detected, such as when a user attempts to embed an invalid string of text, items in error are identified and error messages are provided as text. Authored Content (HTML): Authored content does not contain user input controls which would require error identification. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Labels are provided for input fields. Authored Content (HTML): Authors can ensure that content meets this criterion. |
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): Where input errors are automatically detected, such as when embedded content does not match an accepted format, suggestions for correction are provided to the user. Authored Content (HTML): Authored content does not contain user input controls that would require suggestions for correction. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): 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 contain legal or financial data and does not modify user-controllable data. |
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)
Revised Section 508
|
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product is not implemented using markup languages. Authored Content (HTML): Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. |
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Software (iOS): Does Not Support Authored Content (HTML): Supports |
Software (iOS): User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): This criterion does not apply to non-web software. Authored Content (HTML): Authored content does not contain status messages. |
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
302.1 Without Vision |
Software (iOS): Does Not Support Authored Content (HTML): Partially Supports |
|
|
302.2 With Limited Vision |
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users with limited vision. |
|
302.3 Without Perception of Color |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not rely solely on color to communicate information. Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
|
302.4 Without Hearing |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not require the use of hearing. Authored Content (HTML): The product is functional for users without hearing. Examples include:
|
|
302.5 With Limited Hearing |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not require the use of hearing. Authored Content (HTML): The product is functional for users with limited hearing. Examples include:
|
|
302.6 Without Speech |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not require the use of speech. Authored Content (HTML): Authors can create content which is functional for users without speech. |
|
302.7 With Limited Manipulation |
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most functions of the product are usable with limited manipulation. Exceptions include:
Authored Content (HTML): Authors can create content which is functional with limited manipulation. |
|
302.8 With Limited Reach and Strength |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product is functional with limited reach and strength. Authored Content (HTML): Authors can create content which is functional with limited reach and strength. |
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides an interface that relies on icons, contains a streamlined interface, and does not auto play audio content. Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. |
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
501.1 Scope – Incorporation of WCAG 2.x AA |
See WCAG 2.x section |
See information in WCAG 2.x section. |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is not platform software. |
|
502.2.2 No Disruption of Accessibility Features |
Partially Supports |
The product does not disrupt most platform accessibility features. Exceptions include:
|
|
502.3.1 Object Information |
Does Not Support |
Most objects in the product do not expose name, role, state, boundary, or description information to assistive technology. |
|
502.3.2 Modification of Object Information |
Supports |
The product allows assistive technology to modify states and properties of controls. |
|
502.3.3 Row, Column, and Headers |
Not Applicable |
The product does not use data tables. |
|
502.3.4 Values |
Supports |
The product exposes the values of input controls to assistive technology. |
|
502.3.5 Modification of Values |
Supports |
The product allows assistive technology to modify the values and text of input controls. |
|
502.3.6 Label Relationships |
Partially Supports |
The product exposes most label relationships to assistive technology. Exceptions include:
|
|
502.3.7 Hierarchical Relationships |
Does Not Support |
The product does not expose most hierarchical parent-child relationships, such as programmatic heading relationships, to assistive technology. |
|
502.3.8 Text |
Supports |
The product exposes text content and text values to assistive technology. |
|
502.3.9 Modification of Text |
Supports |
The product allows assistive technology to modify the text of input controls. |
|
502.3.10 List of Actions |
Does Not Support |
Most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology. |
|
502.3.11 Actions on Objects |
Partially Supports |
|
|
502.3.12 Focus Cursor |
Supports |
The product exposes focus, text insertion point, and selection attributes to assistive technology. |
|
502.3.13 Modification of Focus Cursor |
Supports |
|
|
502.3.14 Event Notification |
Supports |
The product notifies assistive technology about attribute changes in user interface elements. |
|
502.4 Platform Accessibility Features |
Not Applicable |
The product is not platform software. |
|
503.2 User Preferences |
Partially Supports |
|
|
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide an alternative user interface that functions as assistive technology. |
|
503.4.1 Caption Controls |
Supports |
The product provides user controls for captions. |
|
503.4.2 Audio Description Controls |
Does Not Support |
The product does not provide user controls for audio descriptions. |
|
504.2 Content Creation or Editing |
See WCAG 2.x section |
See information in WCAG 2.x section. |
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Does Not Support |
When converting content, the product does not preserve closed captioning or audio descriptions. |
|
504.2.2 PDF Export |
Not Applicable |
The product does not export PDF files. |
|
504.3 Prompts |
Does Not Support |
Most authoring functions do not prompt authors to create content which conforms to WCAG 2.0 Levels A and AA. |
|
504.4 Templates |
Not Applicable |
The product does not provide templates for authored content. |
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: Functional Performance Statements (FPS)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Software (iOS): Does Not Support Authored Content (HTML): Partially Supports |
Software (iOS): Most functions of the product are not usable without vision. Examples include:
Authored Content (HTML): Authors can create content in which most functions can be used without vision. Exceptions include:
|
4.2.2 Usage with limited vision |
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users with limited vision. |
4.2.3 Usage without perception of colour |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not rely solely on color to communicate information. Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
4.2.4 Usage without hearing |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not require the use of hearing. Authored Content (HTML): The product is functional for users without hearing. Examples include:
|
4.2.5 Usage with limited hearing |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not require the use of hearing. Authored Content (HTML): The product is functional for users with limited hearing. Examples include:
|
4.2.6 Usage with no or limited vocal capability |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not require the use of speech. Authored Content (HTML): Authors can create content which is functional for users without speech. |
4.2.7 Usage with limited manipulation or strength |
Software (iOS): Partially Supports Authored Content (HTML): Supports |
Software (iOS): Most of the product is functional with limited manipulation and strength. Exceptions include:
Authored Content (HTML): Authors can create content which is functional with limited manipulation. |
4.2.8 Usage with limited reach |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product is functional with limited reach. Authored Content (HTML): Authors can create content which is functional with limited reach. |
4.2.9 Minimize photosensitive seizure triggers |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): 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. |
4.2.10 Usage with limited cognition, language or learning |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides an interface that relies on icons, contains a streamlined interface, and does not auto play audio content. Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Software (iOS): Supports Authored Content (HTML): Supports |
Software (iOS): The product does not ask for or display legal, financial, or personal data. Authored Content (HTML): Authors can create content which maintains user privacy when accessibility features are used. |
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed functionality |
Not Applicable |
5.1.2.2-5.1.7 are not applicable for this product, which has no closed functionality. |
5.2 Activation of accessibility features |
Not Applicable |
The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not use biological characteristics for user identification or for control of the product. |
5.4 Preservation of accessibility information during conversion |
Does Not Support |
When converting content, while closed captioning content may be detected by the product, only open captioning will be rendered to users. Similarly, alternative audio description tracks cannot be selected. |
5.5.1 Means of operation |
Not Applicable |
The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate. |
5.5.2 Operable parts discernibility |
Partially Supports |
The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include:
|
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 turn off or adjust key repeat. |
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 |
Does Not Support |
Although the product provides controls to toggle closed captioning, it does not display available closed captioning tracks. |
7.1.2 Captioning synchronization |
Not Appplicable |
The product does not display closed captions. |
7.1.3 Preservation of captioning |
Does Not Support |
The product does not preserve closed caption data when transmitting video. |
7.1.4 Captions characteristics |
Not Appplicable |
The product provides captioning only through the display of unmodifiable characters. |
7.1.5 Spoken subtitles |
Not Appplicable |
The product does not display closed captioning tracks that are programmatically determinable. |
7.2.1 Audio description playback |
Does Not Support |
The product does not provide a mechanism to select and play closed audio description. |
7.2.2 Audio description synchronization |
Not Appplicable |
The product does have a mechanism to play closed audio description. |
7.2.3 Preservation of audio description |
Does Not Support |
The product does not preserve closed audio description data when transmitting video. |
7.3 User controls for captions and audio description |
Does Not Support |
The product provides user controls for captions, but not for audio descriptions. |
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.x section)
Chapter 10: Non-web Documents
Notes: Not Applicable
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
10.1.1.1 through 10.4.1.3 |
See WCAG 2.x section |
See information in WCAG 2.x section |
10.5 Caption positioning |
Document (Video): Not Applicable Authored Content (HTML): Not Applicable |
Document (Video): The video does not have captions which would require positioning. Authored Content (HTML): The product does not allow authors to create captions which would require positioning. |
10.6 Audio description timing |
Document (Video): Not Applicable Authored Content (HTML): Not Applicable |
Document (Video): The video does not have audio description which would require timing. Authored Content (HTML): The product does not allow authors to create audio descriptions which would require timing. |
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
11.1.1.1 through 11.4.1.3 |
See WCAG 2.x section |
See information in the WCAG 2.x section. |
|
11.5.2.3 Use of accessibility services |
See 11.5.2.5 through 11.5.2.17 |
See information in 11.5.2.5 through 11.5.2.17. |
|
11.5.2.4 Assistive technology |
Not Applicable |
The product is not assistive technology. |
|
11.5.2.5 Object information |
Does Not Support |
Most objects in the product do not expose name, role, state, boundary, or description information to assistive technology. |
|
11.5.2.6 Row, column, and headers |
Not Applicable |
The product does not use data tables. |
|
11.5.2.7 Values |
Supports |
The product exposes the values of input controls to assistive technology. |
|
11.5.2.8 Label relationships |
Partially Supports |
The product exposes most label relationships to assistive technology. Exceptions include:
|
|
11.5.2.9 Parent-child relationships |
Does Not Support |
The product does not expose most hierarchical parent-child relationships to assistive technology. |
|
11.5.2.10 Text |
Supports |
The product exposes text content and text values to assistive technology. |
|
11.5.2.11 List of available actions |
Does Not Support |
Most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology. |
|
11.5.2.12 Execution of available actions |
Supports |
The product allows assistive technology to perform actions on objects. |
|
11.5.2.13 Tracking of focus and selection attributes |
Supports |
The product exposes focus, text insertion point, and selection attributes to assistive technology. |
|
11.5.2.14 Modification of focus and selection attributes |
Supports |
The product allows assistive technology to move focus and modify selection attributes. |
|
11.5.2.15 Change notification |
Supports |
The product notifies assistive technology about attribute changes in user interface elements. |
|
11.5.2.16 Modifications of states and properties |
Supports |
The product allows assistive technology to modify states and properties of controls. |
|
11.5.2.17 Modifications of values and text |
Supports |
The product allows assistive technology to modify the values and text of input controls. |
|
11.6.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
|
11.6.2 No disruption of accessibility features |
Partially Supports |
Most product functions do not disrupt platform accessibility features. Exceptions include:
|
|
11.7 User preferences |
Partially Supports |
|
|
11.8.2 Accessible content creation |
See WCAG 2.x section |
See information in WCAG 2.x section. |
|
11.8.3 Preservation of accessibility information in transformations |
Does Not Support |
The product does not preserve information provided for accessibility for video content. Exceptions include:
|
|
11.8.4 Repair assistance |
Not Applicable |
The product does not have accessibility checking functionality. |
|
11.8.5 Templates |
Not Applicable |
The product does not provide templates for authored content. |
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)