Adobe Accessibility Conformance Report
VPAT® Version 2.3 – December 2018
Product Information
Name of Product/Version: Adobe Experience Manager (AEM) 6.5 Sites
Product Description: Adobe Experience Manager (AEM) 6.5 Sites helps you speed up content creation through a robust content management system (CMS) using artificial intelligence.
Date: July 2019
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: Product testing involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well 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 |
Web Content Accessibility Guidelines 2.1, at https://www.w3.org/TR/WCAG21/ |
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, - V2.1.2 (2018-08) at https://www.etsi.org/deliver/etsi_en//301500_301599/301549/02.01.02_60/en_301549v020102p.pdf |
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.x Level AAA.
WCAG 2.x Report
Tables 1 and 2 also document conformance with:
- • EN 301 549: Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
- • Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.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.
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)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: The product provides sufficient text alternatives for most instances of non-text content, such as images and image buttons. Exceptions include:
Authored Content (HTML): Authors can add a text alternative using the Alternative Text field in the Advanced Image Properties tab in the Image Component dialog box. Notes: Some advanced components, such as the Carousel, do not provide a default means to add alternate text descriptions to images. The system administrator may need to configure these components to support the ‘alt’ attribute. |
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
|
Web: Supports Authored Content (HTML): Supports
|
Web: The product does not contain prerecorded audio-only or video-only media. Authored Content (HTML): Authors can provide alternatives to audio-only and video-only content within the same document or in linked documents. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded synchronized media. Authored Content (HTML): The product does not generate synchronized media. Authors will need to verify that their content conforms to this requirement. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded video content that would require audio description or a media alternative. Authored Content (HTML): The product does not generate synchronized media. Authors will need to verify that their content conforms to this requirement. |
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
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most structure and relationship information, such as the structure of lists and tables, is provided through element semantics. Exceptions include:
Authored Content (HTML): Authors can provide appropriate semantics and textual information for visual structures and relationships. |
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product presents content in a meaningful sequence. Authored Content (HTML): The product allows authors to present content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Instructions do not rely solely on sensory characteristics. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product do not convey information through color alone. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.2 Audio Control (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain audio that plays automatically. Authored Content (HTML): Authors can create content that provides a mechanism to pause or stop the audio. |
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
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: Critical user flows to use the product cannot be accomplished through a keyboard interface alone. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most of the product allows the user to navigate away from any control that can be navigated to using the keyboard alone. Exceptions include:
Authored Content (HTML): Authored content can be made without keyboard traps. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: The single character key shortcuts provided are only active when a page is selected. Authored Content (HTML): Authored content can be made without 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
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not include time limits. Authored Content (HTML): The product does not create content that requires timed responses. Authors may create this functionality and can ensure that it meets this requirement. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: 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
|
Web: Supports Authored Content (HTML): Supports
|
Web: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content does not flash. |
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
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The product does not provide a mechanism to bypass repeated navigation blocks of content. The keyboard user is required to tab repeatedly (30-40 tab stops) through menu items. Authored Content (HTML): Authors can ensure that content meets this criterion by providing skip links to bypass repeated blocks of content in a set of pages. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: When editing specific pages, the title describes the purpose of the page. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: 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
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: The purpose of links in the product can be determined from the link text alone or from programmatic context of the link with the rare exception of links that were meant to be visually hidden that do not contain the link purpose. Authored Content (HTML): Authors can provide the purpose of links through link text alone or through programmatic context. |
2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to:
Revised Section 508 - Does not apply
|
Web: Supports Authored Content (HTML): Supports |
Web: Functionality of the product that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture. Authored Content (HTML): Authors can create content that does not use multipoint or path-based gestures for operation. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: For functionality of the product that can be operated using a single pointer, the down event is not used to execute the function except where essential. Authored Content (HTML): Authors can create content that allows for the cancellation of single-point activation. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: The accessible names of controls contain the text of their visible labels. 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 |
Web: Supports Authored Content (HTML): Supports |
Web: Product functionality is not operated by device motion or user motion. Authored Content (HTML): Functionality in authored content is not 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
|
Web: Supports Authored Content (HTML): Supports |
Web: The language is programmatically determinable within the product. Authored Content (HTML): Authors can set the language for 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
|
Web: Supports Authored Content (HTML): Supports |
Web: Components do not initiate a change of context when focused. Authored Content (HTML): In the default configuration, interactive components provided for authors do not initiate a change of context on focus. |
3.2.2 On Input (Level A)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Changes of context do not occur automatically on user input. Authored Content (HTML): Authors can ensure that 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)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Input errors are identified and described to the users in text. Authored Content (HTML): Error identification text can be added using the constraints tab in each standard form component dialog. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports
|
Web: Labels are provided for input fields. There may be some exceptions. Authored Content (HTML): Authors can ensure that content meets this criterion. Programmatic labels are created when form inputs are added to a document. Note: Providing programmatic labels for groups of controls may require editing of the page source code or configuration of component editors. |
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
|
Web: Partially Supports Authored Content (HTML): Partially Supports |
Web: The user interface code in general has complete start and end tags. Elements may not be nested according to specifications or elements may contain duplicate attributes or duplicate IDs. Authored Content: Authors can ensure that content meets this criterion. Conforming documents can be created using the product. Note: Production of conforming documents may require editing of the page source code or configuration of component editors. There are some duplicate ids. |
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: For most of the product, the name and role of components can be programmatically determined, states, properties, and values can be programmatically set, and notification of changes to these items is available to assistive technology. Exceptions include:
Authored Content (HTML): 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)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain live synchronized media. Authored Content (HTML): The product does not generate synchronized media. Authors will need to verify that their content conforms to this requirement. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded video content that would require audio description. Authored Content (HTML): The product does not generate synchronized media. Authors will need to verify that their content conforms to this requirement. |
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Content does not restrict its view and operation to a single display orientation. Authored Content (HTML): Authors can ensure that content does not restrict its view and operation to a single display orientation. |
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain input fields that collect information about the user. 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)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Some 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)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports
|
Web: The product mostly allows browser zoom to resize text up to 200 percent without loss of content or functionality. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.5 Images of Text (Level AA)
Revised 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. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 - Does not apply |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most content is available at a 320 pixel width or a 256 pixel height. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 - Does Not Apply |
Web: Supports Authored Content (HTML): Supports |
Web: User interface components and informative graphical objects in the product have sufficient contrast. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Loss of functionality does not occur by setting the specified style changes in the product. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Where receiving or removing pointer hover and keyboard focus, the product’s additional content is dismissable, hoverable, and persistent. 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)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Users can locate web pages in the product through multiple ways. Authored Content (HTML): Authors can provide more than one way to locate a page in a set of pages. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most headings and labels, where identified, are descriptive. There may be some exceptions. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Many focusable elements have a visible keyboard focus indicator. In some cases, actionable controls do not exhibit a visual indication of focus. Exceptions include:
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.2 Language of Parts (Level AA)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Content is only presented in one language at a time. Authored Content (HTML): Authors can set the language for individual phrases within content using the edit HTML code option. |
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)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: When navigational mechanisms are repeated in the product, such as in the header or as the user progresses through the steps of an activity, they occur in a consistent relative order. Authored Content (HTML): Authors can ensure that the navigational mechanisms they use on the form are consistent. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Components with the same functionality are identified consistently. Authored Content (HTML): Authors can ensure that components with the same functionality are identified consistently in a set of pages. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Where input errors are automatically detected, such as form fields using invalid characters, suggestions for correction are provided to the user when possible. Some text for descriptions and suggestions may be vague. Authored Content (HTML): Authors can add functionality to provide error suggestions. Note: Providing error suggestion functionality may require editing of the page source code or configuration of component editors. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing. Authored Content (HTML): Authors can ensure that content meets this criterion. Authors can add scripted functionality to conform to this requirement. Note: Providing the scripted functionality may require editing of the page source code or configuration of component editors. |
4.1.3 Status Messages (Level AA)
Revised Section 508 - Does not apply |
Web: Partially Supports Authored Content (HTML): Supports |
Web: When status updates do not receive focus, such as when submitting an edit or creating a new activity, the product provides the update to assistive technology as a live region. Authored Content (HTML): Authors can ensure that content meets this criterion. |
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 |
Web: Does Not Support Authored Content (HTML): Supports |
Web: Some individual controls in the product are keyboard operable and functional without vision. However, most complete processes of the product are not usable without vision:
Authored Content (HTML): Authors can create content which is functional for users without vision. |
302.2 With Limited Vision |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited vision. |
302.3 Without Perception of Color |
Web: Partially Supports Authored Content (HTML): Supports |
Web: The product does not rely solely on color to communicate information, with the exception of error messages as described in 1.4.1 Use of Color. Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
302.4 Without Hearing
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authors can create content which is functional for users without hearing. |
302.5 With Limited Hearing
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authors can create content which is functional for users with limited hearing. |
302.6 Without Speech
|
Web: Supports Authored Content (HTML): Supports |
Web: 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 |
Web: Does Not Support Authored Content (HTML): Supports |
Web: Some controls in the product are keyboard operable. However, most complete processes of the product are not usable with limited manipulation.
Authored Content (HTML): Authors can create content which is functional with limited manipulation. |
302.8 With Limited Reach and Strength |
Web: Partially Supports Authored Content (HTML): Supports
|
Web: The product is mostly functional with limited reach and strength. The product requires the use of a computer mouse for full functionality. Authored Content (HTML): Authors can create content which is functional with limited reach and strength. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: Partially Supports Authored Content (HTML): Supports |
Web: 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 online help and consistent identification of user interface components. However, some functions of the product are more difficult than necessary for users with limited language, cognitive, and learning abilities; examples are:
Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. |
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes: AEM 6.5 Sites is considered a Software product with exceptions for 502 and 503 because it is a web application that does not have access to platform accessibility services. See the WCAG 2.x Level A and Level AA Success Criteria for additional details.
501 General
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section. |
See information in the WCAG section |
504 Authoring Tools |
||
504.2 Content Creation or Editing |
See WCAG 2.x section. |
See information in WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
The product software does not convert information to and from different formats. |
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 |
Templates are not provided. However, authors can create templates to assist in the creation of content. Authors can ensure the WCAG 2.0 Level A and AA requirements are satisfied in the templates. Content authors will also need to ensure that the content is accessible. |
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: According to C.4 Functional Performance, this section is informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Web: Does Not Support Authored Content (HTML): Supports
|
Web: Some individual controls in the product are keyboard operable and functional without vision. However, most complete processes of the product are not usable without vision:
Authored Content (HTML): Authors can create content which is functional for users without vision. |
4.2.2 Usage with limited vision |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited vision. |
4.2.3 Usage without perception of colour |
Web: Partially Supports Authored Content (HTML): Supports |
Web: The product does not rely solely on color to communicate information, with the exception of error messages as described in 1.4.1 Use of Color. Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
4.2.4 Usage without hearing |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authors can create content which is functional for users without hearing. |
4.2.5 Usage with limited hearing |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authors can create content which is functional for users with limited hearing. |
4.2.6 Usage without vocal capability
|
Web: Supports Authored Content (HTML): Supports |
Web: 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 |
Web: Does Not Support Authored Content (HTML): Supports
|
Web: Some controls in the product are keyboard operable. However, most complete processes of the product are not usable with limited manipulation or strength.
Authored Content (HTML): Authors can create content which is functional with limited manipulation. |
4.2.8 Usage with limited reach
|
Web: Supports Authored Content (HTML): Supports |
Web: The product is functional with limited reach. Authored Content (HTML): Authors can create content which is functional with limited reach and strength. |
4.2.9 Minimize photosensitive seizure |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain flashing content. Authored Content (HTML): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures. |
4.2.10 Usage with limited cognition |
Web: Partially Supports Authored Content (HTML): Supports |
Web: The product provides online help and consistent identification of user interface components. Most functions of the product are consistent and straight forward for users with limited cognitive abilities. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not ask for legal, financial, or personal data. Authored Content (HTML): Authors can create content which does not ask for legal, financial, or personal data. |
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 specific documented accessibility features. The software instead relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not rely on biometric information. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
As described in 504.2.1 in the Revised Section 508, the product software does not convert information to and from different formats. |
5.5.1 Means of operation |
Not Applicable |
The product does not have operable parts that require grasping, pinching, or twisting of the wrist to operate. |
5.5.2 Operable parts discernibility |
Not Applicable |
The product has only non-mechanical operable parts, such as on-screen buttons. |
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: Not Applicable
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: 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 section |
10.5 Caption positioning |
Authored Content (Video): Not Applicable |
The product does not allow authors to create captions which would require positioning. |
11.6.1 User control of accessibility features |
Authored Content (Video): Not Applicable |
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 |
Not Applicable |
Not applicable to web |
11.5.2.1 Platform accessibility service support for software that provides a user interface |
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.2 Platform accessibility service support for assistive technologies |
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.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 |
Not applicable to web |
11.5.2.5 Object information |
Not Applicable |
Not applicable to web |
11.5.2.6 Row, column, and headers |
Not Applicable |
Not applicable to web |
11.5.2.7 Values |
Not Applicable |
Not applicable to web |
11.5.2.8 Label relationships |
Not Applicable |
Not applicable to web |
11.5.2.9 Parent-child relationships |
Not Applicable |
Not applicable to web |
11.5.2.10 Text |
Not Applicable |
Not applicable to web |
11.5.2.11 List of available actions |
Not Applicable |
Not applicable to web |
11.5.2.12 Execution of available actions |
Not Applicable |
Not applicable to web |
11.5.2.13 Tracking of focus and selection attributes |
Not Applicable |
Not applicable to web |
11.5.2.14 Modification of focus and selection attributes |
Not Applicable |
Not applicable to web |
11.5.2.15 Change notification |
Not Applicable |
Not applicable to web |
11.5.2.16 Modifications of states and properties |
Not Applicable |
Not applicable to web |
11.5.2.17 Modifications of values and text |
Not Applicable |
Not applicable to web |
11.6.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
11.6.2 No disruption of accessibility features |
Supports |
The product does not disrupt platform accessibility features. |
11.7 User preferences |
Supports |
The product adapts to platform settings for color, contrast, font size, and focus cursor. |
11.8.2 Accessible content creation |
See WCAG 2.x section. |
See information in WCAG section |
11.8.3 Preservation of accessibility information in transformations |
Supports |
The product preserves information provided for accessibility. |
11.8.4 Repair assistance |
Not Applicable |
The product does not have accessibility checking functionality. |
11.8.5 Templates |
Not Applicable |
Templates are not provided. However, authors can create templates to assist in the creation of content. Authors can ensure the WCAG 2.0 Level A and AA requirements are satisfied in the templates. Content authors will also need to ensure that the content is accessible. |
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)