Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle WebCenter Content (Update 1) 12.2.1.4.0

Product Description:

Oracle WebCenter Content bundles Oracle's solutions for Contents Management, Records Management, and Imaging, providing a complete solution for customers seeking to implement an enterprise-wide content management system.

WebCenter Content includes:

  • Content Management

  • Universal Records Management

  • Content Conversion

  • Imaging

WebCenter Content has two Web User Interfaces available for use - the original "Native UI" and the modern "Content UI". Both are covered in this ACR.

Date:

03-May-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

  • The WYSIWYG (What You See Is What You Get) Site Studio Contributor tool, which is part of the optional Site Studio feature
  • PDF, Mobi, ePub documentation

When using the Java based applets on Microsoft Windows systems, the Java Access Bridge for Microsoft Windows will need to be enabled to support assistive technologies

User preferences can be configured in the Content UI:

  • Any user can choose to use the screen reader mode, large fonts mode and high contrast mode
  • This can be done at the first login or at any subsequent point of time.

Dependent Products


This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports
The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

  • Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Supports

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
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Partially Supports

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
1.3.2 Meaningful Sequence(Level A)Supports

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.
1.3.3 Sensory Characteristics(Level A)Supports

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.
1.3.4 Orientation (Level AA)Supports

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.
1.3.5 Identify Input Purpose (Level AA)Partially Supports

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.
1.4.1 Use of Color(Level A)Partially Supports

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
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Partially Supports

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
1.4.4 Resize text(Level AA)Supports

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
1.4.5 Images of Text(Level AA)Supports

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
1.4.10 Reflow (Level AA)Partially Supports

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.
1.4.11 Non-text Contrast (Level AA)Not Supported

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
1.4.12 Text Spacing (Level AA)Partially Supports

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
1.4.13 Content on Hover or Focus (Level AA)Partially Supports

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.
2.1.1 Keyboard(Level A)Partially Supports

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
2.1.2 No Keyboard Trap (Level A)Supports

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
2.1.4 Character Key Shortcuts (Level A)Not Applicable

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
2.2.1 Timing Adjustable(Level A)Supports

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
2.2.2 Pause, Stop, Hide (Level A)Supports

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
2.3.1 Three Flashes or Below Threshold(Level A)Supports

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
2.4.1 Bypass Blocks(Level A)Partially Supports

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
2.4.2 Page Titled(Level A)Supports

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.
2.4.3 Focus Order(Level A)Supports

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
2.4.4 Link Purpose (In Context)(Level A)Supports

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.
2.4.5 Multiple Ways(Level AA)Supports

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
2.4.6 Headings and Labels(Level AA)Supports

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.
2.4.7 Focus Visible(Level AA)Supports

The product was tested for:

  • Visual indication of the location of the focus

The documentation was tested for:

  • Location of focus is visible.
2.5.1 Pointer Gestures (Level A)Not Applicable

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
2.5.2 Pointer Cancellation (Level A)Supports

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
2.5.3 Label in Name (Level A)Partially Supports

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
2.5.4 Motion Actuation (Level A)Supports

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
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly set lang attribute for each page

The documentation was tested for:

  • Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)Supports

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
3.2.1 On Focus(Level A)Supports

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
3.2.2 On Input(Level A)Supports

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
3.2.3 Consistent Navigation(Level AA)Supports

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
3.2.4 Consistent Identification(Level AA)Supports

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

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
3.3.2 Labels or Instructions (Level A)Supports

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
3.3.3 Error Suggestion (Level AA)Supports

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
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

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
4.1.1 Parsing(Level A)Supports

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

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.
     
4.1.3 Status Messages (Level AA)Not Applicable

The product was tested for:

  • There are no status messages

The documentation was tested for:

  • There are no status messages

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

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
602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

back to top

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.