Oracle Accessibility Conformance Report

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

Following defect was found:

• Bug 38187149 - Form elements denoted with '?' on the Service Console UI landing page are missing labels.

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

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

Following defects were found:

• Bug 37330798 - Landmarks is missing unique role or role/label/title to allow screen readers navigate properly for Resources section in 'Blockchain Platform Details' and 'Work Request Details' page of controlplane console UI.

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

The Web GUI and Documentation were tested for:

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

Following defect was found for Web GUI:

Bug 38193605 - Sequence of elements for certain attributes in the Service Console UI does not follow a logical reading order.

• Timstamp , refresh button and help icon are not in logical reading order for health section of nodes
• Refresh and collapse button are not in logical reading order for all the tab in service console

The Non-web GUI and CLI were tested for:

• The correct reading sequence is discernible when output is rendered to a file.

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 and CLI were tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, colour, 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, colour, or sound
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

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.

The CLI was tested for:

• Text display orientation in a command line user interface is based on the ability of the terminal application use

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

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

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

• Information conveyed by colour is available in text

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

Following defects were found for Web GUI:

• Bug 37358674 - Text contrast is less than minimum contrast ratio for the non editable text in 'Scale' operations of Blockchain platform
  • Defect Impacts - 'Scale' sidepanel in 'Blockchain Platform Details' page which is visible when 'Scale' action button is clicked on the page
  • Check box for MSP Id's in Organizations section in created channel form
  • Created channel form where Text under input field is not as per guideline
• Bug 38191583 - Contrast of text is not as per guideline for Few elements in service console
  • Below area affected with this
    • Refresh and expand/collapse button for all the tabs
    • Hamburger menu beside all the rows in all the tab
    • Text in Filter box present in all the tabs
    • Topology view under network tab and nodes tab
    • Text inside the input field of Rich History configuration
    • Service console url on address bar

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

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 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 customized or the particular image is essential

The Non-web GUI and CLI were tested for:

• Images of text are not used

The Web GUI 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 defects were found:

• Bug 37329812 - More Actions' dropdown button in the 'Blockchain Platform Details' page is lost/hidden when zoom is greater than 300%.
• Bug 38187507 - Horizontal scrollbars is missing in the Channel tab and Developer tools tab, making it impossible to view the complete content horizontally when the zoom level is set to 400%.
• Bug 38187248 - In the Service Console, content overlaps when the zoom level is set to 400%
  • Issues observed in Service Console UI:
    • Text Cut-Off in Developer Tools Tab : In the Developer Tools tab, the left-hand side menu text is horizontally cut off for all listed sections, including:
      • Samples
      • Application Development
      • Chaincode Development
      • Blockchain App Builder
    • Main Menu Options Missing : Main menu options disappear, impacting navigation.
    • Title Overlap : The "Blockchain" title gets overlapped with other UI elements.

The CLI were tested for:

• Text information can reflow with only one direction of scrolling when rendered in a GUI-based terminal application that supports text rendering sizes up to 400% larger than normal.

The Non-web ui 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

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

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

The CLI was tested for:

• Non-text characters and Graphics are not used

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

• Text is not rendered using markup languages.

The Documentation was tested for:

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

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

• There is no content that appears on hover or focus

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 Non-web GUI , CLI 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

The Web GUI, Non-web GUI and CLI 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

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

• There are no single character keyboard shortcuts

The Web GUI was tested for:

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

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

• Time limits are not used

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

• There is no moving, blinking, scrolling or auto-updating content.

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

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

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 and CLI were 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

The Web GUI and Documentation were tested for:

• Pages have a meaningful title specified in the TITLE elemen

The following defect was found for Web UI:

• Bug 38187386 - The HTML document of the Service Console UI landing page doesn't have descriptive title.

The Non-web GUI and CLI were tested for:

• The name of the software application is meaningful.

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

The CLI was tested for:

• Keyboard focus is not used

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

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

The CLI was tested for:

• Headers describe the topic or purpose of the content below them
• Labels are not used

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

• Visual indication of the location of the focus

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.

The CLI was tested for:

• Keyboard focus is not used

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

• There are no multipoint or path-based gesture actions

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

The CLI was tested for:

• There are no single pointer operations

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.

The CLI was tested for:

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

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

• There are no functions that require motion of the device

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

• There is no functionality that uses dragging movements

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.

CLI was tested for:

• The product does not contain interactive targets.

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.

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

• The Non-web 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.

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 and CLI were tested for:

• The Non-web 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

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

The CLI was tested for:

• Keyboard focus is not used

The Web GUI, Non-web GUI, CLI 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

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

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.

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

The Web GUI, Non-web GUI and CLI 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

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

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

The Web GUI , Non-web GUI and CLI 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

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

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

• There are no occurrences of information that the user needs to enter which has been previously entered.

The Web GUI, Non-web GUI and CLI 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

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 defects were found for Web GUI:

• Bug 38187649 - What's new dialog doesn't have accessible name

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

The CLI was tested for:

• User interface components are not used

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

The Web GUI was tested for:

• The Web application only uses technologies that run in a browser and are not a plugin/applet

The Non-web, CLI and Documentation were tested for:

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

The Web GUI was tested for:

• The Web application only uses technologies that run in a browser and are not a plugin/applet

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

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

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

Product documentation is in electronic format.