Oracle Accessibility Conformance Report

The Workspace Console was 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
• Titles for Objects and Applets are provided
• Controls have an associated name
• Time-based media is not used
• Image maps are not used
• Non-text characters have meaningful alternative text
• CAPTCHAs are not used

The Client was tested for:

• Images that convey information are embedded within standard user interface components and have a meaningful AccessibleName and/or AccessibleDescription
• Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription
• Data tables include a summary or caption, programmatically connected with the table as the AccessibleTable's AccessibleSummary
• Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
• Time-based media is not used
• Non-text characters have meaningful alternative text
• CAPTCHAs are not used

The documentation was tested for:

• Images that convey information have meaningful alternative text
• Images that are decorative are marked up using ALT=”” or CSS background images
• Titles for Objects and Applets are provided
• Controls have an associated name
• Time-based media is not used
• Image maps are not used
• Non-text characters have meaningful alternative text
• CAPTCHAs are not used

The Workspace Console was tested for:

• User interface component labels are associated with the fields they are labeling
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
• Data tables specify SUMMARY or CAPTION
• Layout tables use appropriate markup
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

The Client was tested for:

• User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations
• Headings are marked as such with a Group relation from the header to the items beneath the header
• Groups of components are marked as such, with a Group relation from the header of the group to the members of the group
• Style sheets are used only to change the layout and presentation on the screen
• Lists are contained within a List component
• Tables are contained within a Table component, implement the AccessibleTable interface, provide an AccessibleSummary, and contain include row and column headers where appropriate

The documentation was tested for:

• User interface component labels are associated with the fields they are labeling
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists
• Table markup is used for marking up data tables (including row and column headers, table captions/summaries where appropriate)
• Data tables specify SUMMARY or CAPTION where appropriate
• Layout tables are not used
• Groups of components are not used
• Style sheets are used only to change the layout and presentation on the screen

Exceptions found:

• Bug 16501929:  In the metadata field area, date field captions and the drop-down calendar fail to be read by a screen reader.  In addition, inclusion of date metadata fields may cause other metadata fields to fail reading.
• Bug 16501947:  On the batch search dialog in the Client, a screen reader fails to read the From and To date field captions as well as the drop-down calendar.
• Bug 18205088:  In the Client, choice list fields are not read correctly when you navigate through the items.
• Bug 20634888:  In the Commit Profile "Edit Execution Order" dialog, a screen reader may encounter an empty list item.
• Bug 25302207: In the "Add/Edit Conversion job" dialog of Workspace Console,  a screen reader may encounter an empty list item.

The product was tested for:

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

The documentation was tested for:

• Content is available in a meaningful sequence

The product was 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 documentation was 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. Images have meaningful text alternative

The product was tested for:

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

The documentation was tested for:

•  Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential

The product was tested for:

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

Exceptions found:

• Bug 32198755 - Input purpose is missing on some fields 

The documentation was tested for:

• There are no text fields that collect information about the user

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight
• Information conveyed by color has a contrast ratio of at least 3:1

The documentation was tested for:

•  Information conveyed by color is available in alternative formats, such as shape, text, font weight

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Text can be resized up to 200% without loss of content or functionality
• Text (and application) resizes up to 200% using the platform's built-in magnifier or zoom feature

The documentation was tested for:

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

The product was tested for:

• Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

The documentation was tested for:

•  Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

The product was 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.

Exceptions found:

• Bug 32198955 - Horizontal scrollbars are displayed in some pages when the browser size is reduced

The documentation was tested for:

• Content is presented without loss of information or functionality, and without requiring scrolling in two dimensions except for parts of the content which require two-dimensional layout for usage or meaning. Text information reflows so that only one direction of scrolling is required while at 400% zoom

The product was tested for:

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

The documentation was tested for:

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

The product was 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 documentation was 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 was 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 documentation was 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 Workspace Console was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

The Client is composed of components that have full keyboard operation implemented as documented in the Using keyboard shortcuts section of Using Oracle WebCenter Enterprise Capture guide. Where the product uses components developed after this document was published, those components use the WAI-ARIA Keyboard Bindings and Behaviors, or other keyboard operation as documented in the product documentation.

The Client was tested for:

• ability to perform functions from the keyboard only
• logical movement of focus through the controls
• proper operation of unique keystrokes, including those listed in the product documentation

The documentation was tested for:

• The logical tab order through the controls and selectable elements
• Ability to access page elements (links and buttons)
• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls

The product was 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 documentation was tested for:

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

The product was tested for:

• There are no single character keyboard shortcuts.

The documentation was tested for:

• There is no single character keyboard shortcut in content

The product was tested for:

• 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 was tested for:

• No moving, blinking or scrolling content
• No auto-updating information

The documentation was tested for:

• No moving, blinking or scrolling content
• No auto-updating information

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
• WAI-ARIA Landmark elements are used outside of repetitive navigation links

The documentation was tested for:

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

The product was tested for:

• Web pages have a meaningful title specified in the TITLE element.
• Client application:  The name of the software application is meaningful.

The documentation was tested for:

• Pages have a meaningful title specified in the TITLE element.

The Workspace Console was tested for:

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

The Client was tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence, as per the Using keyboard shortcuts section of the Using Oracle WebCenter Enterprise Capture, or where appropriate the WAI-ARIA Keyboard Bindings and Behaviors, or other keyboard operation as documented in the product documentation.

The documentation was tested for:

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

The product was 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 documentation was tested for:

• The purpose of a link can be determined from the link text or from the surrounding text

The product was tested for:

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

The documentation was tested for:

• Pages contain controls that enable reaching other pages
• Pages can be found using the provided "Search" function

The product was tested for:

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

The documentation was tested for:

• Headings and labels describe topic or purpose

The product was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Location of focus is visible

The product was tested for:

• There are no multipoint or path-based gesture actions

The documentation was tested for:

• There are no multipoint or path-based gesture actions

The product was 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 documentation was tested for:

• 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

The product was 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 documentation was 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 was tested for:

• There are no functions that require motion of the device

The documentation was tested for:

• There are no functions that require motion of the device

The Workspace Console was tested for:

• Properly set lang attribute for each page

The Client was tested for:

• Properly set locale/language

The documentation was tested for:

• Properly set lang attribute for each page

The Workspace Console was tested for:

• Proper use of lang attribute for text passages that are in a different language than that of the page

The Client was tested for:

• Properly set locale/language for text passages that are in a different language than that of the software

The documentation was tested for:

• Text passages are in the same language as the page

The Workspace Console was 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 Client was tested for:

• When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

The documentation was 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 Workspace Console was tested for:

• Changes in the value of user interface components 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 Client was test for:

• Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

The documentation was tested for:

• Changes in the value of user interface components 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 Workspace Console was 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

Regarding the Client:

• Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

The documentation was 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 was tested for:

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

The documentation was tested for:

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

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

The documentation was tested for:

• The documentation does not have input fields, except for the Search field

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

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
• Data can be reviewed, corrected, and confirmed by the user before they are finalized

The documentation was tested for:

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

The Workspace Console was tested for:

• Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs

Regarding the Client:

• Markup languages aren't used to generate the user interface

The documentation was tested for:

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
• Pages validate to the HTML specification

The Workspace Console was 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’.
• Custom controls have appropriate roles specified using the role attribute
• Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
• Custom controls have a meaningful programmatically exposed name
• Frames have a meaningful title specified in the title attribute

The Client was tested for:

• User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API
• State information, properties, and values are programmatically exposed for user interface components
• Event notification of changes to names, states, properties, and values is available to assistive technologies

Exceptions found:

• Bug 16501929:  In the metadata field area, date field captions and the drop-down calendar fail to be read by a screen reader.  In addition, inclusion of date metadata fields may cause other metadata fields to fail reading.
• Bug 16501947:  On the batch search dialog in the Client, a screen reader fails to read the From and To date field captions as well as the drop-down calendar.
• Bug 18205088:  In the Client, choice list fields are not read correctly when you navigate through the items.
• Bug 20634888:  In the Commit Profile "Edit Execution Order" dialog, a screen reader may encounter an empty list item.
• Bug 25302207: In the "Add/Edit Conversion job" dialog of Workspace Console,  a screen reader may encounter an empty list item.

The documentation was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.

The product was tested for:

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

The documentation was tested for:

• There are no status messages

Product was tested for:

• Software does not disrupt platform features that are defined in the platform documentation as accessibility features.

Bug 26184220 - Product does not permit user preferences

Oracle WebCenter Enterprise Capture documentation can be found in the 12.2.1.4.0 Oracle Fusion Middleware Accessibility Guide under the "Accessibility Features and Tips for Oracle WebCenter Enterprise Capture" heading.

https://www.oracle.com/pls/topic/lookup?ctx=en/middleware/fusion-middleware/12.2.1.4/acfmw&id=GUID-8A0C6711-621B-48CE-B252-16E3BDF9E4D7

The documentation describes the following accessibility features of Oracle WebCenter Enterprise Capture.

• Capture Workspace Console User Preferences to use Screen Reader
• Capture Workspace Console Keyboard Shortcuts
• Changing the client display to high contrast
• Changing the font size displayed in the client
• Using keyboard shortcuts

Product documentation is in electronic format.