Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Middleware Extensions for Applications Visual Information Builder updated3 11.1.1.12

Product Description:

The Visual Information Builder is a component that allows users to manage business rules that will be executed in the Oracle Business Rules rule engine.

The user interface consists of 2 different views:

- Rule Management page

- Rule Creation page

The Rule Management page displays a set of cards representing the rules in a particular rule set. Users can select a rule to see more details in a pop-up Info Dialog, and make changes to the rule settings such as rule name, activation settings, priority, etc. The user can select the Edit action on a rule, or use the Create New Rule button to go to the Rule Creation page where the logic of a rule is defined.

The Rule Creation page is where the logic for the rule is defined. On the left is a tree which shows a list of available business objects, attributes, and actions that can be used in the rule. Most of the screen is the rule canvas, where the logic of the rule is put together. The canvas displays the logic of the rule as a graph. The high level rule logic is represented as a series of IF and DO blocks, which are linked together to form logical paths such as IF this THEN IF that THEN DO my action. Inside each IF and DO block, users can create conditions and actions. The direction of the links between conditions (horizontal versus vertical) indicates that a set of conditions is meant to be evaluated with the OR operator versus the AND operator. Labels are given to each of these links to clearly indicate these relationships as well.

Navigation through the Rule Management page and through the Rule Creation page can be performed using the keyboard (arrow keys, enter key, etc.) and all parameters to the conditions and actions are provided through text fields. When a condition or action is created, it is displayed as a node in the graph with a textual summary of the condition or action.

Date:

29-Mar-2018

Archive Note:

This VPAT applies to only version 11.1.1.12 prior to 21-Feb-2020. It does not apply to any versions of Oracle Middleware Extensions for Applications Visual Information Builder after this. This VPAT has been superseded by Oracle Middleware Extensions for Applications Visual Information Builder updated3.1 11.1.1.12.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

ScreenReader mode. When ScreenReader mode is turned on, the tree and the canvas on the Rule Creation page do not respond to clicks or the Enter key. (bug 19701497)

Users can accomplish the same functionality by using the Oracle Business Rules (OBR) interface directly.

Instructions on setting accessibility options can be found in the "Fusion Middleware Web User Interface Developer's Guide for Application Development Framework" under the section "Accessibility Support Guidelines at Sign-In".

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.

ADF Faces Rich Client Components (output of JDeveloper), 11g R1 Fusion Apps updated3 Rel11

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.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	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.
Supports with Exceptions: 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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	The product 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 Titles for Objects and Applets are provided Controls have an associated name 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	No Pre-recorded audio-only or video-only content is being used
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	No Pre-recorded video content is being used
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	No pre-recorded video is being used
1.2.4 Captions (Live) (Level AA)	Not Applicable	No live audio content in video is being used
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	No pre-recorded video is being used
1.3.1 Info and Relationships (Level A)	Supports	The product was tested for: User interface component labels are associated with the fields they are labeling Headings are encoded with HTML heading tags 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
1.3.2 Meaningful Sequence(Level A)	Supports	The product was tested for: The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	The product was tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound Instructions provided which refer to graphics included a reference to the text alternative of the graphic
1.4.1 Use of Color(Level A)	Supports	The product was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)	Not Applicable	No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)	Supports with Exceptions	The product was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 Exceptions: The borders of the buttons to add new THEN or ELSE clauses are not shown when using high contrast mode. (bug 22010848) When adding a new condition or action, the rest of the graph (in the background) is no longer visible when using high contrast mode in Chrome. (bug 19546601) Text fields in the Condition and Action dialogs of the Rule Creation page have contrast ratios of 3.1:1. (bug 22606677) The condition dialogs of the rule creation page use spinner components to edit numerical values. When using high contrast mode the arrows of the spinner are hard to read. (bug 20803464)
1.4.4 Resize text(Level AA)	Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text(Level AA)	Supports	The product 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
2.1.1 Keyboard(Level A)	Supports with Exceptions	The product 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) Exceptions: (bug 18997283) It is not possible to delete an entire IF or DO block using the keyboard. Users can delete the contents of the block using the keyboard.
2.1.2 No Keyboard Trap (Level A)	Supports	The product 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.2.1 Timing Adjustable(Level A)	Not Applicable	Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Not Applicable	There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Not Applicable	No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks(Level A)	Not Applicable	This is a component which is embedded into an application's web page, and so does not include web pages of its own.
2.4.2 Page Titled(Level A)	Not Applicable	This is a component which is embedded into an application's web page, and so does not include web pages of its own.
2.4.3 Focus Order(Level A)	Supports with Exceptions	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions: (bug 22922665) - If the user is editing the parameters of an action and then chooses a different action, a prompt will appear asking the user to confirm. After selecting OK, the focus does not return to the action dialog. The user must tab back to the dialog himself. (bug 20026015) - When selecting a condition with the keyboard in order to create a group, the focus of the checkmark is lost. Pressing the down arrow restores focus. (bug 23174338) - After closing the Condition or Action dialog, the focus is not returned to the rule canvas. The user must tab back to the canvas himself. (bug 24323353) - In the Rule Management page, the Information dialog has an X button on the top right of the dialog to close it. The user can tab to this button, but the focus is not visible.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product 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
2.4.5 Multiple Ways(Level AA)	Not Applicable	This is a component which is embedded into an application's web page, and so does not include web pages of its own.
2.4.6 Headings and Labels(Level AA)	Supports	The product was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)	Supports with Exceptions	The product was tested for: Visual indication of the location of the focus Exceptions: (bug 19669846) - In the Rule Management page, there is always an indicator of which rule has focus. However, in some browsers this indicator is not as clear as in others. In Chrome the indicator is clearly visible around the border of the rule. In Firefox the indicator is visible around the border of the rule, but appears as a dashed line. In IE, the indicator is only visible around the header of the rule and appears as a dashed line. (bug 24323353) - In the Rule Management page, the Information dialog has an X button on the top right of the dialog to close it. The user can tab to this button, but the focus is not visible.
3.1.1 Language of Page(Level A)	Not Applicable	This is a component which is embedded into an application's web page, and so does not include web pages of its own.
3.1.2 Language of Parts(Level AA)	Supports	The product was tested for: Proper use of 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 product was tested for: When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.2 On Input(Level A)	Supports with Exceptions	The product 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 Exceptions: (bug 22922665) - If the user is editing the parameters of an action and then chooses a different action, a prompt will appear asking the user to confirm. After selecting OK, the focus does not return to the action dialog. The user must tab back to the dialog himself. (bug 20026015) - When selecting a condition with the keyboard in order to create a group, the focus of the checkmark is lost. Pressing the down arrow restores focus. (bug 23174338) - After closing the Condition or Action dialog, the focus is not returned to the rule canvas. The user must tab back to the canvas himself.
3.2.3 Consistent Navigation(Level AA)	Supports with Exceptions	The product 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 Exceptions: (bug 19669846, 20703380) - Currently all navigational mechanisms are the same with the exception that our Rule Management page uses "enter" to activate the object with focus, whereas the Rule Creation page uses the spacebar to do the same.
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Supports	The product was tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)	Supports	The product was tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Supports	The product was tested for: Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The product was tested for: Submissions can be reversed by the user Data is checked for input errors with an opportunity for the user to correct them Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)	Supports	The product 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 product was 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’.

2017 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	Not Applicable	The product is designed to be isolated from the underlying platform.
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	Not Applicable	The product is designed to be isolated from the underlying platform.
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	Not Supported	BUG 26175494 Product does not have Accessibility Features documentation
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.