Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle WebCenter Content Mobile (11.1.1.9)

Product Description:

The WebCenter Content Mobile apps provide a mobile view for Android and iOS based devices into the WebCenter Content server.. Document content is organized within the service in a folder hierarchy, and the mobile apps provide a UI to browse through this hierarchy and download documents. It also provides keyword search capabilities and a view of a user’s favorite content.

The Android app is developed as a native Android application using the Java programming language and the Android UI toolkit. As such it is expected to provide the accessibility features detailed in the Android developers documentation: support for navigating the UI through the directional pad (d-pad) and/or a physical keyboard, support for screen reading through TalkBack and Explore by Touch.

The iOS app is developed as a native iOS application using the Objective C programming language and the iOS SDK. At present it does not fully support the accessibility features provided by iOS.

Mobile users with accessibility needs should therefore consider using the WebCenter Content Android app

Date:

15-Feb-2018

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:
  • WebCenter Content for iOS app (mobile users should consider the WebCenter Content for Android app)

There are no steps that a user or administrator must take in order to configure accessibility mode for this app.  Users may need to enable the accessibility features of their Android device. Please refer to your manufacturer's help regarding accessibility settings.

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/us/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.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/Level A - Yes
Level AA - Yes
Level AAA - No
Section 508 as published in 2017, at https://www.Section508.govYes

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.
Supports with Exceptions
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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 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 the UIAccessibility Label attribute and are marked with the Image trait
  • Images that are decorative are marked with “setIsAccessibilityElement:NO”
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) or complex image is a container composed of individual accessible elements
  • Controls have an associated name
  • Non-text characters are not used or 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)Supports with Exceptions

The product was tested for:

  • User interface component labels are associated with the fields they are labeling through use of the label's text as the Label trait of the labeled field
  • Headings are marked as such using the Heading trait
  • Tables are contained in a Table component

Exception:

  • Bug 16716423 - If a list like search results has no items there is no feedback provided by TalkBack
  • Bug 27408577 - there is no feedback on how many items are shown in the downloads area
  • Bug 27415587 - When doing an Open With on a file the animated download progress is not accompanied by any feedback from TalkBack that the download is occurring
  • Bug 27416349 - 3 dots (more) menu within the revision history tab has no label
  • Bug 27409766 - Title of Create new folder dialog is not read out
  • Bug 27479570 - Within revision history tab the detials of a revision are not read out
  • Bug 27479996 - On app startup the message that the app is connecting to the server is not read out
1.3.2 Meaningful Sequence(Level A)Supports with Exceptions

The product was tested for:

  • The TalkBack reading/presentation sequence matches the logical reading sequence

Exception:

  • Bug 27409575 - In the about box user can use keyboard to scroll through legal terms but they are not read out by TalkBack
  • Bug 27409631 - In the about box user can use keyboard to scroll through 3rd party terms but they are not read out by TalkBack
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
1.4.1 Use of Color(Level A)Supports

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
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)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
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 using the Android screen magnification feature
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Images of text are not used
2.1.1 Keyboard(Level A)Supports with Exceptions

The product is composed of components that have full keyboard operation implemented through the use of a Bluetooth-connected keyboard

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

Exceptions:

  • Bug 27408161 - Inline error messages on sign-in dialog cannot be accessed via keyboard
  • Bug 27408813 - Inline error messages on change passcode dialog cannot be accessed via keyboard
  • Bug 27409056 - Inline error messages on passcode challenge dialog cannot be accessed via keyboard
  • Bug 27408267 - Action bars in folder list cannot be access via keyboard. Android's ExplorebyTouch feature can be used
  • Bug 27408405 - Action bars in search area cannot be access via keyboard. Android's ExplorebyTouch feature can be used
  • Bug 27410305 - From folder picker dialog for a copy or move the Enter key cannot be used to trigger the final copy or move
  • Bug 27416751 - Workflow status label in file properties tab cannot be accessed via keyboard
  • Bug 27409175 - Upon entering the about dialog the navigate up button cannot be accessed via keyboard
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 using the built-in TalkBack and Switch Control assistive technologies
2.2.1 Timing Adjustable(Level A)Supports

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

 

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

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 is always automatically met.

2.4.2 Page Titled(Level A)Supports

The product was tested for:

  • The name of the software application is meaningful.
2.4.3 Focus Order(Level A)Supports with Exceptions

The product was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence using a connected Bluetooth keyboard, along with TalkBack

Exceptions:

  • Bug 27408267 - Action bars in folder list cannot be access via keyboard. Android's ExplorebyTouch feature can be used
  • Bug 27408405 - Action bars in search area cannot be access via keyboard. Android's ExplorebyTouch feature can be used
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
2.4.5 Multiple Ways(Level AA)Supports

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 is always automatically met.

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

The product was tested for:

  • Visual indication of the location of the focus using TalkBack to display a focus indicator
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly set language property, where it differs from that of the underlying platform using the accessibilityLanguage property
3.1.2 Language of Parts(Level AA)Supports

The product was tested for:

  • Properly set language property, where it differs from that of the underlying platform using the accessibilityLanguage property
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 user interface of the software, an additional change of keyboard focus, or the spawning of a new 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 user interface of the software, an additional change of focus, or the spawning of a new screen
3.2.3 Consistent Navigation(Level AA)Supports

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 is always automatically met.

3.2.4 Consistent Identification(Level AA)Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)Supports with Exceptions

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

Exceptions:

  • Bug 27408161 - Inline error messages on sign-in dialog cannot be accessed via keyboard
  • Bug 27408813 - Inline error messages on change passcode dialog cannot be accessed via keyboard
  • Bug 27409056 - Inline error messages on passcode challenge dialog cannot be accessed via keyboard
3.3.2 Labels or Instructions (Level A)Supports with Exceptions

The product was tested for:

  • labels or instructions are provided when the product requires user input.

Exceptions

  • Bug 27408999 -  The Change passcode dialog gives same instructions of Enter Password for New Passcode and Confirm Passcode input fields
3.3.3 Error Suggestion (Level AA)Supports with Exceptions

The product was tested for:

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

Exceptions:

  • Bug 27408161 - Inline error messages on sign-in dialog cannot be accessed via keyboard
  • Bug 27408813 - Inline error messages on change passcode dialog cannot be accessed via keyboard
  • Bug 27409056 - Inline error messages on passcode challenge dialog cannot be accessed via keyboard
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
  • Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)Supports

The product was tested for:

  • Markup languages aren't used to generate the user interface
4.1.2 Name, Role, Value (Level A)Supports

The product was tested for:

  • TalkBack can gather information about, activate(or set) and keep up to date on the status of user interface controls in the content.

back to top

2017 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 FeaturesSupports

Product was tested for:

  • Software does not disrupt platform features that are defined in the platform documentation as accessibility features.
 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 PreferencesSupports

Application respects user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

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 FeaturesNot Supported

Although app provides compatibility with assistive technology. the documentation does not mention this

Bug 27553908 -  documentation needs a section to list and explain how to use the accessibility and compatibility features of the mobile app

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 http://www.oracle.com/us/corporate/accessibility/oracle-accessibility-program-173235.html) 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/us/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.