ACR: Oracle Blockchain Platform Enterprise Edition 26.3.1

Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

 Oracle Blockchain Platform Enterprise Edition 26.3.1

Product Description:

Oracle Blockchain Platform Enterprise Edition (OBPEE) provides an enterprise platform that enables customers to develop, deploy and manage blockchain networks and applications in their own data centers or in hybrid environments. OBPEE addresses enterprise customers' critical needs, including scalability, availability, privacy/confidentiality, supportability, usability, and the ability to integrate with existing applications.

Oracle Blockchain Platform Enterprise Edition is available for on-premises deployment. It includes an OBPEE Console to administer and monitor the blockchain network. It also includes a REST proxy enabling easy access to blockchain applications and networks through REST API's. In addition, OBPEE includes Blockchain App Builder, which consists of a Visual Studio Code Extension and command line tools. It enables developers to rapidly develop, testing and deployment of chaincodes locally and using remote Oracle Blockchain Platform deployments. Blockchain App Builder can be downloaded through the OBPEE Console's Development Tools tab.

The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the ACRs listed in the Dependent Products section for more information.

Report Date:

07-SEP-26

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

Dependent Products


This product interacts with or is built with the other Oracle products listed in this section. Click below to view information about the accessibility of these dependent products. Products listed are the versions available at the time of publication of this document; newer documents may be available that supersede these 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/

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.0Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.2Level 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.2 Report

Table 1 also documents conformance with:

Note: When reporting on conformance with the WCAG 2.2 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 Web GUI 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)
  • Controls have an associated name
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

The Non-Web GUI was tested for:

  • Images that convey information have meaningful alternative text
  • Images that are decorative are marked up
  • Information shown in complex images such as charts is also available in an alternative textual form
  • 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

The Documentation 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
  • 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
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 Web GUI was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
  • Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
  • Data tables specify SUMMARY or CAPTION
  • Layout tables use appropriate markup
  • Groups of components are marked up with their description
  • Style sheets are used only to change the layout and presentation on the screen

The following bugs were found in Web GUI

Bug 39852130 : Expand/Collapse button for the Operation list under the Activities tab should have discernible text for accessibility in Controlplane UI

Bug 39847012 : Multiple form elements in the Control Plane do not have associated labels

Bug 39749076 : Multiple form elements in the Besu Service Console do not have associated labels

Bug 39846995 : HTML header of the Control Plane includes a blank title element

Bug 39834225 : HTML header of Fabric Service console includes a blank title element

Bug 39781300 : Screen reader unable to read content of Pop ups and pages in Besu Service console

Bug 39775285 : Data Table under Node and Digital Asset tab of Besu service console does not have accessible text

The Non-Web GUI was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are marked as such where appropriate
  • List markup is used for marking up lists
  • Tables are marked as such, including row and column headers and table captions/summaries where appropriate
  • Groups of components are marked as such, with a description for the group

The Documentation was tested for:

  • Data tables specify SUMMARY or CAPTION
  • Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
  • Layout tables use appropriate markup
  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
1.3.2 Meaningful Sequence (Level A)Partially Supports

The Web GUI and Documentation were tested for:

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

The following bugs were found in Web GUI

Bug 32611562 : Navigation order is not correct for refresh and collapse buttons for all the tabs in Fabric Service Console

Bug 39848946 : Keyboard focus does not reach the Save button after completing the new configuration fields because the button is positioned before the input controls in the tab order

The Non-web GUI was tested for:

  • The sequence of elements presented by assistive technologies matches a logical reading sequence.
1.3.3 Sensory Characteristics (Level A)Supports

The Web GUI was tested for:

  • Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The Non-Web GUI 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
  • Instructions provided which refer to graphics included a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)Supports

The Web GUI, Non-Web GUI and Documentation were 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 Web GUI and Non-Web GUI were tested for:

  • Text fields which collect information about the user contain the appropriate autocomplete content attribute.

The Documentation was tested for:

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

The Web GUI, Non-Web GUI and Documentation were tested for:

  • Information conveyed by color is available in text
1.4.2 Audio Control (Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Partially Supports

The Web GUI, Non-web GUI and Documentation were 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 following bugs were found in Web GUI

Bug 39776441 : Some text in the Besu Service Console does not meet the required minimum 4.5:1 contrast ratio

1.4.4 Resize text (Level AA)Supports

The Web GUI and Documentation were tested for:

  • Text can be resized up to 200% without loss of content or functionality

The Non-web GUI was tested for:

  • Text resizes up to 200% using the platform's built-in magnifier or zoom feature
1.4.5 Images of Text (Level AA)Supports

The Web GUI and Documentation were tested for:

  • Images of text are only used when the technology can't create the desired visual presentation, the image can be customised or the particular image is essential

The Non-Web GUI was tested for:

  • Images of text are not used
1.4.10 Reflow (Level AA)Partially Supports

The Web GUI and Documentation were 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

Following bug was found in Web GUI

  • Bug 32575456 Some content is lost in Controlplane UI when zooming to 400%

The Non-Web GUI was tested for:

  • Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content
1.4.11 Non-text Contrast (Level AA)Partially Supports

The Web GUI and Documentation were tested for:

  • The visual presentation of the User Interface Components and Graphical Objects have a contrast ratio of at least 3:1

Following bug was found in Web GUI

  • Bug 32574519 Topology graph, status, and health images in fabric service console do not meet the required minimum 3:1 contrast ratio

The Non-Web GUI was tested for:

  • The visual presentation of the User Interface Components has a contrast ratio of at least 3:1
  • Graphics is not used
1.4.12 Text Spacing (Level AA)Supports

The Web GUI and Documentation were 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 Non-Web GUI was tested for:

  • Text is not rendered using markup languages
1.4.13 Content on Hover or Focus (Level AA)Partially Supports

The Web GUI and Non-Web GUI were tested for:

  • Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
  • Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
  • Persistent: the additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid

The following bugs were found in Web GUI

Bug 39848682 : Tooltips for Rich History Status, ACLs, and Wallet Package File button are not visible when navigating with keyboard focus

The Documentation was tested for:

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

The Web GUI was tested for:

  • Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
  • Proper operation of unique keystrokes and access keys, including those listed in the product documentation
  • The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

The following bugs were found in Web GUI

Bug 39843422 : Keyboard shortcuts are not working to focus on few elements in OBPEE Control Plane

Bug 39773946 : Unable to move between tabs using Arrow Keys: Dashboard, nodes, Explorer, Contracts, Digital Assets, Developer Tools ,Accounts and Logs in Besu Service console

Bug 39749148 : Keyboard navigation is not working for some of the web elements of Fabric Service Console

Bug 32408780 : Cannot deploy a chaincode using keyboard in Fabric Service Console

Bug 32398017 : Cannot input custom time frame using keyboard only in Fabric Service Console

Bug 36433671 : As a keyboard user I have to arrow down more than once to click on the next option of hamburger menu under nodes tab in Fabric Service Console

The Non-Web GUI and Documentation were tested for:

  • Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
  • Proper operation of unique keystrokes and access keys, including those listed in the product documentation
2.1.2 No Keyboard Trap (Level A)Supports

The Web GUI, Non-Web GUI and Documentation were 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
2.1.4 Character Key Shortcuts (Level A)Supports

The Web GUI, Non-Web GUI and Documentation were tested for:

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

The Web GUI was tested for:

  • Time limits used are part of a real-time event, or an essential activity

The Non-web GUI and Documentation were tested for:

  • Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)Supports

The Web GUI, Non-Web GUI and Documentation were tested for:

  • There is no moving, blinking, scrolling or auto-updating content.
2.3.1 Three Flashes or Below Threshold (Level A)Supports

The Web GUI, Non-Web GUI and Documentation were 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 Web GUI and Documentation were tested for:

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

The Non-web GUI was tested for:

  • 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 Web GUI and Documentation were tested for:

  • Pages have a meaningful title specified in the TITLE element

The Non-Web GUI was tested for:

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

The Web GUI, Non-Web GUI and Documentation were tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context) (Level A)Supports

The Web GUI, Non-Web GUI and Documentation were 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

The Web GUI was tested for:

  • Pages are contained in a "site map."
  • Pages can be found using the provided "search" function.
  • Pages are in a site table of contents.
  • Pages are fully inter-linked to each other.
  • Page contains controls that enable reaching all pages.

The Non-web GUI  tested for:

  • 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 does not apply.

The Documentation was tested for:

  • Pages can be found using the provided "Search" function.
  • Pages are in a site table of contents.
  • Pages contain controls that enable reaching other pages.
2.4.6 Headings and Labels (Level AA)Supports

The Web GUI, Non-Web GUI and Documentation were 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 Web GUI, Non-Web GUI and Documentation were tested for:

  • Visual indication of the location of the focus
2.4.11 Focus Not Obscured (Level AA)Supports

The Web GUI , Non-web UI and Documentation were tested for:

  • The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.
2.5.1 Pointer Gestures (Level A)Not Applicable

The Web GUI , Non-web GUI and Documentation were tested for:

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

 The Web GUI , Non-web GUI and Documentation were 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 Web GUI , Non-web GUI and Documentation were 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 Web GUI, Non-web GUI and Documentation were tested for

  • There are no functions that require motion of the device
2.5.7 Dragging Movements (Level AA)Supports

The Web GUI, Non-Web GUI and Documentation were tested for:

  • There is no functionality that uses dragging movements
2.5.8 Target Size (Minimum) (Level AA)Partially Supports

The Web GUI and Non-Web GUI were tested for:

  • Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.
  • The function can be achieved through a different control in the same software that meets this criterion.

Following bug was found in Web GUI

Bug 39755455 : Links in the Digital Asset and Developer Tools tabs of the Fabric Service Console do not have sufficient size and spacing

The Documentation was tested for:

  • Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.
  • The function can be achieved through a different control in the same software that meets this criterion.
  • The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.
3.1.1 Language of Page (Level A)Supports

The Web GUI was tested for:

  • The "lang" attribute is properly set for a given HTML page.

The Non-web GUI was tested for:

  • The Non-web GUI run in English, therefore it is expected that the user is also running their assistive technology in English, where applicable

The Documentation was tested for:

  • Properly set "lang" attribute for a given page.
3.1.2 Language of Parts (Level AA)Supports

The Web GUI was tested for:

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

The Non-web GUI was tested for:

  • The Non-web GUI run in English, therefore it is expected that the user is also running their assistive technology in English, where applicable

The Documentation was tested for:

  • Proper use of the “lang” attribute for text passages that are in a different language than that of the page
3.2.1 On Focus (Level A)Supports

The Web GUI, Non-web GUI and Documentation were tested for:

  • When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.2 On Input (Level A)Supports

he Web GUI, Non-web GUI and Documentation were tested for:

  • Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.3 Consistent Navigation (Level AA)Supports

The Web GUI and Documentation were 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 Non-web GUI was tested for:

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

The Web GUI, Non-web GUI and Documentation were tested for:

  • Images and controls are used and identified consistently throughout the product or documentation
3.2.6 Consistent Help (Level A)Supports

The Web GUI and Non-web GUI were tested for:

  • Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

The Documentation was tested for:

  • None of the following help mechanisms exist: Human contact details, human contact mechanisms, self-help options, automated contact mechanisms.
3.3.1 Error Identification (Level A)Supports

The Web GUI and Non-web GUI were tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

The Documentation was tested for:

  • The documentation does not have input fields, except for the Search field
3.3.2 Labels or Instructions (Level A)Supports

The Web GUI, Non-web GUI and Documentation were tested for:

  • Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)Supports

The Web GUI and Non-web GUI were tested for:

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

The Documentation was tested for:

  • The documentation does not require user input, except for the Search field
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)Supports

he Web GUI and Non-web GUI were 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 finalised

The Documentation was tested for:

  • The documentation does not require user input that modifies user controllable data.
3.3.7 Redundant Entry (Level A)Supports

The Web GUI, Non-web GUI and Documentation were tested for:

  • There are no occurrences of information that the user needs to enter which has been previously entered.
3.3.8 Accessible Authentication (Minimum) (Level AA)Supports

The Web GUI and Non-web GUI were tested for:

  • The product supports password entry by password managers.
  • The product supports copy and paste while authenticating.

The Documentation was tested for:

  • Authentication is not required
4.1.1 Parsing (Level A)Not ApplicableThis criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)Partially Supports

The Web GUI and Documentation were tested for:

  • HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
  • Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
  • Custom controls have appropriate roles specified using the role attribute
  • Custom controls have a meaningful programatically exposed name
  • Frames have a meaningful title specified in the title attribute

Following bugs were found in Web GUI:

Bug 39847328 : Few of the image elements do not have alternate text or role in Controlplane UI

Bug 39749044 : Few of the image elements do not have alternate text or role in Fabric service console

Bug 39749030 : Aria dialog and alert dialog should have accessible name in Fabric Service console

Bug 39906554: Under Wallet tab, Div tag is nested in controlplane console

The Non-web GUI was tested for:

  • User interface components have a programmatically associated name and role
  • State information, properties, and values are programmatically exposed for user interface components
4.1.3 Status Messages (Level AA)Supports

The Web GUI was tested for:

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

The Non-web GUI was tested for:

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

The Documentation was tested for:

  • There are no status messages

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.

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 Non-web GUI 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 PreferencesSupports

The Non-web GUI was tested for:

  • Responds to 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.

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 features information for Oracle Blockchain Cloud Service is found in Oracle Accessibility Guide for Oracle Cloud Services; Part Number E87816-04: https://docs.oracle.com/en/cloud/accessibility/accessibility-oracle-autonomous-blockchain-cloud-service.html#GUID-FC8D168C-6F5C-4AB2-AD04-FB324ABF6EF4

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.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicable Standards/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.