Adobe Accessibility Conformance Report

1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria

• 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: The product provides sufficient text alternatives for most instances of application.

Exception includes:

• Some informative images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information conveyed by the image. This occurs on the following pages; PDF Template Panel; Authoring Workspace; Starter Screen.

Web: The product provides sufficient text alternatives for most instances of application.

Exception includes:

• Some informative images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information conveyed by the image. This occurs on the following pages: Frameless: Main Page Content; Responsive: Main Page Content.

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 (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: The product does not contain prerecorded audio-only or video-only media.

Web: The product does not contain prerecorded audio-only or 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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not contain prerecorded synchronized media

Web: The product does not contain prerecorded synchronized media.

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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not contain prerecorded video content that would require audio description or a media alternative.

Web: The product does not contain prerecorded video content that would require audio description or a media alternative.

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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not contain live synchronized media.

Web: The product 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: The product does not contain prerecorded video content that would require audio description.

Web: The product does not contain prerecorded video content that would require audio description.

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: Does Not Support

Web: Partially Supports

Software: Some structure and relationship information are provided through semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text.

Examples include:

• Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Starter Screen.
• A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following page: Landing Page - Review.
• A block of text is marked up as a heading but is not a heading, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Responsive Template; Set Application Preferences; Right panel; Landing Page - Review; Landing Page - Output.
• Text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Translation Profiles; Collaborate; Set Application Preferences; PDF Template Panel; Right panel; Starter Screen; Landing Page - Review; Landing Page - Output; Hi-Tech Template; Publish Profiles; Landing Page - Author View; Topic List View; Create Project.
• Data is arranged visually like a data table, but the programmatic table header markup is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the table headers and their related data. This occurs on the following pages: Landing Page - Review; Topic List View.
• One or more data cells is incorrectly marked up as a header cell in a table, so the table structure and the header/data relationship between the cell(s) and other cells in the table will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Landing Page - Review; Topic List View
• A set of radio buttons is not programmatically grouped, so the group label for the set of radio buttons will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual radio buttons. This occurs on the following page: Hi-Tech Template; Preset.
• A set of checkboxes is not programmatically grouped, so the group label for the set of checkboxes will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual checkboxes. This occurs on the following page: Hi-Tech Template.

Web: Most visual structure and relationship information is provided through element semantics | object information or in text.

Exceptions include:

• Data is arranged visually like a data table, but the programmatic table header markup is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the table headers and their related data. This occurs on the following pages: Responsive: Main Page Content Tables; Frameless: Main Page Content Tables.
• Text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Frameless: Right Sidebar.

1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria

• 9.1.3.2 (Web)
• 10.1.3.1 (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

Web: Partially Supports

Software: The product presents most content in a meaningful sequence.

Exceptions include:

• Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following pages: Landing Page - Review; Topic List View.
• A hidden or empty interactive element receives screen reader focus, so people who are blind and/or use a screen reader will navigate to an element that is not intended to be part of the reading order on the page or has no content/functionality. This occurs on the following pages: Hi-Tech Template; Landing Page - Author View.

Web: The product presents most content in a meaningful sequence.

Exception includes:

• Screen reader focus does not follow the visual focus order or does not move to the intended target, so the reading order for people who are blind and/or use a screen reader may not follow the visual organization of the page. This occurs on the following page: Frameless: Right Sidebar.

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: Most instructions do not rely solely on sensory characteristics.

Exception includes:

• Some instructions require the ability to see shape, color, size, visual location, or orientation, so they will be difficult or impossible to understand for people who are blind or have low vision. This occurs on the following page: Authoring Workspace.

Web: Instructions do not rely solely on sensory characteristics.

1.3.4 Orientation (WCAG 2.1)
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

Web: Supports

Software: Content does not restrict its view and operation to a single display orientation.

Web: Content does not restrict its view and operation to a single display orientation.

1.3.5 Identify Input Purpose (WCAG 2.1)
Also applies to:
EN 301 549 Criteria

• 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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product’s technology does not have support for programmatic identification of input purpose.

Web: The product does not contain input fields that collect information about the user.

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

Web: Supports

Software: Most functions of the product do not convey information through color alone.

Exception includes:

• Color is used as the only method to convey the state (such as "checked," "pressed," or "selected”) of a control, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following pages: Starter Screen; Frameless Template; Landing Page - Output.

Web: The product does not convey information through color alone.

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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not contain audio that plays automatically.

Web: The product 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

Web: Partially Supports

Software: Most text meets minimum contrast requirements.

Exceptions include:

• The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: Translation Profiles; Collaborate; Set Application Preferences.
• The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Standard Toolbar; Landing Page - Author View.
• The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs on the following pages: Standard Toolbar; Landing Page - Author View.
• The color contrast ratio between text placed over an image and that image is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page: Starter Screen.

Web: Most text meets minimum contrast requirements.

Exceptions include:

• The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs on the following pages: Frameless: Header.
• The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Frameless: Main Page Content; Responsive: Main Page Content; Responsive: Left Navigation

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: Supports

Web: Supports

Software: The product allows operating system display scaling 200% to resize text up to 200 percent without loss of content or functionality.

Web: The product allows operating system display scaling 200% to resize text 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

Web: Partially Supports

Software: The product uses text instead of images of text, except for branding elements that are considered essential.

Web: The product uses text instead of images of text most of the cases, except for branding elements that are considered essential.

Exception includes:

• Text on the page is text embedded in an image instead of actual text. An image of text is difficult to zoom or otherwise modify, so people who have low vision and need to enlarge text to read it may not be able to read the text. People with other disabilities that need to otherwise modify text to read it also may not be able to read this text. This occurs on the following pages: Frameless: Main Page Content; Responsive: Main Page Content.

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

Web: Supports

Software: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. Loss of information or functionality occurs and content which does not require two-dimensional layout for meaning relies on scrolling in two dimensions.

Example includes:

• When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs throughout the application.

Web: At the required width of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions.

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: Does Not Support

Web: Partially Supports

Software: Most meaningful non-text content elements (active user component and graphics) does not have sufficient contrast.

Examples include:

• The visual boundary of an interactive element (like a radio button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the boundaries of the interactive element. This occurs on the following pages: Responsive Template; Translation Profiles; Standard Toolbar; Collaborate; Set Application Preferences; PDF Template Panel; Right panel; Frameless Template; Landing Page - Review; Hi-Tech Template; Preset; Create Project.
• The indicator for the state of an interactive element (like a checkbox or radio button) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the state of the interactive element. This occurs on the following page: Right panel.
• The focus indicator of an interactive element (like a button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when the interactive element is receiving focus. This occurs on the following pages: Landing Page - Author View; Topic List View.

Web: Most meaningful non-text content elements have sufficient contrast.

Exceptions include:

• The visual boundary of an interactive element (like a radio button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the boundaries of the interactive element. This occurs on the following page: Responsive: Left Navigation.
• The focus indicator of an interactive element (like a button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when the interactive element is receiving focus. This occurs on the following pages: Responsive: Left Navigation; Frameless: Header.
• The indicator for the state of an interactive element (like a checkbox or radio button) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the state of the interactive element. This occurs on the following page: Responsive: Left Navigation.

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 (Not Applicable)

Web: Supports

Software: The product is not implemented using markup languages.

Web: The product supports the required text style properties without loss of content or functionality.

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

Web: Supports

Software: When additional content appears on hover, becomes hidden when the mouse pointer moves over it:

Exception includes:

Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on the following pages: Translation Profiles; Publish Profiles.

Web: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion.

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

Web: Supports

Software: Most product functionality can be operated through a keyboard interface.

Exceptions include:

• A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following pages: Responsive Template; Translation Profiles; Starter Screen; Frameless Template; Landing Page - Review; Landing Page - Output; Hi-Tech Template; Preset; Publish Profiles; Landing Page - Author View; Topic List View.

Web: Product 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

Web: Supports

Software: The product does not include keyboard traps.

Web: The product does not include keyboard traps.

2.1.4 Character Key Shortcuts (WCAG 2.1)
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

Web: Supports

Software: The product provides character key shortcuts. it is only active when the relevant user interface component is in focus.

Web: The product provides character key shortcuts. it is only active when the relevant user interface component is in focus.

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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not include time limits.

Web: The product 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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not include elements which move, blink, scroll, or auto-update.

Web: The product does not include elements which move, blink, scroll, or auto-update.

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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not contain flashing content.

Web: The product does not contain flashing content.

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 software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Software: Supports (Not Applicable)

Web: Supports

Software: This criterion does not apply to non-web software.

Web: The product provides mechanism to bypass repeated blocks

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: Supports

Web: Supports

Software: The title of the software describes its purpose.

Web: The title of the software describes its purpose.

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: Partially Supports

Web: Partially Supports

Software: Most components receive focus in a meaningful order.

Exceptions include:

• Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following pages: Hi-Tech Template; Landing Page - Author View.
• Keyboard focus is lost or misplaced as a result of user interaction or content update or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following pages: Standard Toolbar; Right panel; Starter Screen.
• When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following pages: Set Application Preferences; PDF Template Panel.

Web: Most components receive focus in a meaningful order

Exception includes:

• Keyboard focus is lost or misplaced as a result of user interaction or content update or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following page: Frameless: Right Sidebar.

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

Web: 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.

Web: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link.

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 (Not Applicable)

Web: Supports

Software: This criterion does not apply to non-web software.

Web: Multiple ways are available to find other pages on the site.

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: Partially Supports

Web: Partially Supports

Software: Most of the headings and labels are descriptive.

Exceptions include:

• A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Translation Profiles; Collaborate; Set Application Preferences; Right panel; Landing Page - Review; Hi-Tech Template; Preset; Publish Profiles.
• Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Translation Profiles; Set Application Preferences.

Web: Most of the headings and labels are descriptive.

Exception includes:

• A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Responsive: Custom Buttons; Responsive: Left Navigation.

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

Web: Partially Supports

Software: Most focusable elements have a visible keyboard focus indicator.

Exceptions include:

• An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Responsive Template; Frameless Template; Landing Page - Review; Hi-Tech Template; Preset; Topic List View.

Web: Most focusable elements have a visible keyboard focus indicator.

Exception includes:

• An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following page: Responsive: Left Navigation.

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

Web: Supports

Software: All functionality that can be operated with a pointer can be operated with single-point actions.

Web: All functionality that can be operated with a pointer can be operated with single-point actions.

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

Web: Supports

Software: Product functions that use a single pointer are completed when the user releases the pointer.

Web: Product 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: Partially Supports

Web: Supports

Software: In most product functions, accessible names of controls contain the text of their visible labels.

Exceptions include:

• The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Translation Profiles; Collaborate; Set Application Preferences; Landing Page - Review; Hi-Tech Template; Preset; Publish Profiles.
• An interactive element (such as a link, button, or form input) does not have an accessible name because its visible label is not programmatically associated with the element, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Responsive Template; Translation Profiles; Collaborate; Set Application Preferences; Right panel; Hi-Tech Template; Preset.

Web: 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 (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not have functionality operated by device motion or user motion.

Web: The product does not have functionality operated by device motion or user motion.

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

Web: Supports

Software: Changes of language for passages or phrases can be programmatically determined.

Web: Changes of language for passages or phrases can be programmatically determined.

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

Web: Supports

Software: Changes of language for passages or phrases can be programmatically determined.

Web: Changes of language for passages or phrases can be programmatically determined.

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

Web: Supports

Software: Most components do not initiate a change of context when focused.

Exceptions include:

Web: 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

Web: Supports

Software: Changes of context do not occur automatically on user input.

Web: Changes of context do not occur automatically on user input.

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 (Not Applicable)

Web: Supports

Software: This criterion does not apply to non-web software.

Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order.

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 (Not Applicable)

Web: Supports

Software: This criterion does not apply to non-web software.

Web: Components with the same functionality are identified consistently.

3.3.1 Error Identification (Level A)
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: Support

Web: Supports

Software: Where input errors are automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error.

Web: Where input errors are automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error.

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

Web: Partially Supports

Software: Labels are provided for most input fields.

Exceptions include:

• The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Translation Profiles; Set Application Preferences.
• The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Translation Profiles; Landing Page - Review; Publish Profiles; Topic List View.

Web: Labels are provided for most input fields.

Exception includes:

• The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Responsive: Left Navigation; Frameless: Left Sidebar.

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: Support

Web: Supports

Software: Where input errors are automatically detected, suggestions are provided in text for correcting the input in a timely and accessible manner before the data is submitted to the server

Web: Where input errors are automatically detected, suggestions are provided in text for correcting the input in a timely and accessible manner before the data is submitted to the server.

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

Web: Supports

Software: The product does not process legal commitments or financial transactions.

Web: The product does not process legal commitments or financial transactions.

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) – 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

Web: Supports

Software: The product is not implemented using markup languages.

Web: Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique.

4.1.2 Name, Role, Value (Level A)
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

Web: Partially Supports

Software: User interface components in most product functions do not provide programmatic ‘name, role, state, or value’ information.

Examples include:

• A custom checkbox element does not have a programmatic role and/or its current state (checked or not checked) is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be aware that the element is a checkbox or if the checkbox is checked. This occurs on the following page: Topic List View.
• For an element that allows a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the element, the options available, and whether the element or an option is currently checked. This occurs on the following pages: Standard Toolbar; Right panel.
• A control has an incorrect programmatic role, so the role (like "button" or "link") conveyed to screen readers and other assistive technologies is incorrect and misrepresents the control's function to people who use those technologies. This occurs on the following pages: Standard Toolbar; Landing Page - Review.
• A control has an incorrect programmatic state, so the control's state (like "checked"/"unchecked" or "expanded"/"collapsed") conveyed to screen readers and other assistive technologies is incorrect and misrepresents the control's state and functionality to people who use those technologies. This occurs on the following page: Landing Page – Review.
• A control (such as a button or link) does not have a programmatic name, so its name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Responsive Template; Translation Profiles; Standard Toolbar; Collaborate; Set Application Preferences; Right panel; Hi-Tech Template; Preset.
• A control (such as a button or link) does not have a programmatic role, so its role (like "button" or "link") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Landing Page - Review; Topic List View.
• A control (such as a button or link) does not have a programmatic name and role, so its name and role are not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Responsive Template; Frameless Template; Landing Page - Review; Hi-Tech Template; Preset; Publish Profiles; Topic List View.
• The programmatic state of an element that reveals or hides content ("expanded" or “collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of the element or the state will be misrepresented. This occurs on the following pages: Standard Toolbar; Starter Screen; Landing Page - Review; Landing Page - Output.
• The content of a tooltip cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs on the following pages: Hi-Tech Template; Preset; Publish Profiles.
• An element that appears and functions like a tree view widget that presents a hierarchical list does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand name, purpose, structure, or content of the list or how to interact with it. This occurs on the following page: Hi-Tech Template.

Web: User interface components in some product functions do not provide programmatic name, role, state, or value information.

Exceptions include:

• An element that appears and functions like a Combobox does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Responsive: Left Navigation; Frameless: Left Sidebar; Responsive: Header.
• A control has an incorrect programmatic state, so the control's state (like "checked"/"unchecked" or "expanded"/"collapsed") conveyed to screen readers and other assistive technologies is incorrect and misrepresents the control's state and functionality to people who use those technologies. This occurs on the following page: Frameless: Right Sidebar.

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

Web: Partially Supports

Software: Status messages can be programmatically determined and presented by assistive technologies without receiving focus.

Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus.

Exception includes:

• A status message is not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status message or they may not hear it in a timely fashion. This occurs on the following pages: Responsive: Left Navigation; Frameless: Header.

302.1 Without Vision

And

4.2.1 Usage without vision

Software: Does Not Support

Web: Partially Supports

Software: Most functions of the product are not usable without vision.

Examples include:

• 1.1.1 Non-Text Content
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 1.3.3 Sensory Characteristics
• 1.4.1 Use of Color
• 2.1.1 Keyboard
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 4.1.2 Name, Role, Value
• 4.1.3 Status Messages

Web: Most functions of the product are usable without vision.

Exceptions include:

• 1.1.1 Non-Text Content
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 4.1.2 Name, Role, Value
• 4.1.3 Status Messages

302.2 With Limited Vision

and

4.2.2 Usage with limited vision

Software: Does Not Support

Web: Partially Supports

Software: Most functions of the product are not usable with limited vision.

Examples include:

• 1.1.1 Non-Text Content
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 1.3.3 Sensory Characteristics
• 1.4.1 Use of Color
• 1.4.3 Contrast (minimum)
• 1.4.5 Images of Text
• 1.4.10 Reflow
• 1.4.11 Non-Text Contrast
• 1.4.13 Content on Hover or Focus
• 2.1.1 Keyboard
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 3.3.2 Labels or Instructions
• 4.1.2 Name, Role, Value

Web: Most functions of the product are usable with limited vision.

Exceptions include:

• 1.1.1 Non-Text Content
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 1.4.3 Contrast (minimum)
• 1.4.5 Images of Text
• 1.4.11 Non-Text Contrast
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 3.3.2 Labels or Instructions
• 4.1.2 Name, Role, Value

302.3 Without Perception of Color

and

4.2.3 Usage without perception of color

Software: Partially Supports

Web: Partially Supports

Software: Most functions of the product are usable without perception of color.

Exceptions include:

• 1.4.1 Use of Color
• 1.4.3 Contrast (minimum)
• 1.4.11 Non-Text Contrast

Web: Most functions of the product are usable without perception of color.

Exceptions include:

• 1.4.3 Contrast (minimum)
• 1.4.11 Non-Text Contrast

302.4 Without Hearing

And

4.2.4 Usage without hearing

Software: Supports (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not require the use of hearing.

Web: The product does not require the use of hearing.

302.5 With Limited Hearing

And

4.2.5 Usage with limited hearing

Software: Supports (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not require the use of hearing.

Web: The product does not require the use of hearing.

302.6 Without Speech

and

4.2.6 Usage without vocal capability

Software: Supports (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not require the use of speech.

Web: The product does not require the use of speech.

Software: Does Not Support

Web: Partially Supports

Software: Most functions of the product are not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength.

Examples include:

• 2.1.1 Keyboard
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 4.1.2 Name, Role, Value

Web: Most functions of the product are usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength.

Exceptions include:

• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 4.1.2 Name, Role, Value

Software: Does Not Support

Web: Partially Supports

Software: Most functions of the product are not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength.

Examples include:

• 1.4.13 Content on Hover or Focus
• 2.1.1 Keyboard
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 2.5.3 Label in Name
• 4.1.2 Name, Role, Value

Web: Most functions of the product are usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength.

Exceptions include:

• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 4.1.2 Name, Role, Value

Software: Supports

Web: Supports

Software: The product is functional with limited reach and strength.

Web: The product is functional with limited reach and strength.

Software: Partially Supports

Web: Supports

Software: Most functions of the product are usable by people with limited reach.

Exceptions include:

• 1.4.13 Content on Hover or Focus
• 2.5.3 Label in Name

Web: All the functions of the product are usable by people with limited reach.

Software: Supports (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not contain flashing content.

Web: The product does not contain flashing content.

302.9 With Limited Language, Cognitive, and Learning Abilities

and

4.2.10 Usage with limited cognition

Software: Does Not Support

Web: Partially Supports

Software: Most functions of the product are not usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology.

Examples include:

• 1.1.1 Non-Text Content
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 1.3.3 Sensory Characteristics
• 1.4.1 Use of Color
• 1.4.5 Images of Text
• 1.4.10 Reflow
• 1.4.13 Content on Hover or Focus
• 2.1.1 Keyboard
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 2.5.3 Label in Name
• 3.3.2 Labels or Instructions
• 4.1.2 Name, Role, Value
• 4.1.3 Status Messages

Web: Most functions of the product are usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology.

Exceptions include:

• 1.1.1 Non-Text Content
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 1.4.5 Images of Text
• 2.4.3 Focus Order
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible
• 3.3.2 Labels or Instructions
• 4.1.2 Name, Role, Value
• 4.1.3 Status Messages

Software: Supports (Not Applicable)

Web: Supports (Not Applicable)

Software: The product does not ask for or display legal, financial, or personal data.

Web: The product does not ask for or display legal, financial, or personal data.

Templates in the product enable authors to create a range of content which partially conforms to WCAG 2.1 Levels A and AA.

Exceptions include:

• 1.1.1 Non-text Content
• 1.3.1 Info and Relationships
• 2.4.3 Focus Order

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.

Exception includes:

• 4.1.2 Name, Role, Value.

Most objects in the product do not expose name, role, state, boundary, or description information to assistive technology.

Example includes:

• 4.1.2 Name, Role, Value.

The product has data table but programmatically not determinable structure, relationships.

Example includes:

• 1.3.1 Info and Relationships.

The product UI exposes most label relationships to assistive technologies.

Exception includes:

• 4.1.2 Name, Role, Value.
• 1.3.1 Info and Relationships.

The product expose most hierarchical parent-child relationships to assistive technology.

Exceptions include:

• 1.3.1 Info and Relationships,
• 4.1.2 Name, Role, Value.

Most controls in the product expose programmatic role information, which conveys available actions to assistive technology.

Exception includes:

• 4.1.2 Name, Role, Value.

The product allows assistive technology to perform all available actions on objects.

Exception includes:

• 2.1.1 Keyboard.

The product exposes focus location, text insertion point, and object selection state for most user interface components.

Exception includes:

• 2.4.7 Focus Visible.

The product notifies assistive technology to most user interaction events.

Exception includes:

• 4.1.3 Status Messages.

The product allows assistive technology to modify most states and properties of controls.

Exception includes:

• 4.1.2 Name, Role, Value.

Templates in the product enable authors to create a range of content which partially conforms to WCAG 2.1 Levels A and AA.

Exceptions include:

• 1.1.1 Non-text Content
• 1.3.1 Info and Relationships
• 1.4.13 Content on Hover or Focus
• 2.4.3 Focus Order