Oracle Accessibility Conformance Report

The product 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
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Titles for Objects and Applets are provided
• Controls have an associated name
• Text summary or alternative is provided for time-based media
• Client-side image maps specify the ALT attribute on each AREA element.
• 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 product 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

Exceptions found in Site Studio Designer feature:

The properties toolbox in the Site Studio Designer can be arranged in two ways;

• Alphabetical, where all properties are sorted in one large group, or
• Grouped into sections. In this mode Website properties are grouped differently from website section properties, etc. The issue is that a screen reader has no way to know that the current item is actually a header for a group of properties. When it is read it is read as "Website Properties" instead of "Website Properties, group header, contains 24 items", or similar. (Bug 9469116)

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

The product was tested for:

• 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 a 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.

Observations:

Bug 31609665, 31609664, 31609661, 31609655: Turning on the autocomplete is not a good thing to do for username and password fields due to security reasons. So the product team has decided to not turn on the autocomplete. 

Bug 31609729, 31609723: Incorrect Input purpose for "Email address" and "Full Name". In ADF, the input text autocomplete attribute has only on/off as options. So WebCenter Content ADFUI is dependent on the base bug 30924632. 

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

The compare changes feature of Site Studio designer renders both versions of the HTML page and then highlights differences.
The differences are highlighted in two ways:

• red crossed-out text for content that is deleted, and bright green text for newly added content.
• for accessibility and screen readers the differences are also added to the page as hidden links. This allows a screen reader to tab through the page and hear the changes called out, along with an indication as to whether the content was added or removed.

  There currently is no visible focus indication to the color highlighted differences as the reader tabs around. (Bug 9469168)

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
• All other text and images of text have a contrast ratio of at least 4.5:1

Exception found in Content UI:

• Viewer images are not visible in high contrast mode (Bug 20900389).

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

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.

We tested for 400% zoom but our product is not designed to support properly 400% zoom with one-directional scrolling criteria so we have found the below exceptions: 

Bug - 31597817, 31401430, 31364908: Horizontal scroll will be coming and 100% responsiveness is not possible in WebCenter Content UI. There will not be any loss of data in our solution.

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

Bug 31721372:  Non-Text Contrast-User Interface components do not have required contrast ratio

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 above test cases are tested with the below exceptions:

Bug- 31612008: Complete folder name is not coming and it's truncated.  

Bug- 31612510, 31612113: No text spacing in Security Group dropdown list. 

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.

Bug 31703886: Content on Hover is not dismissable without moving the mouse pointer.

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

Exceptions found in Site Studio Designer feature:

• The columns in the asset panel cannot be resized without using a mouse. (Bug 9463184)

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

This is not applicable as there are no single character keyboard shortcuts available. 

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 adjusted to at least 10 times longer before encountered

The documentation was tested for:

• Time limits are not used

The product was tested for:

• There is no moving, blinking or scrolling content

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

Exceptions found in Content UI:

• Skip to Main Content link is missing on all pages (Bug 22844878). This is caused by ADF Bug 22895685.

The documentation was tested for:

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

The product was tested for:

• Pages have a meaningful title specified in the TITLE element

The documentation was tested for:

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

The product was tested for:

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

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 contained in a "site map"
• Pages can be found using the provided "search" function
• Pages are in a site table of contents
• 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.

This is not applicable as 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, 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 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 has been 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.

Observation:

Bug 31612544, 31610517, 31610480, 31610105, 31609736, 31609735, 31609732.

The above product bugs depend on the ADF Bug# 31696289 - ACC: SELECTONECHOICE IN COMPACT MODE - SCREEN READER OMITS. THE LABEL OF THE COMPONENT WHILE READING IT.  The issue is about selectOneChoice component in compact mode being read by omitting the label by the ScreenReader. SelectOneChoice have 2 modes - 'default' and 'compact'. In default mode, the screen reader on focusing on that component reads as ' Button Menu'. In compact mode, the screen reader on focussing on that component reads as 'Button menu' only. Here it omits the .

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

• Properly set lang attribute for each page

The documentation was tested for:

• Properly set lang attribute for each page

The product was tested for:

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

The documentation was tested for:

• Text passages are in the same language as the page

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

• There are no navigational mechanisms that are repeated

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:

• Submissions can be reversed by the user
• 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 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

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 product 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 programatically exposed name
• Frames have a meaningful title specified in the title attribute

Exception found in Native UI:

• Screen reader reads 1 of 1 instead of 1 of x for Actions menu and submenu when selected in table row (Bug 25910498)

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:

• There are no status messages

The documentation was tested for:

• There are no status messages

Documentation available at https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/acfmw/accessibility-features-and-tips-oracle-webcenter-content1.html?xd_co_f=d5c66620-a707-4b37-8cbd-8d72fe81850d#GUID-431B8D2C-F28A-4309-9769-E1B60550E196 covers

• Personalizing accessibility preferences
• Navigating Oracle WebCenter Content user interface using keyboard shortcuts
• Performing specific actions in the Oracle WebCenter Content user interface using keyboard shortcuts

Product documentation is in electronic format