Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Visual Builder Cloud Service Runtime 17.3

Product Description:

Visual Builder Cloud Service (VBCS) is a browser-based low code platform for rapidly creating and hosting business applications through a declarative user interface, without requiring the author to write code. For certain use cases, the author may choose to augment the behavior of applications by writing some code.

VBCS consists of a number of pages, wizards, and other browser-based tools that are used by the author to create and modify web applications. These components in combination are referred to in this document collectively as the VBCS "Designer". This document does not address accessibility of the Designer.

Applications created by a VBCS user (author) can be made visible/accessible to other users on the system through the built-in publishing system. Applications created with VBCS and hosted on VBCS servers are referred to in this document as VBCS Runtime applications, or simply "The Product". VBCS Runtime applications are designed to be accessible by end users. For certain features, though, the application author must take care to provide information to the application through the Designer interface to achieve specific accessibility features in the resulting application. The Designer assists the author with providing this information as needed.

The VBCS Designer itself is built on the Oracle JET framework. Furthermore, applications that are created and hosted on VBCS consist of HTML, JavaScript, and CSS resources which rely heavily on Oracle JET for the User interface.

Date:

30-Mar-2018

Archive Note:

This VPAT applies to only version 17.3. It does not apply to any versions of Oracle Visual Builder Cloud Service Runtime after this. This VPAT has been superseded by Oracle Visual Builder Runtime 19.1.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Oracle Help Center, Self-Publishing Version

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.

Oracle JavaScript Extension Toolkit (JET) 3.0.0

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/us/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: Author is able to provide attribute alt description and other elements on the page has his own description. Images that are decorative are marked up using ALT=”” or CSS background images Author is able to provide more details about table in the caption. The text itself from the caption is not visible, but it's still readable by screen readers. Controls have an associated name which can be set by the author. The product uses label to associate corresponding input elements. If non-text content is used, the application author can provide 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 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 with Exceptions	The Product 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 at the discretion of the application author. 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. During testing the following defects were discovered: Bug 24951794 - Confirmation messages are not read by screen reader. Confirmation messages contain supplemental information about user interactions (for example, a new row was created). These messages appear, then disappear automatically, but focus does not automatically shift to them, so a screenreader will not read these messages. Note that important messages (errors and warnings) do not auto-hide and are read by screen readers. No known workaround. Bug 24951742 - Error and warning messages are not easily discoverable. Errors and warning messages display in the page header. When using a screen reader, these messages will only be read when the user puts focus on the header. Workaround: Some browser plugins (eg, ChromeVOX for Chrome) read these messages at the right time when the message is displayed. Bug 24959178 - When fetching data based on input in a query or filter component for a table or list view a the user is informed through a pop-up that data is being fetched. However, when the fetching is complete, there's no indication to a screen reader that the data fetching is complete. No known workaround.
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. Application authors can control the presentation order of UI elements on the screen, and when they do, that is reflected in the DOM and in the navigation sequence.
1.3.3 Sensory Characteristics(Level A)	Not Applicable	The Product does not generate instructional text for how to operate on the content of the application.
1.4.1 Use of Color(Level A)	Not Applicable	Information is not conveyed using color
1.4.2 Audio Control(Level A)	Not Applicable	No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)	Supports	The product was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1
1.4.4 Resize text(Level AA)	Supports	The Product was tested for: Text can be resized in the browser up to 200% without loss of functionality
1.4.5 Images of Text(Level AA)	Not Applicable	Images of text are not used
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 The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms) During testing the following defects were discovered: Bug 25563998 - Users are able to navigate from a table or list in a parent page to a details or edit page using the provided menu action. When navigating back to the parent page (for example, using "Save and Close" or "Cancel", the focus is returned to the top of the parent page rather than the previously selected row. There's no known workaround at this time.
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. However, there is a session timeout of 4 hours for inactive sessions set by the server for security reasons, which is not configurable by the user. In case of an invalidated session, the user would need to log in again.
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)	Supports	The product was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks(Level A)	Supports	The product was tested for: Structure and hierarchy is marked up with Header elements outside of repetitive navigation links WAI-ARIA Landmark elements are used outside of repetitive navigation links
2.4.2 Page Titled(Level A)	Supports	The product was tested for: Pages have a meaningful title specified in the TITLE element. By default, the name of the page is used as the TITLE, but the author is able to add a more descriptive title if desired.
2.4.3 Focus Order(Level A)	Supports	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence The order of navigation is determined by the application author and follows the sequence of components as they occur in the DOM which is also the order in which they are displayed on the page.
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)	Supports	The product was tested for: Pages are fully inter-linked to each other Page contains controls that enable reaching all pages
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 Default headers are based on the Page name provided by the Author. Default Labels are based on the Field name provided by the Author. How descriptive these terms are of the actual content is up to the Author.
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus
3.1.1 Language of Page(Level A)	Supports	The product was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Not Applicable	By default, there are no passages in a language different from that of the page. If an application author were to include such content, they would need to mark that content with the lang attribute.
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	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
3.2.3 Consistent Navigation(Level AA)	Supports	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
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product. Where the author introduces their own icons and components into the app, they should take care to use them consistently.
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: 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 Application authors can include mechanisms to allow the user to review and correct data before submission, or add custom validations that flag errors and give the user the opportunity to correct them.
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 with Exceptions	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’. Custom controls have appropriate roles specified using the role attribute Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes Custom controls have a meaningful programmatically exposed name The Product uses standard HTML5 components and Oracle JET components which properly expose name (label) and role. In cases where the author chooses to write a custom UI component, they would need to use the appropriate APIs to expose the name, role, and other relevant attributes. During testing the following defects were discovered: Bug 25417421 - Generated links in tables and list views are read by screen reader as a same page link. However, these links actually navigate to a different page. No known workaround. Bug 26526794 - For select (combobox) field controls which are set to "read only" mode, labels are not read by screen readers. Workaround is to take screenreader out of form mode (numeric + key) and use arrows to navigate to field title.

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	Supports	Refer to the following documentation: http://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/accessibility/accessibility-features-and-tips-visual-builder-cloud-service.html
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 provides documentation in electronic form.
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 http://www.oracle.com/us/corporate/accessibility/oracle-accessibility-program-173235.html) 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/us/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.