Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Permitting and Licensing 11.13.24.01.0

Product Description:

Oracle Fusion Applications are a suite of web-based enterprise software business products. Oracle Permitting and Licensing 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 ACR listed in the Product Dependencies section for more information.

Date:

28-Nov-2023

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR 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/Digital 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 Permitting and Licensing 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, voice activation, 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 Permitting and Licensing 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/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

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).
  • Non-text characters have meaningful alternative text.
  • Titles for Objects and Applets are provided.
  • Controls have an associated name.
  • CAPTCHAs are not used.

Exceptions to the above are as follows:

  • Visualizations on Project Overview do not have meaningful alternative text. Bug 33510018.
  • Lock icon on Manage Account does not have alternative text. Bug 36004039.
  • Images for phone, address, and email do not have alternative text. Bug 36004029.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe 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.

Exceptions to the above are as follows:

  • Tab groups on Worklist not marked up as Tabs which results in the wrong number of tabs read by Screen Reader. Bug 34815718 and Bug 35950694.
  • Headings on Register User not marked up as headings. Bug 35090641.
  • Headings on Manage Account not marked up as headings. Bug 36004015.
  • Headings on Column Selection modal in Plan Reviewer Department not marked up as headings. Bug 36014195.
  • Headings on Anonymous User Homepage not marked up as headings. Bug 35990474.
  • Column heading for Fees not marked up as a column heading in Worklist. Bug 35946411.
  • Search Result table for Contact Type, Manage Public Sector Department, Plan Reviewer Department, Transaction Group, and Transaction Category not marked up properly for captions, row, and column headings. Bug 36009819, Bug 36008851, and Bug 36004024.
  • Layout table for Conditions on Manage Account not marked up properly. Bug 36004020.
  • Layout table for Column Selector modal on Plan Reviewer Department not marked up properly.  Bug 3601432.
  • Row headings for Linked Permits in Permit Detail do not describe purpose. Bug 35278114.
  • Aria-label not read by Jaws when using the Arrow keys for a List View. Bug 28571183.
  • Data grid does not give any indication that a cell is interactive when using Screen Reader. Bug 30866153.
  • Manage Account has duplicate landmark. Bug 36004032.
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 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.

Exceptions to the above are as follows:

  • Name, Phone, and Address fields on Register User and Manage Account pages do not have autocomplete content attributes. Bug 35989893 and Bug 36004035.
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 ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Partially 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.

Exceptions to the above are as follows:

  • Case Status text on Schedule Hearing page does not have contrast ratio of at least 4.5:1.  Bug 35340185.
  • Placeholder text for Simple Search does not have contrast ratio of at least 4.5:1. Bug 35847493.
  • Enabled text in Contact Type and Transaction Category pages do not have contrast ratio of at least 4.5:1. Bug 36010004.
  • Text in Global Search results in hover state does not have a contrast of at least 4.5:1. Bug 35993153.
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.

Exceptions to the above are as follows:

  • Inspection Request and Inspection Cancel pages not usable when resized to 200%.  Bug 32084043.
  • Apply for Permit side panel not usable when resized to 200%. Bug 34701069.
  • Worklist Tab selector not operable with keyboard when resized to 200%. Bug 34815764.
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.

Exceptions to the above are as follows:

  • Portal banner region area removes functionality for maps, page finder, and navigational items when resized to 400%. Bug 31613493, Bug 32218095, and Bug 32217988.
  • Anonymous and Public User landing pages remove functionality and have text obscured when resized to 400%.  Bug 34695109, Bug 34695059, and Bug 34752719.
  • Agency Springboard landing page removes functionality and has text obscured when resized to 400%.  Bug 33523905 and Bug 34753581.
  • Notifications modal and detail page not usable when resized to 400%.  Bug 32102848.
  • Global Search result filter removed when resized to 400%.  Bug 34696354.
  • Manage Account page not usable when resized to 400%. Bug 32124646.
  • Error Log Tab not displayed on Communication Center page when resized to 400%. Bug 33046047.
  • Activity Tracking not usable when resized to 400%. Bug 31856592.
  • Case page not usable when resized to 400%. Bug 34812183.
  • Apply for Permit and Business License have text obscured and functionality removed when resized to 400%. Bug 34696783,  Bug 34696791, and Bug 34696796.
  • Payment Cart text obscured and grid requires two-dimensional scrolling when resized to 400%. Bug 34811052.
  • Appeal a Hearing not usable when resized to 400%. Bug 35340218.
  • Inspection Detail page removes functionality when resized to 400%. Bug 35302764 and Bug 35302311.
  • Permit Detail page removes functionality when resized to 400%. Bug 35292519.
  • Notice and Report setup page removes functionality when resized to 400%. Bug 35931300.
  • Manage Public Sector Departments, Plan Reviewer Department, Contact Type, Transaction Group, and Transaction Category removes functionality and requires two-dimensional scrolling when resized to 400%. Bug 35931319 and Bug 36008794.
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.

Exceptions to the above are as follows:

  • Worklist tab focus color has a contrast ratio less than 3:1. Bug 34815740.
  • Search prompt icon on Registered User Homepage and Agency Springboard has a contrast ratio less than 3:1. Bug 35994374.
  • Navigator menu color for focus versus selected has a contrast ratio less than 3:1. Bug 35993658.
  • Selected versus Focus color of tabs when side by side have a contrast ratio less than 3:1. Bug 36004051.
  • Selected versus Focus color of input fields when side by side have a contrast ratio less than 3:1. Bug 35990399.
1.4.12 Text Spacing (Level AA)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
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).

Exceptions to the above are as follows:

  • Deleting conditions on Sync Card Status not operable with the keyboard. Bug 33402202.
  • Text entry with CK Editor control not operable with the keyboard to place focus in text box. Bug 34701090.
  • Phone Input control requires two ESC key sequences to exit modal when operating with Jaws.  Bug 34756659.
  • Search Results on Explore your City not operable with the keyboard. Bug 35930144 and Bug 35930117.
  • Select All checkbox in Fees and Payment cannot be unselected with the keyboard. Bug 35340761.
  • Worklist Tab selector menu not operable with keyboard when resized to 200%. Bug 34815764.
  • Worklist back button tab that displays all tabs not operable with the keyboard when using Jaws. Bug 34815753. 
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)Partially Supports

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element.

Exceptions to the above are as follows:

  • Page Titles for Manage Public Sector Department, Plan Reviewer Department, Contact Type, Transaction Group, and Transaction Category missing meaningful title. Bug  36010208.
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.

Exceptions to the above are as follows:

  • Initial focus is being set to Read More link on Anonymous Home Page.  Bug 34752070.
  • Focus order is lost after closing an Error message in Contact Type, Manager Public Sector Department, Plan Reviewer Department, Transaction Group, and Transaction Category setup pages. Bug 36010125.
  • Focus order is lost after closing the Add Element Dialog in Contact Type, Manage Public Sector Department, Plan Reviewer Department, Transaction Group, and Transaction Category setup pages. Bug 36004192.
  • Initial focus is being set incorrectly when adding phone number on Register User page. Bug 36014232,
2.4.4 Link Purpose (In Context)(Level A)Partially 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.

Exceptions to the above are as follows:

  • Worklist conditions dialog has an unlabeled link. Bug 35950403.
2.4.5 Multiple Ways(Level AA)Partially Supports

The product was tested for:

  • Pages can be found using the provided "search" function.
  • Pages are fully inter-linked to each other.

Exceptions to the above are as follows:

  • Setup pages for Contact Types, Transaction Category, Transaction Group, Manage Public Sector Department, and Plan Reviewer Department are not available within the Navigation Menu or Page Finder function.  Bug 36008904.
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.

Exceptions to the above are as follows:

  • Labeling and implementation of selecting or identifying a comment as a favorite is difficult to understand.  Bug 31114926.
  • Labels of the Report List page do not describe purpose. Bug 33056016.
  • Label for Simple Search text input field and Search button do not describe purpose. Bug 34746956 and Bug 34701060.
  • Labels for Search and Actions in Worklist do not describe purpose. Bug 35950694.
  • Labels for the row selectors do not describe purpose. Bug 33044607.
2.4.7 Focus Visible(Level AA)Partially Supports

The product was tested for:

  • Visual indication of the location of the focus.

Exceptions to the above are as follows:

  • Focus not visible after returning to Permit Detail after making selection and selecting OK or Cancel button, Bug 34701085.
  • Focus not visible for Selection drop down and Go selection button on Registered User Homepage and Agency Springboard in Firefox. Bug 35993767.
  • Focus not visible after closing Error Message dialog after an error occurs. Bug 36010125.
  • Focus not visible after launching Terms of Use dialog. Bug 36004200.
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.

Exceptions to the above are as follows:

  • Visual label for login and account avatar is not included in the accessible name. Bug 36008809.
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)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.
  • 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.
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.

Exceptions to the above are as follows:

  • Implementation of tables and sorting of table columns across different transactions is not consistent.  Bug 28525590 and Bug 28525798.
  • Implementation of tabs across different transactions is not consistent. Bug 31805713.
  • Header icons and colors are not consistent throughout the elements of the application.  Bug 30109779.
  • Labeling and implementation of the Comments and Attachment tables are not consistent. Bug 31114902.
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.

Exceptions to the above are as follows:

  • Required field indicator should be fully expanded on public user facing pages with a visible legend.  Bug 31786375.
  • Instructions for search results on Report an Issue not provided.  Bug 34756667 and Bug 34756776.
  • Labels missing for form fields on Permit Detail Overview. Bug 35941965.
  • Labels for navigation lists not marked up properly. Bug 33224101 and Bug 33289498.
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)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.

Exceptions to the above are as follows:

  • Duplicate IDs exist in the HTML within Comment common user interface components.  Bug 31114902.
  • Duplicate IDs exist in the HTML on Code Enforcement Inspection. Bug 35302780.
  • Duplicate IDs exist in the HTML on Inspection Detail. Bug 35340358.
  • Aria nested incorrectly in the HTML on Homepages and Springboards. Bug 35990464 and Bug 35993616.
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.

Exceptions to the above are as follows:

  • Global Search result links not operable by VoiceControl. Bug 34710370.
  • State of severity combobox not available when control is in display only state on Conditions for Contractors. Bug 35331663.
  • Date elements in Manage Public Sector Departments and Plan Reviewer Department missing attributes for role. Bug 36011121. 
  • Modal dialogs for adding elements in Contact Type, Manage Public Sector Department, Plan Reviewer Department, Transaction Category, and Transaction Group missing accessible name. Bug 36011097.
  • Plan Reviewer Department search field and department lead have incorrect ARIA attributes defined. Bug 36014133 and Bug 36014155.
  • Required state for Classification on Register User and Transaction Category is incorrect. Bug 35990399.
  • Landmark name on Agency Springboard not sufficient. Bug 35993850.
  • Swipes on touch devices when using VoiceOver take user out of popups. Bug 34755904.
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.

Exceptions to the above are as follows:

  • Page Finder status message for results erroneously read by screen reader after control closed. Bug 34755782.
  • Processing status messages repeated multiple times by screen reader. Bug 34701097.
  • Simple Search status message for number of rows and results not being read by screen reader.  Bug 35278044 and Bug 36008954.
  • Explore Your City search results not being read by screen reader on Edge. Bug 35302818.
  • Worklist search results not being read by screen reader. Bug 35950726.
  • Status message for selecting or de-selecting search result row on Contact Type, Manage Public Sector Department, Plan Reviewer Department, Transaction Group, and Transaction Category not read by screen reader. Bug 36009864.
  • State of selected column in Plan Reviewer Department page not read by screen reader. Bug 36014232.
  • View Recommendations and Saved Search Results status messages not read by screen reader. Bug 35940913 and Bug 35940951.

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

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 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSupports

See WCAG 2.0 Section.

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

The product does not include authoring tools that provide format conversions or saving content in multiple formats.

504.2.2 PDF ExportNot Applicable

The product does not provide export of PDF files.

504.3 PromptsNot Supported

The product does not prompt authors to create accessible content.   Bug 28586849.

504.4 TemplatesNot Applicable

The product does not provide templates.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

The product documentation describes:

  • Special keystrokes needed to operate controls.

Accessibility-related documentation can be found in the Oracle Permitting and Licensing documentation in the Using Accessibility Features Chapter.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Support documentation is provided in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

back to top

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.