Oracle Accessibility Conformance Report

The product and documentation were tested for:

• Images that convey information have meaningful alternative text using ALT
• Images that are decorative are marked up using ALT=”” or CSS background images
• CAPTCHAs are not used
• Non-text characters are not used or have meaningful alternative text.

Exception(s) in product:

• MTRM-3177 - Diagram and Execution: Screen reader annouces generic label instead of actual node name in workflow builder and executions diagram

The product and documentation were tested for:

• User interface component labels are associated with the fields they are labeling.
• Relationships between data are identifiable by assistive technology, or a description of the information and the relationship is provided.
• Data tables specify SUMMARY or CAPTION
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
• Layout tables use appropriate markup
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists

Exception(s) in product:

• MTRM-2492 - Screen readers cannot correctly interpret navigation menu structure in transaction navigation panel.

The product and documentation were tested for:

• The sequence of elements in the DOM matches a logical reading sequence

The product and documentation were tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The product and documentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text

The product and documentation were tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.

The product and documentation were tested for:

• Information is not conveyed using color

The product and documentation were tested for:

• Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
• Other texts and images of text have a contrast ratio of at least 4.5:1

Exception(s) in product:

• MTRM-2479: Low contrast affects readability of page title and attempt column of execution history table view
   

The product and documentation were tested for:

• Text can be resized up to 200% without loss of content or functionality

Exception:

• MTRM-3012 - Executions Page: Components like workflow id and large ref names overlaps with other components
  
   

The product and documentation were tested for:

• Images of text are not used.

The product and documentation were tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content

Exception(s) in product:

• MTRM-3012 - Executions Page: Components like workflow id and large ref names overlaps with other components
• MTRM-3179 - Action buttons are not visible and cannot be reached via scrolling in toggle device view in definitions, connectors, agentic ai, builder, notification pages

The product and documentation were tested for:

• Non-text items have a contrast ratio of at least 3:1.

The product and documentation were tested for:

• When the following attributes and no others are modified there is no loss in functionality or content:
  • Line height (line spacing) to at least 1.5 times the font size
  • Spacing following paragraphs to at least 2 times the font size
  • Letter spacing (tracking) to at least 0.12 times the font size
  • Word spacing to at least 0.16 times the font size

The product and documentation were tested for:

• Dismissable -The content can be dismissed without moving the pointer or keyboard focus
• Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing
• Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

The product and documentation were tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

Exception(s) in product:

• MTRM-3179 - Action buttons are not visible and cannot be reached via scrolling in toggle device view in definitions, connectors, agentic ai, builder, notification pages
• MTRM-3164 - Multi component task nodes and add task dialog box are not accessible with keyboard in workflow builder page.

The product and documentation were tested for:

• Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The product and documentation were tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits in the product can be turned off before they are encountered.
• Time limits in the product can be adjusted to at least 10 times longer before encountered.
• Time limits in the product can be extended with at least 20 seconds warning up to 10 times.

The documentation was tested for:

• Time limits are not used

The product and documentation were tested for:

• There is no moving, blinking, scrolling or auto-updating content.

The product and documentation were tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The product and documentation were tested for:

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

The product and documentation were tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

The product and documentation were tested for:

• The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
   

The product and documentation were tested for:

• Pages are fully inter-linked to each other
• Page contains controls that enable reaching all pages

The product and documentation were tested for:

• Headers describe the topic or purpose of the content below them
• Labels describe the purpose of the associated field

The product and documentation were tested for:

• Visual indication of the location of the focus

The product and documentation were tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The product and documentation were tested for:

• There are no multipoint or path-based gesture actions

The product and documentation were tested for:

• When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function
• When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion
• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.

The product and documentation were tested for:

• User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.

The product and documentation were tested for

• There are no functions that require motion of the device.

The product was tested for:

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.

The documentation was tested for:

• There is no functionality in documentation that uses dragging movements.

The product and documentation were tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.
• The function can be achieved through a different control in the same software that meets this criterion.
• The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

The product and documentation were tested for:

• Properly set lang attribute for all pages

The product and documentation were tested for:

• There are no passages of text that are different from the language of the page.

The product and documentation were tested for:

• When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

The product and documentation were tested for:

• Changes in the value of user interface components do not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

The product and documentation were tested for:

• Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time

The product and documentation were tested for:

• Images and controls are used and identified consistently throughout the documentation

The product and documentation were tested for:

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

The product was tested for:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

Exception(s) in product:

• MTRM-3095 - Task-level required input fields do not consistently provide error identification in workflow builder page.

The documentation was tested for:

• The documentation does not have input fields except for the Search field, which accepts all inputs.

The product was tested for:

• Labels or instructions are provided when the product requires user input

The documentation was tested for:

• Content does not require user input

The product was tested for:

• Where suggestions for fixing an input error are known, they are provided to the user

Exception(s) in product:

• MTRM-3095 - Task-level required input fields do not consistently provide error identification in workflow builder page.

The documentation was tested for:

• Content does not require user input

The product was tested for:

• Data is checked for input errors with an opportunity for the user to correct them

The documentation was tested for:

• The documentation does not require user input that modifies user controllable data

The product and documentation were tested for:

• There are no occurrences of information that the user needs to enter which has been previously entered.

The product was tested for:

• The product supports copy and paste while authenticating.

The documentation was tested for:

• Authentication is not required

The product and documentation were tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc
• Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.

Exception(s) in product:

• MTRM-3013 - Dialogs and alert dialogs on defintions, connectors, Agentic AI and transaction pages does not have accessible name
• MTRM-3016 - Workflow workbench history and transaction details right side drawer does not use supported ARIA attributes
• MTRM-3014 - Form element does not have a label in workflow notification and different tasks under workflow builder page

The product was tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

Exception(s) in product:

• MTRM-2496 - No status dialog box for successful submission in connectors, agentic ai and executions page

The documentation was tested for:

• There are no status messages

The product documentation describes:

• special keystrokes needed to operate controls
• workarounds

Accessibility-related documentation can be found at: Develop Accessible Oracle JET Apps.

A reference guide for keystrokes for ojet diagram can be found at: https://jet.oraclecorp.com/trunk/jsdocs/oj.ojDiagram.html#keyboard-section

Product documentation is in electronic format

Technical Support can be found in the Community Forums at:

https://forums.oracle.com/ords/apexds/domain/dev-community/category/application-development?tags=oracle-transaction-manager-for-microservices

Technical Support can be found in the Community Forums at:

https://forums.oracle.com/ords/apexds/domain/dev-community/category/application-development?tags=oracle-transaction-manager-for-microservices