Oracle Accessibility Conformance Report

The product was tested for:

• Images that convey information such as ImageView and ImageButton objects have meaningful alternative text using the android:contentDescription XML attribute for static elements and the setContentDescription() method for dynamic elements.
• Images that are decorative have the android:contentDescription XML attribute set to "@null".
• 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
• Text summary or alternative is provided for time-based media
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

Exceptions:

SPSS-6106:  Incident Queue Page: Close and Map Zoom buttons not read by screen reader

SPSS-6110:  Map View:  Unit Chips, Incident Chips, and My Unit Chip with corresponding status and information not read by screen reader

The product was tested for:

• User interface component labels are associated with the fields they are labeling
• Headings are marked as such using the accessibilityHeading attribute, documented here: https://developer.android.com/reference/android/R.attr#accessibilityHeading
• Tables are contained in a Table component

The product was tested for:

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

The product was tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound

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.

Exception:

SPSS-6178: Only landscape mode is supported

The product was tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.
• There are no text fields that collect information about the user.

The product was tested for:

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

Exception:

SPSS-6109:  Non-Case Reporting Screens: Text content areas with contrast < 3:1

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

Exception:

SPSS-6109:  Non-Case Reporting Screens: Text content areas with contrast < 3:1

The product was tested for:

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

Exception:

SPSS-6113:  IDCS Login Screen, Unit Selection, My Unit/Unit Status, and Incidents Labeling:  Text Content Zoom issues - some fields get cut off when resized to 200% 

The product was tested for:

• Images of text are not used

Due to mobile devices not supporting reflow, this criteria is always met.

The product was tested for:

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

The product was tested for:

• When the following attributes and no others are modified there is no loss in functionality or content:
  • Line height (line spacing) to at least 1.5 times the font size
  • Spacing following paragraphs to at least 2 times the font size
  • Letter spacing (tracking) to at least 0.12 times the font size
  • Word spacing to at least 0.16 times the font size

At the moment, this is not currently testable in native environments.

The product was tested for:

• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls

Exceptions:

Unable to perform functions from keyboard only:

SPSS-6382:  Incident Queue: Keyboard Access: Unable to perform functions from keyboard only: Incident Queues: navigate to first incident from header; unit status chips non-actionable

SPSS-6102:  Incident Queue: Keyboard Access: Unable to perform functions from keyboard only: Map View: Unit Selection for Zoom and action of Zooming into Unit on Map

Illogical movement of focus through the controls on:
SPSS-6101:  Incident Queue: Keyboard Access: Illogical Movement of Focus: First incident and between incident navigation using keyboard

SPSS-6103:  Incident Queue: Keyboard Access: Illogical movement of Focus: Unit Status: Closing panel header, Edit box highlighting visibility, and Status Search

SPSS-6104:  Incident Queue: Keyboard Access: Illogical movement of Focus: Ask Oracle (Menus) Unit Search, and Soft Keyboard Closure

The product was tested for:

• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls

The product was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits are not used.

The product was tested for:

• There is no moving, blinking or scrolling content

The product was tested for:

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

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.

The product was tested for:

• The name of the software application is meaningful.

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

Exceptions:

SPSS-6101:  Incident Queue: Keyboard Access: Illogical Movement of Focus: First incident and between incident navigation using keyboard

SPSS-6102:  Incident Queue: Keyboard Access: Unable to perform functions from keyboard only: Map View: Unit Selection for Zoom and action of Zooming into Unit on Map

The product was tested for:

• Links are not used in the product

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.

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

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

Exceptions:

SPSS-6104:  Incident Queue: Keyboard Access: Illogical movement of Focus: Ask Oracle (Menus) Unit Search, and Soft Keyboard Closure

SPSS-6103:  Incident Queue: Keyboard Access: Illogical movement of Focus: Unit Status: Closing panel header, Edit box highlighting visibility, and Status Search

The product was tested for:

• Multipoint or path-based gesture actions can be completed using a different input modality.

Exceptions:

SPSS-6941:  User does not have single gesture for zoom out on map.

The product was tested for:

• When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function
• When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion

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

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

The product was tested for:

• Application is in the locale/language of the underlying platform

The product was tested for:

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

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

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.

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.

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

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

The product was tested for:

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

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

The product was tested for :

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

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

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

The product was tested for:

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

The product was tested for:

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

The Product Documentation Describes:

• Special keystrokes needed to operate controls.

Accessibility help is available in the Documents & Resources section of the Oracle Public Safety Suite User Manual located on the Customer Portal:

Public Safety Suite Customer Portal

Product documentation is in electronic format.

Oracle Global Customer Support can provide information about accessibility features of the product.

Oracle customers have access to electronic support through Oracle Service Cloud or by calling Oracle Support at 1.800.633.0769 . 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.