Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Fusion Cloud Field Service 24B

Product Description:

Oracle Field Service empowers field employees with browser-based and mobile apps for Android and iOS to drive productivity with instant access to accurate information. Allows mobile employees to view their daily schedule with current, pending and completed jobs visible on a single screen. It also provides field managers with a real-time, holistic view of field-service operations, and allows them to track resources, view in-progress, completed, and future service calls, and to intervene when jobs are in jeopardy of missing SLAs.

Date:

12-Apr-2024

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

  • PDF and ePub files

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
  • Client-side image maps specify the ALT attribute on AREA elements.
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

The documentation was tested for:

  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

The Android application was tested for:

  • Controls have an associated name
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

The iOS application was tested for:

  • 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

The product was tested for:

  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
  • Layout tables use appropriate markup
  • Style sheets are used only to change the layout and presentation on the screen

The documentation was tested for:

  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
  • Layout tables use appropriate markup
  • Style sheets are used only to change the layout and presentation on the screen

The Android application was tested for:

  • User interface component labels are associated with the fields they are labeling

The iOS application 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
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:

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

The Android application was tested for:

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

The iOS application was tested for:

  • The VoiceOver reading/presentation sequence matches the logical reading 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

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

The Android application 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

The iOS application 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
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.
  • A fixed display orientation is required for essential functionality.

The documentation was tested for:

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

The Android application was tested for:

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

The iOS application was tested for:

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)Supports

The product was tested for:

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

The documentation was tested for:

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

The Android application was tested for:

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

The iOS application was tested for:

  • There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)Supports

The product was tested for:

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

The documentation was tested for:

  • Information is not conveyed using color

The Android application was tested for:

  • Information is not conveyed using color

The iOS application was tested for:

  • Information is not conveyed using color
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
  • 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
  • Other text and images of text have a contrast ratio of at least 4.5:1

The Android application 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 iOS application 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
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

The Android application was tested for:

  • Text can be resized up to 200% without loss of content or functionality using the Android Zoom feature

The iOS application was tested for:

  • Text can be resized up to 200% without loss of content or functionality using the iOS Zoom feature
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Besides the decorative Oracle logo, images of text are not being used.

The documentation was tested for:

  • Images of text are not used

The Android application was tested for:

  • Images of text are not used

The iOS application was tested for:

  • Images of text are not used
1.4.10 Reflow (Level AA)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.

The documentation was tested for:

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom.

Due to mobile devices not supporting reflow, this criteria is always met for the Android and iOS applicaions

1.4.11 Non-text Contrast (Level AA)Supports

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

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

The iOS application was tested for:

  • Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)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 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 Android application was tested for:

  • The product does not have content implemented using markup languages that support editing the text style properties in this criteria.

The iOS application was tested for:

  • The product does not have content implemented using markup languages that support editing the text style properties in this criteria.
1.4.13 Content on Hover or Focus (Level AA)Supports

The product was tested for:

  • Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The documentation was tested for:

  • Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The Android application and iOS application were tested for:

  • Information appears on hover or focus using default platform behavior.
2.1.1 Keyboard(Level A)Supports

The product was tested for:

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

The documentation was tested for:

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

The Android application was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls

The iOS application was tested for:

  • 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 each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The Android application 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

The iOS application 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 VoiceOver and Switch Control assistive technologies
2.1.4 Character Key Shortcuts (Level A)Supports

The product was tested for:

  • There are no single character keyboard shortcuts.

The documentation was tested for:

  • There are no single character keyboard shortcuts.

The Android application was tested for:

  • There are no single character keyboard shortcuts.

The iOS application was tested for:

  • There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • Time limits are not used

The documentation was tested for:

  • Time limits are not used

The Android application was tested for:

  • Time limits are not used

The iOS application 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:

  • There is no moving, blinking or scrolling content

The Android application was tested for:

  • There is no moving, blinking or scrolling content

The iOS application 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

The documentation was tested for:

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

The Android application was tested for:

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

The iOS application 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

The product was tested for:

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

The documentation was tested for:

  • A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.

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 for Android and iOS applications

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

The Android application was tested for:

  • The name of the software application is meaningful.

The iOS application was tested for:

  • The name of the software application is meaningful.
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

The Android application was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence using the appropriate platform-specific technique for this, e.g. via a connected Bluetooth keyboard for touch devices, along with the built-in screen reader

The iOS application was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence using the appropriate platform-specific technique for this, e.g. via a connected Bluetooth keyboard for touch devices, along with the built-in screen reader.
2.4.4 Link Purpose (In Context)(Level A)Supports

The product was tested for:

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

The documentation was tested for:

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

The Android application was tested for:

  • Links are not used in the product

The iOS application was tested for:

  • Links are not used in the product
2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • All pages, except those that are a step in a process, are linked from the home page.

The documentation was tested for:

  • Pages can be found using the provided "search" function
  • Pages are in a site table of contents
  • Page contains controls that enable reaching all pages

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 for Android and iOS application

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:

  • Headers describe the topic or purpose of the content below them

The Android application was tested for:

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

The iOS application 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 position of the cursor in editable text fields
  • Current focus location and position of the caret in text is programmatically exposed.

The documentation was tested for:

  • Visual indication of the location of the focus

The Android application was tested for:

  • Visual indication of the location of the focus using TalkBack to display a focus indicator

The iOS application was tested for:

  • Visual indication of the location of the focus using VoiceOver to display a focus indicator
2.5.1 Pointer Gestures (Level A)Supports

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

  • There are no multipoint or path-based gesture actions.

The iOS application 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, the down-event of the pointer is not used to execute any part of the function

The Android application 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

The iOS application 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
2.5.3 Label in Name (Level A)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.

The documentation was tested for:

  • There are no user interface components labeled with text or images of text.

The Android application was tested for:

  • There are no user interface components labeled with text or images of text.

The iOS application was tested for:

  • There are no user interface components labeled with text or images of text.
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.

The Android application was tested for:

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

The iOS application 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

The Android application was tested for:

  • Properly set language property, where it differs from that of the underlying platform using the accessibilityLanguage property

The iOS application 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:

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

The documentation was tested for:

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

The Android application was tested for:

  • Properly set language property, where it differs from that of the underlying platform using the accessibilityLanguage property

The iOS application 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 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 Android application 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 iOS application 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 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 Android application 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

The iOS application 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

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

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 for Android and iOS applications

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

The Android application was tested for:

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

The iOS application 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:

  • User input is not required/possible

The Android application 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 iOS application was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
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:

  • User input is not required/possible

The Android application was tested for:

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

The iOS application was tested for:

  • Labels or instructions are provided when the product requires 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:

  • User input is not required/possible

The Android application was tested for:

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

The iOS application was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

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 Android application 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 iOS application 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
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.
  • Pages validate to the HTML specification.

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

  • Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids
  • Markup content validate to the appropriate markup specification(s)

The iOS application was tested for:

  • Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids
  • Markup content validate to the appropriate markup specification(s)
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’.
  • Frames have a meaningful title specified in the title attribute.

Exceptions:

  • Bug 36357060 - Configuration .Display. VoiceOver does not say numbers correctly
  • Bug 36321539 - Parts Catalog. Assign parts catalog to user type. VoiceOver does not say menu items
  • Bug 36321553 - Parts Catalog. VoiceOver says Field Name irregurally

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

  • User interface components have a programmatically associated name and role using the label property and appropriate Attributes
  • State information, properties, and values are programmatically exposed for user interface components using the appropriate part of the Android API

The iOS application was tested for:

  • User interface components have a programmatically associated name and role using the UIAccessibility Label property and appropriate Attributes
  • State information, properties, and values are programmatically exposed for user interface components using the appropriate part of the UIAccessibility API
4.1.3 Status Messages (Level AA)Supports

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.

The Android application was tested for:

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

The iOS application was tested for:

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

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 Supported

The product was tested for:

  • Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts

Exceptions:

  • Bug 34399444 - Oracle Field Service Android app disrupts Android OS accessibility features such as Sticky Keys, High Contrast and Large Fonts
  • Bug 34399447 - Oracle Field Service iOS app disrupts iOS accessibility features such as Sticky Keys, High Contrast and Large Fonts
 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 Supported

The product was tested for:

  • Responds to platform settings for color, contrast, font type, font size, and focus cursor.

Exceptions:

  • Bug 34399478 - Oracle Field Service iOS app does not respond to iOS settings for color, contrast, font type, font size, and focus cursor.
  • Bug 34399465 - Oracle Field Service Android app does not respond to Android OS 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 FeaturesSupports

Accessibility related documentation can be found here https://docs.oracle.com/en/cloud/saas/field-service/faaca/c-accessibility.html#Accessibility-E0E595D2

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.