Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Blockchain Platform Cloud Service 22.2.1

Product Description:

Oracle Blockchain Platform is Oracle Cloud Infrastructure(OCI) hosted Blockchain as a service, which gives you a pre-assembled platform for building and running smart contracts and maintaining a tamper-proof distributed ledger.

Oracle Blockchain Platform is a network consisting of validating nodes (peers) that update the ledger and respond to queries by executing smart contract code the business logic that runs on the blockchain. External applications invoke transactions or run queries through client SDKs or REST API calls, which prompts selected peers to run the smart contracts. Multiple peers endorse (digitally sign) the results, which are then verified and sent to the ordering service. After consensus is reached on the transaction order, transaction results are grouped into cryptographically secured, tamper-proof data blocks and sent to peer nodes to be validated and appended to the ledger. Service administrators can use the Oracle Blockchain Platform web console to configure the blockchain and monitor its operation.

Date:

03-Jun-2022

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

PDF, mobi formats, ePub formats
Oracle Help Center, Self-Publishing Version

Oracle Blockchain Platform Console is based on Oracle JET, OUI-react and OUI-savant and TypeScript. It inherits the accessibility support from the technologies.

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/Guideline	Included In Report
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	Yes

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 web interface 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 defect was found in Web interface test: BUG - 34156869 Service Console -Image elements should have alternate text or a role of none or presentation The Non-web interface 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 CLI was tested for: Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used Images 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 Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The product has no multimedia.
1.3.1 Info and Relationships (Level A)	Partially Supports	The web interface 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 Following defects were found: BUG - 34099337 CP Console _ Landmarks must have a unique role or role/label/title (i.e. accessible name) combination BUG - 34102491 CP Console_Table headers in a data table must refer to data cells The Non-web interface 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 CLI was tested for: Headings follow standard text patterns for rendering headings Lists follow standard text patterns for rendering lists Paragraphs follow standard text patterns for rendering paragraphs Tables follow standard text patterns for rendering tables 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)	Supports	The web interface was tested for: The sequence of elements in the DOM matches a logical reading sequence The Non-web interface was tested for: The correct reading sequence is discernible The CLI was tested for: The correct reading sequence is discernible when output is rendered to a file or screen The documentation was tested for: The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	The web interface was tested for: Instructions provided which refer to graphics included a reference to the text alternative of the graphic The Non-web interface 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 CLI 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 interface was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The NonWeb GUI was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The CLI was tested for: Text display orientation in a command line user interface is based on the ability of the terminal application used. The documentation 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)	Not Applicable	Web interface: There are no text fields that collect information about the user. NonWeb GUI: There are no text fields that collect information about the user. CLI: There are no text fields that collect information about the user. Documentation: There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)	Supports	The web interface was tested for: Information conveyed by color is available in text The Non-web interface was tested for: Information conveyed by color is available in text The CLI was tested for: Information conveyed by color is available in text The documentation was tested for: Information conveyed by color is available in text
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	The web interface 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 defect was found in Web interface test: BUG - 34098683 Cp Console _Element must have sufficient color contrast Tags and text issues seen in details page of Blockchain platform having less than minimum contrast ratio for accessibility Contrast of text is not as per guideline for all the non editable text in scale operations of Blockchain platform Contrast of text is not as per guideline for workrequest image and status in workrequest page The Non-web interface 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 CLI was tested for: Text has 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 texts and images of text have a contrast ratio of at least 4.5:1
1.4.4 Resize text(Level AA)	Supports	The Web interface was tested for: Text can be resized up to 200% without loss of content or functionality The NonWeb GUI was tested for: Text resizes up to 200% using the platform's built-in magnifier or zoom feature The CLI was tested for: Text can be resized up to 200% without loss of content or functionality when rendered in a GUI-based terminal application that supports text rendering sizes up to 200% larger than normal The documentation was tested for: Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text(Level AA)	Supports	The Web interface was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential The NonWeb GUI was tested for: Images of text are not used The CLI was tested for: Images of text are not used The documentation was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
1.4.10 Reflow (Level AA)	Partially Supports	The Web interface 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 following defect was found: BUG - 34102816 CP Console_"Terminate" option from the drop down getting removed while at zoom 125% Menu options (Dashboard,Network,Nodes,Channel, Chaincodes,Developer Tools) getting lost while at zoom 125% Hamburger menu getting lost in Nodes tab while at zoom 300% and at Aspect ratio 1920X1080 or 1280X1024 Rich History Configuration page content getting lost while at zoom level 250% Create new channel page header lost while at zoom level 200% Deploy chaincode page content getting lost while at Zoom level 400% Contents are getting overlapped in Developers Tool tab while at Zoom level 300% BUG - 34103021 Service Console_Page Contents are getting lost with different zoom level The NonWeb GUI and CLI were tested for: 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 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 interface was tested for: The visual presentation of the User Interface Components and Graphical Objects have a contrast ratio of at least 3:1 The following defect was found: BUG - 34098683 Cp Console _Element must have sufficient color contrast Contrast of Non-text is not as per guideline for workrequest image and status in workrequest page The NonWeb 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 The CLI was tested for: Non-text characters and Graphics are not used The documentation was tested for: The visual presentation of the User Interface Components and Graphical Objects have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Partially Supports	The Web interface 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 NonWeb GUI was tested for: Text is not rendered using markup languages. The CLI was tested for: Text is not rendered using markup languages. The documentation was tested for: 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
1.4.13 Content on Hover or Focus (Level AA)	Supports	The Web interface was tested for: Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing. Dismissable :The content can be dismissed without moving the pointer or keyboard focus 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 NonWeb GUI was tested for: Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing. Dismissable :The content can be dismissed without moving the pointer or keyboard focus 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 CLI was tested for: There is no content that appears on hover or 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 intereface 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 defects were found BUG - 34103630 Service Console_Elements are not getting highlighted when focused with 'Tab' Key Drop down section in network and nodes tab are not getting highlighted Drop down parameters in Install and Deploy chaincode is not getting highlighted BUG - 34095046 Service Console_ Navigation orderer is not correct for refresh and collapse buttons The NonWeb 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 CLI was tested for: Ability to perform functions from the keyboard only Proper operation of unique keystrokes, including those listed in the product documentation The documentation 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
2.1.2 No Keyboard Trap (Level A)	Supports	The Web interface 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 NonWeb GUI 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 CLI 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
2.1.4 Character Key Shortcuts (Level A)	Partially Supports	The Web interface was tested for: Single character keyboard shortcuts can be turned off. Single character keyboard shortcuts can be remapped. Single character keyboard shortcuts are only active when that component has focus The following defect was found BUG - 34140214 : Character key shortcuts could not be turned off or remapped The NonWeb GUI was tested for: Single character keyboard shortcuts can be turned off. Single character keyboard shortcuts can be remapped. Single character keyboard shortcuts are only active when that component has focus. The CLI was tested for: There are no single character keyboard shortcuts The documentation was tested for: There are no single character keyboard shortcuts
2.2.1 Timing Adjustable(Level A)	Supports	The Web interface was tested for: Time limits used are part of a real-time event, or an essential activity The NonWeb GUI and CLI were tested for: Time limits are not used The documentation was tested for: Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Not Applicable	The Web interface was tested for: There are no moving, blinking or auto-scrolling information is included in the product. The NonWeb GUI and CLI were tested for: There are no moving, blinking or auto-scrolling information is included in the product. The documentation was tested for: No moving, blinking or auto-scrolling information is included in the documentation
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The Web interface was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz The NonWeb GUI and CLI were 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
2.4.1 Bypass Blocks(Level A)	Supports	The web interface was tested for: Structure and hierarchy are marked up with Header elements outside of repetitive navigation links NonWeb GUI and CLI: Not Applicable. 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 documentation was tested for: Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
2.4.2 Page Titled(Level A)	Supports	The Web interface was tested for: Pages have a meaningful title specified in the TITLE element The NonWeb GUI and CLI were tested for: The name of the software application is meaningful. The documentation was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports	The Web interface was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence The NonWeb GUI was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence The CLI was tested for: Keyboard focus is not used The documentation was 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 interface was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose The NonWeb GUI 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 CLI was tested for: Links are not used in the product The documentation was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)	Supports	The Web interface was tested for: Quick links for instant access in a flattened, non-hierarchical form, and access via content links on a given page to meaningful items which navigate to other pages Page contains links that enable reaching other pages NonWeb GUI and CLI: 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 interface was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The NonWeb GUI was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The CLI was tested for: Headers describe the topic or purpose of the content below them Labels are not used The documentation 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 Web interface was tested for: Visual indication of the location of the focus The NonWeb GUI and CLI were tested for: Visual indication of the location of the focus The documentation was tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Not Applicable	The Web interface was tested for There are no multipoint or path-based gesture actions. The NonWeb GUI was tested for There are no multipoint or path-based gesture actions. The CLI 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.
2.5.2 Pointer Cancellation (Level A)	Supports	The Web interface 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 NonWeb GUI 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 CLI was tested for: There are no single pointer operations 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
2.5.3 Label in Name (Level A)	Supports	The Web interface was tested for: Labels that contain text or images of text contain the visually presented text. In the case of graphs and their text and text images, screen reader mode will produce and allow access to the corresponding text The NonWeb GUI was tested for: Labels that contain text or images of text contain the visually presented text. In the case of graphs and their text and text images, screen reader mode will produce and allow access to the corresponding text The CLI was tested for: User interface components are not used The documentation was tested for: Labels that contain text or images of text contain the visually presented text.
2.5.4 Motion Actuation (Level A)	Not Applicable	The Web interface was tested for There are no functions that require motion of the device. The NonWeb GUI was tested for There are no functions that require motion of the device. The CLI 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.
3.1.1 Language of Page(Level A)	Supports	The Web interface was tested for: The "lang" attribute is properly set for a given HTML page. The human language conforms to that set for the platform (OS) or the host system (programmatically determinable from that system) The NonWeb GUI and CLI were tested for: The NonWeb GUI and CLI 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 interface was tested for: Proper use of the “lang” attribute for text passages that are in a different language than that of the page The NonWeb GUI and CLI were tested for: Not Applicable. The NonWeb GUI and CLI 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 interface 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 NonWeb GUI 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 CLI was tested for: Keyboard focus is not used 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
3.2.2 On Input(Level A)	Supports	The Web interface 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 NonWeb GUI 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 CLI 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 keyboard focus, or the spawning of a new window The documentation was tested for: Changes in the value of user interface components do 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 interface 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. NonWeb GUI: 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 CLI: 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 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.
3.2.4 Consistent Identification(Level AA)	Supports	The Web interface was tested for: Images and controls are used and identified consistently throughout the product The NonWeb GUI was tested for: Images and controls are used and identified consistently throughout the product The CLI was tested for: Images and controls are not used The documentation was tested for: Images and controls are used and identified consistently throughout the documentation
3.3.1 Error Identification(Level A)	Supports	The Web interface 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 NonWeb GUI 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 CLI 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: The documentation does not have input fields, except for the Search field
3.3.2 Labels or Instructions (Level A)	Supports	The Web interface was tested for: Labels or instructions are provided when the product requires user input The NonWeb GUI was tested for: Labels or instructions are provided when the product requires user input The CLI was tested for: Labels or instructions are provided when the product requires user input The documentation was tested for: The documentation does not require user input, except for Search field
3.3.3 Error Suggestion (Level AA)	Supports	The Web Interface was tested for: Where suggestions for fixing an input error are known, they are provided to the user The NonWeb GUI was tested for: Where suggestions for fixing an input error are known, they are provided to the user The CLI was 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	The Web interface 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 NonWeb GUI 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 CLI was tested for: 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.
4.1.1 Parsing(Level A)	Supports	The Web interface 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 The NonWeb GUI was tested for: Markup languages aren't used to generate the user interface The CLI was tested for: Markup languages aren't used to generate the user interface 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
4.1.2 Name, Role, Value (Level A)	Supports	The Web interface 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 The NonWeb 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 The CLI was tested for: User interface components are not used
4.1.3 Status Messages (Level AA)	Supports	The Web intereface was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus The NonWeb GUI and CLI were 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 Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The 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 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Supports	The Web interface was tested for: The Web application only uses technologies that run in a browser and are not a plugin/applet The NonWeb and CLI were tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts The documentation was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Supports	The Web interface was tested for: The Web application only uses technologies that run in a browser and are not a plugin/applet The NonWeb GUI and CLI were tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor The documentation was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	Accessibility features information for Oracle Blockchain Cloud Service is found in Oracle Accessibility Guide for Oracle Cloud Services; 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 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable	Product documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle 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 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.