Adobe Accessibility Conformance Report
VPAT® Version 2.3 – December 2018
Product Information
- Name of Product/Version: FrameMaker 2019 Release
- Product Description: Fast. Powerful. Future-ready. Boost performance with an all-new 64-bit FrameMaker. Create rich, immersive content with unmatched image handling capabilities. Experience faster opening and publishing of PDF and HTML5 files. Push the envelope with new capabilities built on top of the latest technologies. Get started with XML/DITA authoring with an easy-to-use workspace, productivity enhancements and lots more.
- Date: August 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: Testing Adobe FrameMaker 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:
Level AA: Yes
Level AAA: No
Level AA: Yes
Level AAA: No
Corrections to the ICT Final Rule as published by the US Access Board in the Federal Register on January 22, 2018
https://www.etsi.org/deliver/etsi_en//301500_301599/301549/02.01.02_60/en_301549v020102p.pdf
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
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.
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.1.1 (Web)
- 10.1.1.1 (Non-web document)
- 11.1.1.1.1 (Open Functionality Software)
- 11.1.1.1.2 (Closed Functionality Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Most product functions do not contain images which would require a text alternative. Exceptions include:
In the document editor, embedded image objects lack a text alternative.
In the QR Code Builder dialog, the QR code graphic does not provide a text alternative.
Authored Content (HTML): Authors can provide text alternatives for most images. Exceptions include:
Some image buttons in the navigation controls, such as Previous and Next, lack text alternatives.
Authored Content (PDF): Authors can provide text alternatives for images.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.1 (Web)
- 10.1.2.1 (Non-web document)
- 11.1.2.1.1 (Open Functionality Software)
- 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: 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 embedded in a document. Authors can also provide transcripts for video-only media.
Authored Content (PDF): Authors can provide audio description for what would otherwise be video-only media embedded in a document. Authors can also provide transcripts for video-only media.
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.2 (Web)
- 10.1.2.2 (Non-web document)
- 11.1.2.2 (Open Functionality Software)
- 11.1.2.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product does not contain prerecorded synchronized media.
Authored Content (HTML): Authors can provide open captions for audio content in embedded video, but the product does not allow authors to provide closed captions.
Authored Content (PDF): Authors can provide open captions for audio content in embedded video, but the product does not allow authors to provide closed captions.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.3 (Web)
- 10.1.2.3 (Non-web document)
- 11.1.2.3.1 (Open Functionality Software)
- 11.1.2.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not contain prerecorded video content that would require audio description or a media alternative.
Authored Content (HTML): Authors can provide transcripts for video.
Authored Content (PDF): Authors can provide transcripts for video.
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.4 (Web)
- 10.1.2.4 (Non-web document)
- 11.1.2.4 (Open Functionality Software)
- 11.1.2.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not contain live synchronized media.
Authored Content (HTML): Authored content does not contain live synchronized media.
Authored Content (PDF): Authored content does not contain live synchronized media.
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.5 (Web)
- 10.1.2.5 (Non-web document)
- 11.1.2.5 (Open Functionality Software)
- 11.1.2.5 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product does not contain prerecorded video content that would require audio description.
Authored Content (HTML): Authors can embed video with audio description in the main narration track, but the product does not allow authors to provide separate audio description tracks.
Authored Content (PDF): Authors can embed video with audio description in the main narration track, but the product does not allow authors to provide separate audio description tracks.
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.1 (Web)
- 10.1.3.1 (Non-web document)
- 11.1.3.1.1 (Open Functionality Software)
- 11.1.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Does Not Support
Software: Most structure and relationship information, such as grouping of form fields, is provided through object information. However, some information is provided visually but is not provided to assistive technology. Examples include:
In a document window, the XML hierarchy text is not provided to assistive technology.
In the Spell Checker dialog, the radio buttons lack programmatic grouping.
In the Standard Templates window, the text content is not provided to assistive technology.
Authored Content (HTML): Most visual structure and relationship information is provided through element semantics.
Exceptions include:
Headings are not programmatically indicated as such.
Lists are not programmatically indicated as such.
Authored Content (PDF): Most visual structure and relationship information is not provided through element semantics.
Examples include:
Most text elements are not tagged.
Most list items are not structured properly.
Most headings are not denoted through structure.
Most tab order entries with annotations are not set to “Structure”.
Some table headers are not associated with their respective data cells.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.2 (Web)
- 10.1.3.2 (Non-web document)
- 11.1.3.2.1 (Open Functionality Software)
- 11.1.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product presents most content in a meaningful sequence. However, in some cases text in the document editor is announced out of sequence in assistive technology. Examples include:
When two pages appear side by side, alternating lines of text from the two pages are announced.
When a pod appears in front of a document, pod text is announced between lines of document text.
Authored Content (HTML): Content is presented in a meaningful sequence.
Authored Content (PDF): Content is presented in a meaningful sequence.
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.3 (Web)
- 10.1.3.3 (Non-web document)
- 11.1.3.3 (Open Functionality Software)
- 11.1.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most instructions do not rely solely on sensory characteristics. Exceptions include:
In the Standard Templates window, an instruction relies on visual position information.
Authored Content (HTML): Authors can ensure that content meets this criterion.
Authored Content (PDF): Authors can ensure that content meets this criterion.
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.3.4 (Web)
- 10.1.3.4 (Non-web document)
- 11.1.3.4 (Open Functionality Software)
- 11.1.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Content does not restrict its view and operation to a single display orientation.
Authored Content (HTML): Authored content does not restrict its view and operation to a single display orientation.
Authored Content (PDF): Authored content does not restrict its view and operation to a single display orientation.
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.3.5 (Web)
- 10.1.3.4 (Non-web document)
- 11.1.3.5 (Open Functionality Software)
- 11.1.3.5 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not contain input fields that collect information about the user.
Authored Content (HTML): Authored content does not include input fields that collect information about the user.
Authored Content (PDF): Authored content does not include 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.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.1 (Web)
- 10.1.4.1 (Non-web document)
- 11.1.4.1 (Open Functionality Software)
- 11.1.4.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most functions of the product do not convey information through color alone. Exceptions include:
In some tab lists, the currently selected tab is indicated solely by a color difference.
Authored Content (HTML): Authors can ensure that content meets this criterion.
Authored Content (PDF): Authors can ensure that content meets this criterion.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.2 (Web)
- 10.1.4.2 (Non-web document)
- 11.1.4.2 (Open Functionality Software)
- 11.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not contain audio that plays automatically.
Authored Content (HTML): Authored content does not contain audio that plays automatically.
Authored Content (PDF): Authored content does not contain audio that plays automatically.
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.3 (Web)
- 10.1.4.3 (Non-web document)
- 11.1.4.3 (Open Functionality Software)
- 11.1.4.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most text meets minimum contrast requirements. Exceptions include:
In the Welcome screen, the DITA version number has insufficient color contrast.
In the Standard Templates window, green text elements have insufficient color contrast.
Authored Content (HTML): Authors can ensure that text meets contrast requirements.
Authored Content (PDF): Authors can ensure that text meets contrast requirements.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.4 (Web)
- 10.1.4.4 (Non-web document)
- 11.1.4.4.1 (Open Functionality Software)
- 11.1.4.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not provide its own text resizing function. When text is resized using operating system display scaling, some content is unavailable. Examples include:
In the Welcome screen, some content under “Resources” and “Learn” extends off-screen and cannot be scrolled into view.
In the QR Code Builder dialog, some form controls extend off-screen and cannot be scrolled into view.
Authored Content (HTML): Using browser zoom, text can be resized up to 200 percent without loss of content or functionality.
Authored Content (PDF): Using the zoom function of a PDF reader application, text can be resized up to 200 percent without loss of content or functionality.
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.5 (Web)
- 10.1.4.5 (Non-web document)
- 11.1.4.5.1 (Open Functionality Software)
- 11.1.4.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: The product uses text instead of images of text, except for branding elements that are considered essential.
Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include:
When text is grouped with a non-text object, it is published as an image of text.
Authored Content (PDF): Authored content does not contain images of text.
1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.4.10 (Web)
- 10.1.4.10 (Non-web document)
- 11.1.4.10.1 (Open Functionality Software)
- 11.1.4.10.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Does Not Support
Authored Content (HTML): Supports
Authored Content (PDF): Partially Supports
Software: At the required width of 320 CSS pixels, content or functionality extends off-screen in most product functions and cannot be scrolled into view. Examples include:
In most pods and dialogs, form controls and content extend off-screen.
In the Welcome screen, most sections of content are cut off.
In the status bar of the Document window, content is cut off.
Authored Content (HTML): At the required width equivalent of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions.
Authored Content (PDF): At the required width of 320 CSS pixels, most authored content is presented without loss of information or functionality. Some authored content, such as pages containing interactive annotations, requires two-dimensional layout for meaning and relies on scrolling in two dimensions. Exceptions include:
Footnote markers do not appear in superscript position.
1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.4.11 (Web)
- 10.1.4.11 (Non-web document)
- 11.1.4.11 (Open Functionality Software)
- 11.1.4.11 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Most meaningful non-text content elements, such as form controls and graphical buttons, have sufficient contrast. Exceptions include:
Borders of text entry fields lack sufficient color contrast.
The selected state indicator of some toolbar buttons lacks sufficient color contrast.
Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include:
Some Search form controls lack sufficient contrast.
Some navigation controls use a low-contrast color to indicate selection.
Authored Content (PDF): Authors can ensure that content meets this criterion.
1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.4.12 (Web)
- 10.1.4.12 (Non-web document)
- 11.1.4.12 (Open Functionality Software)
- 11.1.4.12 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product’s Welcome screen has markup content but no mechanism for applying text style properties to the content.
Authored Content (HTML): Authors can ensure that content meets this criterion.
Authored Content (PDF): Authors can ensure that content meets this criterion.
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.4.13 (Web)
- 10.1.4.13 (Non-web document)
- 11.1.4.13 (Open Functionality Software)
- 11.1.4.13 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include:
Tooltip text disappears when hovered with a mouse pointer.
Authored Content (HTML): Authored content does not contain content elements triggered by hover or focus.
Authored Content (PDF): Authored content does not contain content elements triggered by hover or focus.
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.1 (Web)
- 10.2.1.1 (Non-web document)
- 11.2.1.1.1 (Open Functionality Software)
- 11.2.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Some product functionality, such as the functions of most dialogs and pods, can be operated directly through a keyboard interface. Some controls do not receive keyboard focus, such as editor toolbars and Welcome screen controls, yet the same functions are available through standard keystrokes in application menus or through documented product-specific keyboard shortcuts. However, some functions are not keyboard accessible. Exceptions include:
Some functions of the Welcome screen
Functions of the Drawing toolbar.
Insertion of symbols from the Equations pod.
Selection of objects previously inserted in a document, such as frames and images.
The workspace switcher function.
Display of tooltip text for graphical buttons.
Authored Content (HTML): Most product functionality can be operated through a keyboard interface. Exceptions include:
Some active controls are not keyboard operable.
Some same page navigational links do not move programmatic focus to the target content.
Authored Content (PDF): Authored content functionality can be operated through a keyboard interface.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.2 (Web)
- 10.2.1.2 (Non-web document)
- 11.2.1.2 (Open Functionality Software)
- 11.2.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Some actions, such as closing a dialog or inserting a non-text object in a document, cause a momentary keyboard trap. However, users can continue to other product functions by performing menu commands with the keyboard.
Authored Content (HTML): Authored content does not include keyboard traps.
Authored Content (PDF): Authored content does not include keyboard traps.
2.1.4 Character Key Shortcuts (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.4 (Web)
- 10.2.1.4 (Non-web document)
- 11.2.1.4.1 (Open Functionality Software)
- 11.2.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not provide character key shortcuts.
Authored Content (HTML): Authored content does not provide character key shortcuts.
Authored Content (PDF): Authored content does not provide character key shortcuts.
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.1 (Web)
- 10.2.2.1 (Non-web document)
- 11.2.2.1 (Open Functionality Software)
- 11.2.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not include time limits.
Authored Content (HTML): Authored content does not include time limits.
Authored Content (PDF): Authored content does not include time limits.
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.2 (Web)
- 10.2.2.2 (Non-web document)
- 11.2.2.2 (Open Functionality Software)
- 11.2.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not include elements which move, blink, scroll, or auto-update.
Authored Content (HTML): Authors can ensure that content meets this criterion.
Authored Content (PDF): 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.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.3.1 (Web)
- 10.2.3.1 (Non-web document)
- 11.2.3.1 (Open Functionality Software)
- 11.2.3.1(Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not contain flashing content.
Authored Content (HTML): Authors can ensure that content does not flash.
Authored Content (PDF): 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.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.1 (Web)
- 10.2.4.1 (Non-web document) – Does not apply
- 11.2.4.1 (Open Functionality Software) – Does not apply
- 11.2.4.1 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web softwar
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: This criterion does not apply to non-web software.
Authored Content (HTML): The authored content provides an inline frame, which allows assistive technology users to bypass a repeated navigation block. However, for users without assistive technology, a bypass mechanism is not provided.
Authored Content (PDF): This criterion does not apply to non-web documents.
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.2 (Web)
- 10.2.4.2 (Non-web document)
- 11.2.4.2 (Open Functionality Software) - Does not apply
- 11.2.4.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Does Not Support
Software: Most windows have titles which describe their purpose. Exceptions include:
The Spell Checker pod is presented as a window, but does not provide a title to assistive technology.
Authored Content (HTML): The product allows authors to customize the page title.
Authored Content (PDF): The product does not allow authors to customize the document title or display it in the window title.
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.3 (Web)
- 10.2.4.3 (Non-web document)
- 11.2.4.3 (Open Functionality Software)
- 11.2.4.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Components receive focus in a meaningful order.
Authored Content (HTML): Most components receive focus in a meaningful order. Exceptions include:
Some content, such as the Previous and Next controls, gains focus in the reverse order as its intended visual focus order.
Some content, such as the Search form focus order, does not match the visual order.
Authored Content (PDF): Components receive focus in a meaningful order.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.4 (Web)
- 10.2.4.4 (Non-web document)
- 11.2.4.4 (Open Functionality Software)
- 11.2.4.4 (Closed Software
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: 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): Authored content provides the purpose of links through link text alone or through programmatic context.
Authored Content (PDF): Authored content provides the purpose of links through link text alone or through programmatic context.
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.5 (Web)
- 10.2.4.5 (Non-web document) – Does not apply
- 11.2.4.5 (Open Functionality Software) – Does not apply
- 11.2.4.5 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: This criterion does not apply to non-web software.
Authored Content (HTML): Authors can provide more than one way to locate a page in a set of pages, such as Search and navigation.
Authored Content (PDF): This criterion does not apply to non-web documents.
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.6 (Web)
- 10.2.4.6 (Non-web document)
- 11.2.4.6 (Open Functionality Software)
- 11.2.4.6 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Headings and labels are descriptive.
Authored Content (HTML): Authors can ensure that content meets this criterion.
Authored Content (PDF): Authors can ensure that content meets this criterion.
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.7 (Web)
- 10.2.4.7 (Non-web document)
- 11.2.4.7 (Open Functionality Software)
- 11.2.4.7 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
In the Welcome screen, two elements in the tab sequence lack a visible focus indicator.
Authored Content (HTML): Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Some off-screen inactive navigation elements receive keyboard focus.
Authored Content (PDF): 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.
2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.1 (Web)
- 10.2.5.1 (Non-web document)
- 11.2.5.1 (Open Functionality Software)
- 11.2.5.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: 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.
Authored Content (PDF): Authored content does not rely on multipoint or path-based gestures.
2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.2 (Web)
- 10.2.5.2 (Non-web document)
- 11.2.5.2 (Open Functionality Software)
- 11.2.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Product functions that use a single pointer are completed when the user releases the pointer.
Authored Content (HTML): Authored content functions that use a single pointer are completed when the user releases the pointer.
Authored Content (PDF): Authored content functions that use a single pointer are completed when the user releases the pointer.
2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.3 (Web)
- 10.2.5.3 (Non-web document)
- 11.2.5.3 (Open Functionality Software)
- 11.2.5.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The accessible names of controls contain the text of their visible labels.
Authored Content (HTML): The accessible names of controls contain the text of their visible labels.
Authored Content (PDF): The accessible names of controls contain the text of their visible labels.
2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.4 (Web)
- 10.2.5.4 (Non-web document)
- 11.2.5.4 (Open Functionality Software)
- 11.2.5.4 (Closed Software
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: 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.
Authored Content (PDF): Authored content does not have functionality operated by device motion or user motion.
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.1.1 (Web)
- 10.3.1.1 (Non-web document)
- 11.3.1.1.1 (Open Functionality Software)
- 11.3.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Does Not Support
Authored Content (PDF): Does Not Support
Software: The language is programmatically determinable within the product. The language of the product is set based on the version installed by the user.
Authored Content (HTML): The product does not allow authors to set the language of the page.
Authored Content (PDF): The product does not allow authors to set the language of the document.
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.1.2 (Web)
- 10.3.1.2 (Non-web document)
- 11.3.1.2 (Open Functionality Software) – Does not apply
- 11.3.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Content is only presented in one language at a time.
Authored Content (HTML): Authored content is only presented in one language at a time.
Authored Content (PDF): Authored content is only presented in one language at a time.
Guideline Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.1 (Web)
- 10.3.2.1 (Non-web document)
- 11.3.2.1 (Open Functionality Software)
- 11.3.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most components do not initiate a change of context when focused. Exceptions include:
In the Character Catalog pod, a focus change occurs when the user focuses items in the list.
Authored Content (HTML): Authored content components do not initiate a change of context when focused.
Authored Content (PDF): Authored content components do not initiate a change of context when focused.
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.2 (Web)
- 10.3.2.2 (Non-web document)
- 11.3.2.2 (Open Functionality Software)
- 11.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Changes of context do not occur automatically on user input.
Authored Content (HTML): Changes of context do not occur automatically on user input.
Authored Content (PDF): Authored content does not contain user input controls.
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.3 (Web)
- 10.3.2.3 (Non-web document) – Does not apply
- 11.3.2.3 (Open Functionality Software) – Does not apply
- 11.3.2.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: This criterion does not apply to non-web software.
Authored Content (HTML): Navigational mechanisms are repeated in the same relative order in a set of pages.
Authored Content (PDF): This criterion does not apply to non-web documents.
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.4 (Web)
- 10.3.2.4 (Non-web document) – Does not apply
- 11.3.2.4 (Open Functionality Software) – Does not apply
- 11.3.2.4 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: This criterion does not apply to non-web software.
Authored Content (HTML): Authors can ensure that components with the same functionality are identified consistently in a set of pages.
Authored Content (PDF): This criterion does not apply to non-web documents.
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.1 (Web)
- 10.3.3.1 (Non-web document)
- 11.3.3.1.1 (Open Functionality Software)
- 11.3.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most input errors are identified and described to the users in text. Exceptions include:
In the Create CMS Connection dialog, the error message for an invalid server format does not indicate which field is in error.
Authored Content (HTML): Authored content does not detect input errors.
Authored Content (PDF): Authored content does not detect input errors.
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.2 (Web)
- 10.3.3.2 (Non-web document)
- 11.3.3.2 (Open Functionality Software)
- 11.3.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Labels are provided for most input fields. Exceptions include:
In the Create CMS Connection dialog, labels and instructions do not indicate which fields are required.
Authored Content (HTML): Labels or instructions are provided when content requires user input.
Authored Content (PDF): Authored content does not contain user input controls that would require labels or instructions.
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.3 (Web)
- 10.3.3.3 (Non-web document)
- 11.3.3.3 (Open Functionality Software)
- 11.3.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Where input errors are automatically detected, suggestions for correction are provided to the user in most cases. Exceptions include:
In the Publish dialog, an error message for Output Location does not say which characters are allowed or disallowed.
In the Code Builder dialog, an error message for Telephone does not say what format is required.
Authored Content (HTML): Authored content does not detect input errors that are displayed to users.
Authored Content (PDF): Authored content does not detect input errors that are displayed to users.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.4 (Web)
- 10.3.3.4 (Non-web document)
- 11.3.3.4 (Open Functionality Software)
- 11.3.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: 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.
Authored Content (PDF): 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.
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria
- 9.4.1.1 (Web)
- 10.4.1.1 (Non-web document)
- 11.4.1.1.1 (Open Functionality Software)
- 11.4.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Embedded markup, such as Welcome screen content, meets parsing requirements.
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.
Authored Content (PDF): The authored content is not implemented using markup languages.
4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria
- 9.4.1.2 (Web)
- 10.4.1.2 (Non-web document)
- 11.4.1.2.1 (Open Functionality Software)
- 11.4.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: Does Not Support
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product’s main menus convey name, role, and state information to assistive technology. However, user interface components in most product functions lack programmatic name, role, state, or value information. Examples include:
In most pods and dialogs, form input fields lack accessible names.
In the document editor, the accessible text values of some content, such as headings, equations, and line endings, do not match the visual presentation of the content.
In the document editor, non-text objects, such as images and frames, lack accessible role and property information.
In the document window, status bar controls lack accessible names and roles.
The Workspace menu lacks an accessible name and role.
In the Standard Templates window, navigation controls lack accessible name, role, and state information.
Authored Content (HTML): Authors can ensure that most content meets this criterion. Exceptions include:
Page tabs do not provide their selected state.
Some frames lack meaningful titles.
Some Search input fields lack programmatic labels.
Some parts of the navigation controls are inappropriately identified as dialogs.
Authored Content (PDF): Authors can ensure that most content meets this criterion. Exceptions include:
Embedded video elements are not tagged as media.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document) – Does not apply
- 11.4.1.3 (Open Functionality Software) – Does not apply
- 11.4.1.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: This criterion does not apply to non-web software.
Authored Content (HTML): Authored content does not include status messages.
Authored Content (PDF): This criterion does not apply to non-web documents.
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.
Software: Does Not Support
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: Most functions of the product are not usable without vision. Examples include:
As noted in 1.1.1 Non-text Content, some images lack a text alternative.
As noted in 1.3.1 Info and Relationships, some structure and relationship information is provided visually, but is not provided to assistive technology.
As noted in 1.3.2 Meaningful Sequence, in some cases text in the document editor is announced out of sequence.
As noted in 2.1.1 Keyboard, some product functions are not keyboard accessible.
As noted in 4.1.2 Name, Role, Value, user interface components in most product functions lack programmatic name, role, state, or value information.
Authored Content (HTML): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, some image buttons in the navigation controls lack text alternatives.
As noted in 1.3.1 Info and Relationships, some visual structure information is not provided through element semantics.
As noted in 2.1.1 Keyboard, some controls are not keyboard accessible.
As noted in 3.1.1 Language of Page, the language of the page is not set.
As noted in 4.1.2 Name, Role, Value, some user interface components lack name or state information.
Authored Content (PDF): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships, most visual structure information is not provided through element semantics.
As noted in 3.1.1 Language of Page, the language of the document is not set.
As noted in 4.1.2 Name, Role, Value, some user interface components lack name or state information.
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.
As noted in 1.4.4 Resize Text, some content is unavailable when text is resized using operating system display scaling.
As noted in 503.2 User Preferences, some elements do not adapt to system settings for color and contrast.
As noted in 503.2 User Preferences, system settings for mouse pointer size and insertion point cursor size are not honored in the document editor.
Authored Content (HTML): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.4.5 Images of Text, when text is grouped with a non-text object, it is published as an image of text.
Authored Content (PDF): Authors can create content which is functional for users with limited vision.
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color, some tab selections are indicated solely by a color difference.
Authored Content (HTML): Authors can create content which is functional for users without perception of color.
Authored Content (PDF): Authors can create content which is functional for users without perception of color.
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product does not require the use of hearing.
Authored Content (HTML): Authors can create content in which most functions can be used without hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Authored Content (PDF): Authors can create content in which most functions can be used without hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product does not require the use of hearing.
Authored Content (HTML): Authors can create content in which most functions can be used with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Authored Content (PDF): Authors can create content in which most functions can be used with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not require the use of speech.
Authored Content (HTML): Authors can create content which is functional for users without speech.
Authored Content (PDF): Authors can create content which is functional for users without speech.
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, some product functions are not keyboard accessible.
As noted in 2.4.7 Focus Visible, two elements in the Welcome screen lack a visible focus indicator.
As noted in 3.2.1 On Focus, a component in the Character Catalog pod initiates a change of context when focused.
Authored Content (HTML): Authors can create content in which most functions can be used with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, some controls are not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, a bypass mechanism is not provided for users without assistive technology.
As noted in 2.4.3 Focus Order, some components do not receive focus in a meaningful order.
As noted in 2.4.7 Focus Visible, some off-screen inactive navigation elements receive keyboard focus.
Authored Content (PDF): Authors can create content which is functional with limited manipulation.
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product is functional with limited reach and strength.
Authored Content (HTML): Authors can create content which is functional with limited reach and strength.
Authored Content (PDF): Authors can create content which is functional with limited reach and strength.
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable 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 descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 3.3.1 Error Identification, an error message in the Create CMS Connection dialog does not indicate which field is in error.
As noted in 3.3.2 Labels or Instructions, required fields are not indicated in the Create CMS Connection dialog.
As noted in 3.3.3 Error Suggestion, some error messages do not provide suggestions for correction.
Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities.
Authored Content (PDF): 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:
The product exposes the values of most input controls to assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value, some user-entered content objects in the document editor are not exposed to assistive technology.
The product exposes most hierarchical parent-child relationships to assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships, radio buttons in the Spell Checker dialog lack programmatic grouping.
The product exposes most text content and text values to assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships, XML hierarchy text is not exposed to assistive technology.
As noted in 1.3.1 Info and Relationships, text in the Standard Templates window is not exposed to assistive technology.
As noted in 4.1.2 Name, Role, Value, some user-entered text in the document editor is exposed incorrectly to assistive technology.
Most controls in the product expose programmatic role information, which conveys available actions to assistive technology. As noted in 4.1.2 Name, Role, Value, exceptions include:
The Workspace menu lacks an accessible role.
Controls in the Standard Templates window lack accessible roles.
The product allows assistive technology to perform most actions on objects. As noted in 2.1.1 Keyboard, exceptions include:
Some functions of the Welcome screen.
Functions of the Drawing toolbar.
Insertion of symbols from the Equations pod.
The workspace switcher function.
The product exposes most focus, text insertion point, and selection attributes to assistive technology. Exceptions include:
The selection attribute of some objects in documents, such as frames and images, are not exposed to assistive technology.
The product allows assistive technology to move focus and modify most selection attributes. Exceptions include:
The product does not allow assistive technology to select some objects in documents, such as frames and images.
In most product functions, the product adapts to platform settings for color, contrast, font size, and focus cursor. Exceptions include:
In the application bar, top-level menu items do not adapt to system settings for color and contrast.
In pods and dialogs, field labels and tab list items do not adapt to system settings for color and contrast.
Some text, such as prompts for XML values in the document editor, does not adapt to system settings for both foreground and background color, causing a reduction in contrast.
In the document editor, system settings for mouse pointer size and insertion point cursor size are not honored.
When publishing to HTML or PDF, the product preserves most information for accessibility that is available in source documents. Exceptions include:
As noted in 1.3.1 Info and Relationships, some visual structure and relationship information is not provided through element semantics.
The product does not preserve captions and audio description data when publishing a document with imported video.
When publishing to a PDF 1.7 file, the product does not enable PDF/UA-1 conformance for most content. Examples include:
Most path objects and text objects are not tagged.
Link elements lack alternative text values.
Figure elements lack bounding boxes.
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.
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.
Software: Does Not Support
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: Most functions of the product are not usable without vision. Examples include:
As noted in 1.1.1 Non-text Content, some images lack a text alternative.
As noted in 1.3.1 Info and Relationships, some structure and relationship information is provided visually, but is not provided to assistive technology.
As noted in 1.3.2 Meaningful Sequence, in some cases text in the document editor is announced out of sequence.
As noted in 2.1.1 Keyboard, some product functions are not keyboard accessible.
As noted in 4.1.2 Name, Role, Value, user interface components in most product functions lack programmatic name, role, state, or value information.
Authored Content (HTML): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, some image buttons in the navigation controls lack text alternatives.
As noted in 1.3.1 Info and Relationships, some visual structure information is not provided through element semantics.
As noted in 2.1.1 Keyboard, some controls are not keyboard accessible.
As noted in 3.1.1 Language of Page, the language of the page is not set.
As noted in 4.1.2 Name, Role, Value, some user interface components lack name or state information.
Authored Content (PDF): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships, most visual structure information is not provided through element semantics.
As noted in 3.1.1 Language of Page, the language of the document is not set.
As noted in 4.1.2 Name, Role, Value, some user interface components lack name or state information.
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.
As noted in 1.4.4 Resize Text, some content is unavailable when text is resized using operating system display scaling.
As noted in 1.4.10 Reflow, at the required width of 320 CSS pixels, content or functionality extends off-screen in most product functions and cannot be scrolled into view.
As noted in 1.4.11 Non-text Contrast, some meaningful non-text content elements do not have sufficient contrast.
As noted in 11.7 User Preferences, some elements do not adapt to system settings for color and contrast and system settings for mouse pointer size and insertion point cursor size are not honored in the document editor.
Authored Content (HTML): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.4.5 Images of Text, when text is grouped with a non-text object, it is published as an image of text.
As noted in 1.4.11 Non-text Contrast, some controls in Search and navigation do not have sufficient contrast.
Authored Content (PDF): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.4.10 Reflow, at the required width of 320 CSS pixels footnote markers do not appear in superscript position.
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color, some tab selections are indicated solely by a color difference.
Authored Content (HTML): Authors can create content which is functional for users without perception of color.
Authored Content (PDF): Authors can create content which is functional for users without perception of color.
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product does not require the use of hearing.
Authored Content (HTML): Authors can create content in which most functions can be used without hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Authored Content (PDF): Authors can create content in which most functions can be used without hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Software: Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Partially Supports
Software: The product does not require the use of hearing.
Authored Content (HTML): Authors can create content in which most functions can be used with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Authored Content (PDF): Authors can create content in which most functions can be used with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded), closed captions are not preserved in embedded video.
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not require the use of speech.
Authored Content (HTML): Authors can create content which is functional for users without speech.
Authored Content (PDF): Authors can create content which is functional for users without speech.
Software: Partially Supports
Authored Content (HTML): Partially Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable with limited manipulation or strength. Exceptions include:
As noted in 2.1.1 Keyboard, some product functions are not keyboard accessible.
As noted in 2.4.7 Focus Visible, two elements in the Welcome screen lack a visible focus indicator.
As noted in 3.2.1 On Focus, a component in the Character Catalog pod initiates a change of context when focused.
Authored Content (HTML): Authors can create content in which most functions can be used with limited manipulation or strength. Exceptions include:
As noted in 2.1.1 Keyboard, some controls are not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, a bypass mechanism is not provided for users without assistive technology.
As noted in 2.4.3 Focus Order, some components do not receive focus in a meaningful order.
As noted in 2.4.7 Focus Visible, some off-screen inactive navigation elements receive keyboard focus.
Authored Content (PDF): Authors can create content which is functional with limited manipulation or strength.
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product is functional with limited reach.
Authored Content (HTML): Authors can create content which is functional with limited reach.
Authored Content (PDF): Authors can create content which is functional with limited reach.
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: As noted in 2.3.1 Three Flashes or Below Threshold, 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.
Authored Content (PDF): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.
Software: Partially Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable 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 descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 3.3.1 Error Identification, an error message in the Create CMS Connection dialog does not indicate which field is in error.
As noted in 3.3.2 Labels or Instructions, required fields are not indicated in the Create CMS Connection dialog.
As noted in 3.3.3 Error Suggestion, some error messages do not provide suggestions for correction.
Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities.
Authored Content (PDF): Authors can create content which is functional for users with limited language, cognitive, and learning abilities.
Software: Supports
Authored Content (HTML): Supports
Authored Content (PDF): Supports
Software: The product does not ask for or display legal, financial, or personal data.
Authored Content (HTML): Authored content does not contain legal or financial data and does not modify user-controllable data.
Authored Content (PDF): Authored content does not contain legal or financial data and does not modify user-controllable data.
Chapter 5: Generic Requirements
Notes:
When publishing to HTML or PDF, the product preserves most information for accessibility that is available in source documents. Exceptions include:
As noted in 1.3.1 Info and Relationships, some visual structure and relationship information is not provided through element semantics.
The product does not preserve captions and audio description data when publishing a document with imported video.
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:
Some graphical on-screen buttons do not have an accessible name.
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.x section)
Notes:
Chapter 10: Non-web Documents
Notes:
Chapter 11: Software
Notes:
The product exposes the values of most input controls to assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value, some user-entered content objects in the document editor are not exposed to assistive technology.
The product exposes most hierarchical parent-child relationships to assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships, radio buttons in the Spell Checker dialog lack programmatic grouping.
The product exposes most text content and text values to assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships, XML hierarchy text is not exposed to assistive technology.
As noted in 1.3.1 Info and Relationships, text in the Standard Templates window is not exposed to assistive technology.
As noted in 4.1.2 Name, Role, Value, some user-entered text in the document editor is exposed incorrectly to assistive technology.
Most controls in the product expose programmatic role information, which conveys available actions to assistive technology. As noted in 4.1.2 Name, Role, Value, exceptions include:
The Workspace menu lacks an accessible role.
Controls in the Standard Templates window lack accessible roles.
The product allows assistive technology to perform most actions on objects. As noted in 2.1.1 Keyboard, exceptions include:
Some functions of the Welcome screen.
Functions of the Drawing toolbar.
Insertion of symbols from the Equations pod.
The workspace switcher function.
The product exposes most focus, text insertion point, and selection attributes to assistive technology. Exceptions include:
The selection attribute of some objects in documents, such as frames and images, are not exposed to assistive technology.
The product allows assistive technology to move focus and modify most selection attributes. Exceptions include:
The product does not allow assistive technology to select some objects in documents, such as frames and images.
In most product functions, the product adapts to platform settings for color, contrast, font size, and focus cursor. Exceptions include:
In the application bar, top-level menu items do not adapt to system settings for color and contrast.
In pods and dialogs, field labels and tab list items do not adapt to system settings for color and contrast.
Some text, such as prompts for XML values in the document editor, do not adapt to system settings for both foreground and background color, causing a reduction in contrast.
In the document editor, system settings for mouse pointer size and insertion point cursor size are not honored.
When publishing to HTML or PDF, the product preserves most information for accessibility that is available in source documents. Exceptions include:
As noted in 1.3.1 Info and Relationships, some visual structure and relationship information is not provided through element semantics.
The product does not preserve captions and audio description data when publishing a document with imported video.
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.
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)