Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Public Sector Compliance and Regulation 11.13.21.01.0

Product Description:

Oracle Fusion Applications are a suite of web-based enterprise software business products. Oracle Public Sector Compliance and Regulation targets the needs of state and local officials responsible for regulating building development and business operation within their jurisdictions.The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the Oracle Fusion Applications Common Dependencies VPAT listed in the Product Dependencies section for more information.

Date:

03-Dec-2020

Archive Note:

This VPAT applies to only versions 11.13.21.01.0 through 11.13.21.10.0. It does not apply to any versions of Oracle Public Sector Compliance and Regulation after this. This VPAT has been superseded by Oracle Public Sector Compliance and Regulation 11.13.22.01.0.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

The product contains an authoring tool that allows the author to design forms such as for permits or business licenses. While the content produced from the authoring tool is accessible, the content designer itself is excluded.
The product integrates to a third party rendering tool, ESRI, to display maps.
The product provides Chatbot Assistants which are an alternative to the UI.
BI Publisher reports are intended for printing purposes only.
Product Documentation in PDF format.
The product utilizes process automation in Oracle Integration Cloud.

Oracle Public Sector Compliance and Regulation has a single run time mode for the user interface. The single run time mode ensures a more consistent approach to the user interface regardless of whether the user is utilizing a screen reader, keyboard, high contrast, zoom, or large fonts mode. There are specific keystrokes for a number of operations within the application. For information on keystrokes and on accessibility in the product, review the Using Accessibility Features chapters in the Oracle Public Sector Community Development documentation.

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 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 (e.g. a data table). Titles for Objects and Applets are provided. Controls have an associated name. CAPTCHAs are not used. During testing, the following issues were identified: Help and lock icon are not read by the assistive technology. Bug 28071894. Attachment icon in Code Enforcement Incidents is missing ALT text. Bug 31552620. Delete icon in Time Reporting Entry is missing ALT text. Bug 31453259.
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 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. 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 issues were identified: Table Summary, column, and row headings are missing from the Link Transactions table. Bug 31594126. Payment Cart marked up as a list instead of table. Bug 31793780. Business License Refund Request table has row headers not marked up. Bug 31801379. Collection table common component has header cell not marked up with heading. Bug 31873879. Grid View for Permit Inspection List has a table with column and row headers not marked up. Bug 31805020 and Bug 31826908. Planning Application table has header not scoped. Bug 31831711.
1.3.2 Meaningful Sequence(Level A)	Partially Supports	The product was tested for: The sequence of elements in the DOM matches a logical reading sequence. During testing, the following issues were identified: Incorrect tab order sequence on the Generate Notifications in Code Enforcement. Bug 30672842.
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 include a reference to the text alternative of the graphic.
1.3.4 Orientation (Level AA)	Supports	The product 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)	Partially Supports	The product was tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. During testing, the following issues were identified: Postal code on user registration page missing autocomplete content attribute. Bug 32124564. Postal code on the application intake page missing autocomplete content attribute. Bug 32131181. Business name, postal code, and email on Manage Accounts page missing autocomplete content attributes. Bug 32124733.
1.4.1 Use of Color(Level A)	Supports	The product was tested for: Information is not conveyed only using color.
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
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. All other text and images of text have a contrast ratio of at least 4.5:1.
1.4.4 Resize text(Level AA)	Partially Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality. During testing, the following issues were identified: Record detail pages for permits, business licenses, projects, and inspections have table elements which cannot be resized to 200%. Bug 31839775, 31840039, 31840065, and 31842690. Record detail pages for permits, business licenses, projects, and inspections have overlapping content when scrolling when resized at 200%. Bug 31839696, 31839711, 31839664, and 31843068 Incident icon and back button on Case Incident page obscures text when resized to 200%. Bug 31839291 and Bug 31839374. Apply page for permits and business licenses truncates text when resized to 200%. Bug 31834812. Actions disappear when using back button on Inspection List transaction when resized to 200%. Bug 31843125.
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.
1.4.10 Reflow (Level AA)	Not Supported	The product 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. During testing, the following issues were identified: Portal banner region area removes functionality for maps, page finder, and navigational items when resized to 400%. Bug 31613493, 32103370, and 32102808. Anonymous and Public User landing pages remove functionality when resized to 400%. Bug 32106769 and Bug 32103325. Explore Your City Expand/Collapse and Advanced Search not usable when resized to 400% zoom. Bug 32124487. Record detail pages for permits, business licenses, projects, applications, and inspections has truncated text, obscured text, and obscured user interface elements when scrolling and resized at 400%. Bug 31839696, 31839711, 31839664, 31839775, 31840039, 31840065, and 31842690. Apply page for permits, business licenses , and planning applications have truncated text, obscured text, and obscured user interface elements when resized to 400%. Bug 31834812 and Bug 32124807. Report an Issue and Case Incident truncates text, obscures text, and obscures user interface elements when resized to 400%. Bug31839291 and Bug 31839374. Download icon for common table user interface components missing when resized to 400%. Bug 31248620. Pagination region for common table user interface components has two dmensional scrolling when resized to 400%. Bug 31366845. Notifications table removes functionality and has two dimesional scroll when resized to 400%. Bug 32102848. Folder tab common user interface component requires two dimensional scrolling when resized to 400%. Bug 32107618. Calendar common table user interface component not usable when resized to 400%. Bug 31366998. User Registration page has labels disassociated from form controls when resized to 400%. Bug 32107794. Manage Account page not usable when resized to 400%. Bug 32124646.
1.4.11 Non-text Contrast (Level AA)	Partially Supports	The product was tested for: Non-text items have a contrast ratio of at least 3:1. During testing, the following issues were identified: Common user interface slider components have contrast ratio less than 3:1. Bug 332095577. Form controls in common user interface components contained within a gray or blue background frame have a contrast ratio less than 3:1. Bug 32095599. Common user interface icon components used download, filter, and sort for tables have a contrast ratio less than 3:1. Bug 32095619. MouseOver colors for expand/collapse icons on side panels for permits, business licenses, applications, and incidents have contrast ratio less than 3:1. Bug 32095646. MouseOver colors to differentiate columns and rows in the common user interface table components have contrast ratio less than 3:1. Bug 32095631. Default color in the common user interface components when focus lands on actionable controls has contrast ratio less than 3:1. Bug 31366734.
1.4.12 Text Spacing (Level AA)	Partially Supports	The product 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 During testing, the following issues were identified: Tile titles are obscured on Agency Springboard with increased text spacing. Bug 32103370. Tile titles are obscured in Page Finder with increased text spacing. Bug 32103391.
1.4.13 Content on Hover or Focus (Level AA)	Supports	The product was tested for: Dismissable -The content can be dismissed without moving the pointer or keyboard focus Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid..
2.1.1 Keyboard(Level A)	Partially Supports	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). During testing, the following issues were identified: New fields added to a form in the Form Designer are not operable with the Designer using the keyboard. Bug 29698702.
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.1.4 Character Key Shortcuts (Level A)	Supports	The product was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for: Time limits in the product can be turned off before they are encountered. Time limits in the product can be extended with at least 20 seconds warning up to 10 times. Time limits are longer than 20 hours.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for: There is no moving, blinking or automatic scrolling content that is greater than or equal to 5 seconds.
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: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page. 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.
2.4.3 Focus Order(Level A)	Partially Supports	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence. During testing, the following issues were identified: Registration tree view has hidden field which receives focus. Bug 31793624.
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 between list, and 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 can be found using the provided "search" function. Pages are fully inter-linked to each other.
2.4.6 Headings and Labels(Level AA)	Partially 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. During testing the following issues were identified: Labeling and implementation of selecting or identifying a comment as a favorite is difficult to understand. Bug 31114926. Label is missing for a heading in the Business License comments page. Bug 31116554. Label is missing for expand/collapse icon on record detail side panel page for permits, business licenses, planning applications, projects, and inspections. Bug 31799490. Labels not unique for multiple edit buttons with different context on record detail pages for permits, business licenses, planning applications, projects, and inspections. Bug 31826080. View Invoice History transaction has multiple search elements with different context that should be made unique. Bug 31798012. Labels for columns in Expiration Group Rules are not indicative of field purpose. Bug 31117769. Condition Action combo box on Business License Rules page has extraneous text read for drop down values. Bug 31516416.
2.4.7 Focus Visible(Level AA)	Partially Supports	The product was tested for: Visual indication of the location of the focus. During testing, the following issues were identified: Focus is not visible on the prompt icon for the global search box in the portal banner region. Bug 31786073.
2.5.1 Pointer Gestures (Level A)	Supports	The product was tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The product 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. When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion. When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.
2.5.3 Label in Name (Level A)	Partially Supports	The product has been 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. During testing, the following issues were identified: Selected Tab in the filter tab common user interface component has visual label that is not contained in the accessible label. Bug 31629537.
2.5.4 Motion Actuation (Level A)	Supports	The product was tested for: There are no functions that require motion of the device.
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)	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)	Partially 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. During testing, the following issues were identified: Substantial change of context exists when applying for a permit, business license, or planning application when search box receives focus.Bug 31834789.
3.2.2 On Input(Level A)	Partially 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. In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components. During testing, the following issues were identified: Unexpected change of focus exists on Business Rules Detail page when performing an add or delete action. Bug 31516416.
3.2.3 Consistent Navigation(Level AA)	Supports	The product was tested for: There are no navigational mechanisms that are repeated.
3.2.4 Consistent Identification(Level AA)	Partially Supports	The product was tested for: Images and controls are used and identified consistently throughout the product. During testing, the following issues were identified: Implementation of tables and sorting of table columns across different transactions is not consistent. Bug 28525590 and Bug 28526798. Modals are not implemented consistently from a keyboard or an assistive technology perspective. Bug 28587781 and Bug 30565922. Header icons and colors are not consistent throughout all elements of the application. Bug 30109779. Labeling and implementation of the Comments and Attachment tables are not consistent. Bug 31114902 and Bug 31114963.
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)	Partially Supports	The product was tested for: Labels or instructions are provided when the product requires user input. During testing, the following issues were identified: Required field indicator should be fully expanded on public user facing pages with a visible legend. Bug 31786375. Pagination region content should include instructions and labels to understand purpose. Bug 31794145.
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)	Partially 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. During testing, the following issues were identified: Confirmation mechanism not provided when permanently cancelling permit. Bug 31826523.
4.1.1 Parsing(Level A)	Partially 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. During testing the following issues were identified: Duplicate IDs exist in the HTML in the Comment common user interface components in Code Enforcement and Inspection. Bug 31114902, 31114963, 31873879. Duplicate IDs exist in the HTML for Filter Tab common user interface components. Bug 31625397. Duplicate IDs exist in the HTML for Request Inspection page. Bug 31799802. HTML does not validate for prior search results in Explore Your City transaction. Bug 31816744.
4.1.2 Name, Role, Value (Level A)	Partially 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’. Frames have a meaningful title specified in the title attribute. During testing, the following issues were identified: Recommended permits not read to the user after completing questionnaire. Bug 28428677. Label missing for frame in the Business License comments page. Bug 31116554. Collection table common component has duplicate landmarks. Bug 31500274 and Bug 31894148. Regions are needed on anonymous, public user, and agency staff landing pages to better understand content. Bug 31834721. Action menu in Worklist table not being read by the assitive technology. Bug 32059074.
4.1.3 Status Messages (Level AA)	Partially Supports	The product was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. During testing, the following issues were identified: Status messages are not cleared when applying for a permit or license. Bug 31834762.

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	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	Supports	See WCAG 2.0 Section.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product does not include authoring tools that provide format conversions or saving content in multiple formats.
504.2.2 PDF Export	Not Applicable	The product does not provide export of PDF files.
504.3 Prompts	Not Supported	The product does not prompt authors to create accessible content. Bug 28586849.
504.4 Templates	Not Applicable	The product does not provide templates.

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	The product documentation describes: Accessibility modes, either at installation or runtime Special keystrokes needed to operate controls Workarounds Accessibility-related documentation can be found in the Oracle Public Sector Compliance and Regulation documentation in the Using Accessibility Features Chapter,
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	Support documentation is provided 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.