Adobe Accessibility Conformance Report International Edition

Web: Partially Supports

Authored Content: Supports

Web: The product provides sufficient text alternatives for most instances of images and non-text content. Exceptions include:

Some 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 available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: List View; Edge Delivery Services; Edit demo - DA.

Authored Content: Authors can provide text alternatives for images and non-text content.

Web: Supports

Authored Content: Supports

Web: The product provides audio description for video-only media.

Authored Content: Authors can provide audio description for what would otherwise be video-only media

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain prerecorded synchronized media.

Authored Content: Authored content does not contain prerecorded synchronized media.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authored content does not contain video content that would require audio description or a media alternative.

Web: Partially Supports

Authored Content: Partially Supports

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

An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Preview.

Some content that is visually presented as multiple lists is not marked up as a list, so the presence and structure of each list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Right Bar Buttons; Edit demo - DA; Browse.

Some 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: Right Bar Buttons; Preview.

Some heading levels are out of order, 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: Native authoring (Project da.live); Edit demo - DA.

Content is arranged visually like a data table, but some visual tables are not programmatically marked up as tables, so each 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: List View.

A nested list is not marked up properly, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Edge Delivery Services.

A block quotation lacks semantic markup, so the quotation's context is only available visually. People who are blind and/or use a screen reader may not be aware that the text is a quotation. This occurs on the following page: Native authoring (Project da.live).

Some blocks of text are marked up as headings but are not headings, 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 page: List View; Native authoring (Project da.live).

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 page: Block-collection config - DA.

Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following pages: Right Bar Buttons; List View.

Data is arranged visually like a complex data table with multiple rows of column headers and/or columns of row headers, but there is no programmatic markup to associate the headers with any data. 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 page: Block-collection config - DA.

Authored Content: Authors can provide appropriate semantics, object information and textual equivalents for most visual structure and relationship information. Exceptions include:

Content is arranged visually like a data table, but some visual tables are not programmatically marked up as tables, so each 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: Search.

Some blocks of text are marked up as headings but are not headings, 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 page: Search

Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Search.

Web: Partially Supports

Authored Content: Supports

Web: 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 page: Native authoring (Project da.live).

Authored Content: The product allows authors to present content in a meaningful sequence.

Web: Supports

Authored Content: Supports

Web: Instructions do not rely solely on sensory characteristics.

Authored Content: Authors can ensure that content meets this criterion.

Web: Partially Supports

Authored Content: Supports

Web: Most functions of the product do not convey information through color alone. Exceptions include:

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 page: Block-collection config - DA.

Color is used as the only method to identify errors on some form fields, so the errors for those fields 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 page: New menu.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authored content does not contain audio that plays automatically.

Web: Partially Supports

Authored Content: Supports

Web: Most product functionality can be operated through a keyboard interface. Exceptions include:

Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs on the following pages: Block-collection config - DA; Edit demo - DA; Right Bar Buttons; New menu.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Does not Support

Web: The product does not include keyboard traps.

Authored Content: Authored content does include keyboard traps. Examples include:

There is a keyboard trap, so people who use a keyboard to navigate content will get stuck in one place on the page. This occurs on the following page: Sample Blocks - Video.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not provide character key shortcuts.

Authored Content: Authored content does not provide character key shortcuts.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not include time limits.

Authored Content: Authored content does not include time limits.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Playback control is a function of the user’s media player, not the authored content.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain flashing content.

Authored Content: Authors can ensure that content does not flash.

Web: Supports

Authored Content: Supports

Web: The product provides mechanism to bypass repeated blocks.

Authored Content: Authored content does not contain repeated blocks that would require a skip mechanism.

Web: Supports

Authored Content: Supports

Web: The titles of pages describe their purpose.

Authored Content: The product allows authors to customize the page title.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most components receive focus in a meaningful order. Exceptions include:

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

Keyboard focus or touch screen swiping goes to multiple elements that are 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 page: Native authoring (Project da.live).

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Keyboard focus or touch screen swiping goes to multiple elements that are 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 page: Sample Blocks – Video.

Web: Partially Supports

Authored Content: Partially Supports

Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. Exceptions include:

Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following pages: Native authoring (Project da.live); List View.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following page: Search.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not rely on multipoint or path-based gestures.

Authored Content: Authored content does not rely on multipoint or path-based gestures.

Web: Supports

Authored Content: Supports

Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.

Authored Content: Authors can ensure that content meets this criterion.

Web: Partially Supports

Authored Content: Partially Supports

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

Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following page: List View.

The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Edit demo - DA; Edge Delivery Services; List View; Block-collection config - DA.

Authored Content: Authors can ensure that the accessible names of controls contain the text of their visible labels. Exceptions include:

Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following page: Sample Blocks – Video.

The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following page: Search.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authored content does not have functionality operated by device motion or user motion.

Web: Supports

Authored Content: Supports

Web: The language is programmatically determinable within the product.

Authored Content: Authors can set the language of the page.

Web: Supports

Authored Content: Supports

Web: Components do not initiate a change of context when focused.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Supports

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

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Supports

Web: The product contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.

Authored Content: Authors can ensure that content meets this criterion.

Web: Partially Supports

Authored Content: Supports

Web: Most input errors are identified and described to the users in text. Exceptions include:

Errors for some form inputs (such as text input fields, radio buttons, select dropdowns, or checkboxes) are not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: New menu.

Authored Content: Authored content does not detect input errors that are displayed to users.

Web: Partially Supports

Authored Content: Partially Supports

Web: Labels are provided for most input fields. Exceptions include:

The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following pages: Block-collection config - DA; Edit demo - DA.

Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: New menu; History; List View.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following page: Search.

Web: Supports

Authored Content: Supports

Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Supports

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.

Authored Content: 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.

Web: Partially Supports

Authored Content: Partially Supports

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

Multiple form input elements do not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of each element and may not understand its purpose or how to interact with it. This occurs on the following pages: List View; Block-collection config - DA; Edit demo - DA.

Multiple buttons do not have a programmatic name, so each button's 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: List View; Edit demo - DA; Browse.

An iframe does not have a programmatic title that is 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 or content of the iframe without browsing its content. This occurs on the following page: Right Bar Buttons.

In a table that can be sorted by column, the sorted state (ascending or descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presented and whether that order is meaningful when interpreting the data. This occurs on the following page: List View.

Multiple elements do not have an attribute in their HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), 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: Block-collection config - DA; Edit demo - DA.

Multiple buttons do not have a programmatic role, so each button's role (usually button, but sometimes link or something else) 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: Edit demo - DA; Right Bar Buttons; New menu.

Multiple buttons do not have a programmatic role and name, so each button's role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") 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: Right Bar Buttons; Edit demo - DA.

For some elements that allow 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 each element, the options available, and whether the element or an option is currently checked. This occurs on the following pages: Edit demo - DA; Browse; Right Bar Buttons.

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: Edit demo - DA; Block-collection config - DA; List View; Edge Delivery Services; Browse; History.

An element that appears and functions like a set of tabs with their associated tab panels 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 element's name, purpose, content, structure, or current state or how to interact with the tabs and their associated content. This occurs on the following page: Block-collection config - DA.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Multiple form input elements do not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of each element and may not understand its purpose or how to interact with it. This occurs on the following page: Search

Multiple buttons do not have a programmatic name, so each button's 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 page: Search

In a table that can be sorted by column, the sorted state (ascending or descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presented and whether that order is meaningful when interpreting the data. This occurs on the following page: Search.

A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Sample Blocks - Video.

An element is missing or has an incorrect programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or content or how to interact with it. This occurs on the following page: Sample Blocks - Video.

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 page: Search.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain live synchronized media.

Authored Content: Authored content does not contain live synchronized media.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authored content does not contain video content that would require audio description.

Web: Supports

Authored Content: Supports

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

Authored Content: Authors can ensure that content does not restrict its view and operation to a single display orientation.

Web: Supports

Authored Content: Supports

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

Authored Content: Authors can ensure that content meets this criterion.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most text meets minimum contrast requirements. Exceptions include:

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: New menu; Edit demo - DA; Native authoring (Project da.live); Block-collection config - DA; Browse.

The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of each control. This occurs on the following pages: Browse; List View; Edit demo - DA.

The color contrast ratio between placeholder text in multiple inputs and each 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: Edit demo - DA; New menu.

Authored Content: Authors can ensure that most text meets contrast requirements. Exceptions include:

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 page: Search.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions include:

Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Right Bar Buttons; Edit demo - DA.

Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs on the following pages: Edit demo - DA; Edge Delivery Services; Browse; Native authoring (Project da.live).

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following page: Search.

Web: Partially Supports

Authored Content: Supports

Web: On most pages, when content can be presented visually using only text, an image of text is not used to present that text. Exceptions include:

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 page: Edge Delivery Services.

Authored Content: Authors can ensure that content meets this criterion.

Web: Partially Supports

Authored Content: Partially Supports

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

When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following pages: Edit demo - DA; Right Bar Buttons.

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 on the following pages: Edit demo - DA; Right Bar Buttons; Edge Delivery Services; Browse; List View.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following page: Search.

Web: Partially Supports

Authored Content: Partially Supports

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

The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following pages: List View; History.

The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs on the following pages: Edit demo - DA; Block-collection config - DA.

Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs on the following pages: Edge Delivery Services; List View; Edit demo - DA; Block-collection config - DA; History.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following page: Search; Sample Blocks – Video.

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 page: Sample Blocks - Video.

Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs on the following page: Search.

Web: Supports

Authored Content: Supports

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

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Partially Supports

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

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

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 page: Sample Blocks - Video.

Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on the following page: Sample Blocks - Video.

Web: Supports

Authored Content: Supports

Web: Users can locate web pages in the product.

Authored Content: Authors can provide more than one way to locate a page in a set of pages.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most headings and labels for form and interactive controls are informative. Exceptions include:

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: Edge Delivery Services; History; Block-collection config - DA; List View; Edit demo - DA.

Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs on the following pages: Block-collection config - DA; History.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

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: Sample Blocks - Video; Search.

Web: Partially Supports

Authored Content: Supports

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

Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Edge Delivery Services; New menu; Browse.

The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible, 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: Block-collection config - DA.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Supports

Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Supports

Web: All functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

Authored Content: Authors can ensure that content meets this criterion.

Web: Supports

Authored Content: Partially Supports

Web: The size of the target for each clickable control is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Multiple target hit areas do not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following pages: Search; Sample Blocks - Search.

Web: Supports

Authored Content: Supports

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

Authored Content: Authors can set the language for individual phrases within content.

Web: Supports

Authored Content: Supports

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

Authored Content: Navigational mechanisms are repeated in the same relative order in a set of pages.

Web: Supports

Authored Content: Supports

Web: Components with the same functionality are identified consistently.

Authored Content: Authors can ensure that components with the same functionality are identified consistently in a set of pages.

Web: Supports

Authored Content: Supports

Web: Where input errors are automatically detected suggestions for correction are provided to the user.

Authored Content: Authors can provide suggestions for correction of automatically detected input errors.

Web: Supports

Authored Content: Supports (Not Applicable)

Web: The product does not process legal commitments or financial transactions. When editing files, changes to user-controllable data are reversible or can be confirmed before finalizing.

Authored Content: Authored content does not contain legal or financial data and does not modify user-controllable data.

Web: Supports

Authored Content: Supports

Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the website.

Authored Content: Authors can ensure that content meets this criterion.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include:

Some status messages are 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 messages, or they may not hear them in a timely fashion. This occurs on the following pages: Native authoring (Project da.live); List View.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Some status messages are 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 messages, or they may not hear them in a timely fashion. This occurs on the following page: Search.

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 3.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content in which most functions can be used without vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 2.1.2 No Keyboard Trap

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.4 Resize text

As noted in 1.4.5 Images of Text

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content in which most functions can be used with limited vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.4 Resize text

As noted in 2.1.2 No Keyboard Trap

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 3.3.1 Error Identification

Authored Content: Authors can create content in which most functions can be used without perception of color. Exceptions include:

As noted in 1.4.3 Contrast (Minimum)

Web: Supports

Authored Content: Supports

Web: The product is functional for users without hearing.

Authored Content: Authors can create content which is functional for users without hearing.

Web: Supports

Authored Content: Supports

Web: The product is functional for users with limited hearing.

Authored Content: Authors can create content which is functional for users with limited hearing.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authors can create content which is functional for users without speech.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content which is functional with limited manipulation. Exceptions include:

As noted in 2.1.2 No Keyboard Trap

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 4.1.2 Name, Role, Value

Web: Supports

Authored Content: Supports

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

Authored Content: Authors can create content which is functional with limited reach and strength.

Web: Partially Supports

Authored Content: Partially Supports

Web: 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 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.5 Images of Text

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:

1.3.1 Info and Relationships

2.4.3 Focus Order

2.4.4 Link Purpose (In Context)

2.4.6 Headings and Labels

3.3.2 Labels or Instructions

4.1.2 Name, Role, Value

Web: Not Applicable

Web: The product is not platform software.

Web: Not Applicable

Web: The product is not platform software.

Web: Partially Supports

Web: The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: In most instances, when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exception includes:

As noted in 1.3.1 Info and Relationships

Web: Partially Supports

Web: For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 4.1.2 Name, Role, Value

Web: Supports

Web: When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology.

Web: Supports

Web: All text, text attributes (such as whether text is static or editable), and text boundaries (such as text that receives visual focus) are programmatically determinable, so they can be perceived and conveyed by assistive technology.

Web: Supports

Web: When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.

Web: Supports

Web: When one or more actions may be performed on an element, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology.

Web: Partially Supports

Web: For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exception includes:

As noted in 2.1.1 Keyboard

Web: Partially Supports

Web: On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exception includes:

As noted in 2.4.7 Focus Visible

Web: Supports

Web: When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.

Web: Supports

Web: In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exception includes:

As noted in 4.1.3 Status Messages

Web: Not Applicable

Web: The product is not platform software.

The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

In most instances, when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:

As noted in 2.1.1 Keyboard

On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 2.4.7 Focus Visible

In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:

As noted in 4.1.3 Status Messages

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 3.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

Authored Content: Authors can create content in which most functions can be used without vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 2.1.2 No Keyboard Trap

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.4 Resize text

As noted in 1.4.5 Images of Text

As noted in 1.4.10 Reflow

As noted in 1.4.11 Non-text Contrast

As noted in 1.4.12 Text Spacing

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content in which most functions can be used with limited vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.4 Resize text

As noted in 1.4.10 Reflow

As noted in 1.4.11 Non-text Contrast

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.1.2 No Keyboard Trap

As noted in 2.4.3 Focus Order

As noted in 2.4.6 Headings and Labels

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.11 Non-Text Contrast

As noted in 3.3.1 Error Identification

Authored Content: Authors can create content which is functional for users without perception of color. Exceptions include:

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.11 Non-Text Contrast

Web: Supports

Authored Content: Supports

Web: The product is functional for users without hearing.

Authored Content: Authors can create content which is functional for users without hearing.

Web: Supports

Authored Content: Supports

Web: The product is functional for users with limited hearing.

Authored Content: Authors can create content which is functional for users with limited hearing.

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authors can create content which is functional for users without speech.

Web: Partially Supports

Authored Content: Partially Supports

Web: Most functions of the product are usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 2.5.3 Label in Name

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content which is functional with limited manipulation and strength. Exceptions include:

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.1.2 No Keyboard Trap

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.5.3 Label in Name

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Authored Content: Partially Supports

Web: Most functions of the product are usable by people with limited reach. Exceptions are noted in:

As noted in 2.5.3 Label in Name

Authored Content: Authors can create content which is functional with limited reach. Exceptions include:

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.5.3 Label in Name

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain flashing content.

Authored Content: The product does not contain flashing content.

Web: Partially Supports

Authored Content: Partially Supports

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 are noted in:

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.5 Images of Text

As noted in 1.4.10 Reflow

As noted in 2.1.1 Keyboard

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 2.5.3 Label in Name

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

Authored Content: Authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 1.4.10 Reflow

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.5.3 Label in Name

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

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

Authored Content: Authored content does not ask for or display legal, financial, or personal data.

The product does not provide closed caption playback. Examples include:

Sample Blocks - Video

The product does not provide a mechanism to select and play closed audio description. Examples include:

Sample Blocks - Video

The product exposes the name, role and state or value of most objects to assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

The product exposes the row, column, and headers of table cells to assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

The product UI exposes most label relationships to assistive technologies. Exceptions include:

As noted in 4.1.2 Name, Role, Value

When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

The product exposes most text content and text values to assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

The product allows assistive technology to perform all actions on objects. Exceptions include:

As noted in 2.1.1 Keyboard

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

As noted in 2.4.7 Focus Visible

The product notifies assistive technology to most user interaction events. Exceptions include:

As noted in 4.1.3 Status Messages

The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions include:

As noted in 4.1.2 Name, Role, Value

For most objects that allow the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value