Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Aconex for Android 20.6

Product Description:

Oracle Aconex mobile application provides issue and inspection management for quality assurance/control, safety on construction sites, as well as the ability to view project drawings and pin issues to drawings. This application helps overcome the challenges of paper-based drawing and inspection management, and scattered and incomplete project data.

Oracle Aconex simplifies building information modeling by connecting teams, models and project data on a single online collaboration platform. Access the BIM information you need for your construction and engineering projects, from wherever you are, from your mobile device.

Oracle Aconex provides collaborative project delivery, including design & construction coordination, field management, and project controls. Asset owners and project leaders rely on Oracle Construction and Engineering software for the visibility and control, connected supply chain, and data security needed to drive performance and mitigate risk, helping teams plan, build, and operate critical assets.

Date:

22-Jul-2020

Archive Note:

This VPAT applies to only version 20.6. It does not apply to any versions of Oracle Aconex for Android after this. This VPAT has been superseded by Oracle Aconex for Android 20.9.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

1. 29532194 - Drawing display along with the pins 

2. 29532171 - PDF Inspections in Inspections module 

3. 31444663 - Navigation across Models in Model Module

4. 31522851 - Details are not displayed when show more button is clicked

 

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)Partially Supports

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

 

-Content description , in turn accessibility information is missing for the "phone" icon which appears when the new issue is added by the user or the existing issue is modified by the user. 

-Content description, in turn accessibility information is missing for the "error" icon which appears in the issue listing screen when there is an error for issue create or issue edit action by the user. 

-Content description, in turn accessibility information is missing for the “cross" icon which appears in the drawing listing screen when the item is getting downloaded.

-Content Description, in turn accessibility information is missing for "back" icon which appears in Drawings filter screen when user opens to apply filters in Drawing List.

-Content Description, in turn accessibility information is missing for "Cross" icon which appears in Markup Screen when user applies markup on selected Photo of issue/inspection.

-Content Description, in turn accessibility information is missing for "Undo" icon which appears in Markup Screen when user applies markup on selected photo of an issue/inspection.

-Content Description, in turn accessibility information is missing for "Create Issue" icon which appears in Inspection Details screen when new inspection is created/edited by an user.

-Content Description, in turn accessibility information is missing for "Status" dropdown which appears in Inspection Details screen when an inspection is created/edited by an user.

-Content Description, in turn accessibility information is missing for "Save" icon which appears when user Signs an inspection in Signature Dialog for a Inspection.

-Content Description, in turn accessibility information is missing for "Back" button which appears in Markup screen when user opens an attached photo of an inspection.  

-Content Description, in turn accessibility information is missing for "Add Notes" icon which appears in Inspection detail screen when new inspection is  being created/edited by an user.

-Content Description, in turn accessibility information is missing for "save" icon which appears in markup screen when the markup is applied on selected photo of issue/inspection.

-Content Description, in turn accessibility information is missing for "thickness" icon which appears in mark up screen when the markup is applied  on selected photo of an issue/inspection.

-Content Description, in turn accessibility information is missing for color selection icon which appears when the markup is applied on selected photo of an issue/inspection in mark up screen  

- Content Description, in turn accessibility information is missing for save icon which appears in inspection details screen when user creates/edits inspection 

- Content description should be provided for the Progress Loader in Checklist Templates Screen which appears while  templates are getting fetched from the server or DB.
- Content description should be provided for Loader icon which appears when project is selected and project data is getting fetch from the server or DB.

- Accessibility information should be provided for Number of Templates available in Template Group in Template List Screen

The exceptions are captured in the bugs- 29453442, 31028408 , 31028217,31432810, 31413735, 31432728,31432806, 31432799, 31403407

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 marked as such using the accessibilityHeading attribute

Below issues were noted while testing for Accessibility , 

-Issue Filter and Inspection Filter  screens has to provide default filter information on screen entry or when user resets the applied filters on the respective screens. 

-Provide accessibility information about custom fields addition to issue detail screen on selecting issue types 

-Provide accessibility information on log-in progress 

-Provide accessibility information for new pin creation from drawing detail screen and change accessibility focus to new issue pin screen and provide accessibility hint for user to drag up the new issue screen. 

-Following actions in New issue screen in drawing details takes accessibility focus to Drawing details title. The focus should move back to corresponding 

item in New Issue screen 

  • Changing issue type 
  • Changing issue description 
  • Adding photos 
  • Changing Assigned To 
  • Changing Locations 
  • Changing Location Details

- Provide Accessibility information for Location Field in Inspection Detail Screen

- Provide Accessibility information for Mandatory Field in Inspection Detail Screen while creating/editing an inspection

- Provide Accessibility information about Group Headers of Line Items in Inspection Detail Screen while creating/editing an inspection

Exceptions are captured in the bug - 29530482,  31413985,  31413955, 31432845, 31432819, 31432840, 31403423, 31444647

1.3.2 Meaningful Sequence(Level A)Partially Supports

The product was tested for:

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

- Sequence is not maintained and focus is not present on the popup when
user clicks on status dropdown in inspection details screen

 - Accessibility focus order is not maintained in the Web View when user logs in using 2SV credentials.

Exceptions are captured in the bug - 31001164, 31403418, 31414204,  31432851

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


- Accessibility information is not provided for the  download button in the drawings screen which can be used by the user to download the drawing
-  Accessibility information is not provided when the download button is clicked in the drawings screen and the  change in the icon state is not indicated to the user
- Accessibility information is not  provided when pull to refresh is in progress in drawings list

- Accessibility information is not  provided when pull to refresh is in progress in issues list

- Accessibility information is not  provided when pull to refresh is in progress in inspections list

The exceptions are  captured in Bug - 29530496,  31432864

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

The product was tested for 

  • Text fields which collect information about the user contain the appropriate autocomplete content attribute.
1.4.1 Use of Color(Level A)Partially Supports

The product is tested for 

  • Color is not used as the only visual means of conveying information

- Accessibility information should be provided for the export icon  in disabled state which appears in Inspection Detail Screen when user edits an inspection.
Accessibility information should be provided for the mandatory field which appears in Inspection Detail Screen when user creates/edits an inspection
- Accessibility information should be provided for the mandatory fields for Custom project fields which appears in Issue Detail Screen when user creates/edits an issue

- Accessibility information should be provided for the "Notes" icon about the state, whether Line item has comments added, which appears in Inspection Details screen while user creates/edit an inspection

- Accessibility information should be provided for the "Create Issue" icon about the state, whether Line item has issue created, which appears in Inspection Details screen while user creates/edit an inspection

- Accessibility information should be provided for the "Photo" icon about the state, whether Line item has photo attached, which appears in Inspection Details screen while user creates/edit an inspection

The exceptions are captured in Bug -   31432872

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

- In inspection details screen, text contrast ratio is not  maintained for Status Drop down
- In Inspection details screen,text contrast ratio is not  maintained for Response fields

- In Inspection Properties screen,text contrast ratio is not  maintained for Inspection Number Field

- In Issues Details Screen, text contrast ratio is not  maintained for Add Photos Button

Exceptions are captured in Bug -  29530522 and Bug - 31041505, 31432905, 31432894, 31432888, 31432877

 

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 Zoom feature provided by Android OS.
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Images of text are not used.
1.4.10 Reflow (Level AA)Not Applicable

Due to mobile devices not supporting reflow, this criteria can not be met.

1.4.11 Non-text Contrast (Level AA)Partially Supports

The product was tested for:

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

- In inspection details screen, text contrast ratio is not  maintained for Status Drop down
- In Inspection details screen,text contrast ratio is not  maintained for Response fields

- In Inspection Properties screen,text contrast ratio is not  maintained for Inspection Number Field

- In Issues Details Screen, text contrast ratio is not  maintained for Add Photos Button

Exceptions are captured in Bug -  29530522 and Bug - 31041505, 31432905, 31432894, 31432888, 31432877

1.4.12 Text Spacing (Level AA)Not Applicable

The product was tested for:

  • Markup languages aren't used to generate the user interface
1.4.13 Content on Hover or Focus (Level AA)Not Applicable

The product was tested for

  • There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)Partially Supports

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.

- The content in the location filter is reading out as "greater than " instead of "in"
- Dragging the pane to create a new issue in drawing details is not possiblefrom bluetooth keyboard

- Status. of the issue  is not being read in the photo details screen

Exceptions are mentioned in the bug - 29530588 , 31529114

2.1.2 No Keyboard Trap (Level A)Supports

The product 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 using the built-in TalkBack and Switch Control assistive technologies
2.1.4 Character Key Shortcuts (Level A)Supports

This product has tested for: 

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

The product was tested for:

  • Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)Not Applicable

The product was tested for:

  • There is no moving, blinking, scrolling or auto updating 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

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

The product was tested for:

  • The text of links  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)Partially 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.

 - Provide Accessibility information for Location Field in Inspection Detail Screen

 - Provide Accessibility information for Mandatory Field in Inspection Detail Screen while creating/editing an inspection.

Provide Accessibility information about Group Headers of Line Items in Inspection Detail Screen while creating/editing an inspection

The exceptions are mentioned in bug - 31403395, 31414144,  31414036, 31432927

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
2.5.1 Pointer Gestures (Level A)Supports

This product was tested for

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

This product was test 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
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.
2.5.4 Motion Actuation (Level A)Not Applicable

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

  • Application is in the locale/language of the underlying platform
3.1.2 Language of Parts(Level AA)Supports

The product was tested for:

  • There are no parts where the language differs from that of the application/platform.
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)Partially 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.

Exceptions are raised as part of bug 31432979

When selecting mail type, mail create screen gets added with some fields, and this change is not informed to the user

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)Partially 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.

- Accessibility information should be provided about an error which occurs when an inspection is edited or created in Inspection Details Screen.

The exceptions are captured in the following bug - 31143553 

3.3.2 Labels or Instructions (Level A)Partially Supports

The product was tested for:

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

    Exceptions are captured in 31521352

Accessibility  information is not notified to the user when instruction of Custom Textarea/Text field is displayed  while  creating/editing issue in Issue Details Screen

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

The product was tested for:

  • 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 elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids
4.1.2 Name, Role, Value (Level A)Partially Supports

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

Accessibility information should be provided about the state of  the Navigation icon which appears in List screen while creating/editing inspection

Accessibility information should be provided about the state(disabled) of  the Inspection item in List Screen while creating/editing inspection

Accessibility information should be provided about the state(disabled) of  the Issue  item in List Screen while creating/editing issue screens

Accessibility information should be provided about the state(disabled) of  the Drawing item in List Screen while creating/editing Drawing screens

The exceptions are captured in the bug - 29533375, 31403386

4.1.3 Status Messages (Level AA)Partially Supports

This product has not yet been evaluated for this criteria

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

Exceptions are captured under 31400609, 31570392

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 FeaturesSupports

The product was tested for:

  • Does not disrupt platform 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 PreferencesPartially Supports

The product was tested for:

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

1. Application do not respond correctly to large font settings in Acknowledgement screen

2. Application do not respond correctly to large font settings for Inspection number in  inspection list screen

3. High contrast setting are distorting images in the drawing list screen. 

The exceptions are captured in the bug -  29530761,  31432983

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

The product documentation does not provide information on  accessibility and compatibility features as required by the hardware and software guidelines as of now.

The information has been captured in the bug with bug id 29629514

However, Aconex provides web-based documentation that covers product functionality at https://help.aconex.com/oracle-aconex-mobile.

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 FeaturesSupports

Aconex provides web-based documentation that covers product functionality at https://help.aconex.com/oracle-aconex-mobile. To ask questions or report issues, https://help.aconex.com/contact-us contains information by which users can communicate via voice/phone or electronically with Aconex Support.

603.3 Accommodation of Communication NeedsSupports

Aconex provides web-based documentation that covers product functionality at https://help.aconex.com/oracle-aconex-mobile. To ask questions or report issues, https://help.aconex.com/contact-us contains information by which users can communicate via voice/phone or electronically with Aconex Support.

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.