Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Payment Cloud Service (OPCS) 23.3.10

Product Description:

This ACR is for Oracle Payment Cloud Service (OPCS), a web based application that uses APEX enabling the processing of card payments.

Date:

26-Sep-2023

Contact Information:

accessible_ww@oracle.com

Notes:

This Accessibility Conformance Report (ACR) does not cover the following product areas:

  • Account Holder verification process also known as KYC (Know Your Customer). Uses are redirected to the adyen.com domain to complete and are then returned to Oracle Payment Cloud Services. 

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
  • Controls have an associated name
  • Non-text characters are not used or have meaningful alternative text

Exceptions: 

  • Bug 35687892: Missing Alt text for Oracle logo in global page header and terminal device model images in Terminals page. 
  • Bug 35686872: Three dots actions button is missing Alt text in the below pages.
    • Locations page
    • Account Holder > Accounts > Users tab
    • Account > Locations and Users tabs
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.

Exceptions:

  • Bug 35683260: In the Locations page > Manage Users drawer, the region headings for the 'Not Assigned' and 'All' tabs don't identify unassigned users and all users. It incorrectly identifies as Assigned users. 
1.3.2 Meaningful Sequence(Level A)Supports

The product was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence.
1.3.3 Sensory Characteristics(Level A)Supports

The product was tested for:

  • Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound.
  • Instructions provided which refer to graphics included a reference to the text alternative of the graphic.
1.3.4 Orientation (Level AA)Partially Supports

The product was tested for 

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.

Exceptions: 

  • Bug 35696573: Responsive design issues in Terminals and Reports page
    • device images display out of card
    • device model names are truncated so won't know which device model the terminal belongs to
    • Large text size in Reports header causing text overlap issues.
1.3.5 Identify Input Purpose (Level AA)Supports

The product was tested for 

  • Text fields which collect information about the user contain the appropriate autocomplete content attribute. 
1.4.1 Use of Color(Level A)Supports

The product was tested for 

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight.
  • Information conveyed by color has a contrast ratio of at least 3:1.
1.4.2 Audio Control(Level A)Not 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: 

  • Bug 35697087: Contrast ratio is low for the below web elements on page. 
    • 'Guest Card Statement Descriptor" field value in the Edit Account drawer
    • 'Guest Card Statement Descriptor" field value in the Edit Location drawer
1.4.4 Resize text(Level AA)Supports

The product was tested for:

  • Text can be resized up to 200% without loss of content or functionality.
1.4.5 Images of Text(Level AA)Partially 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.

Exceptions: 

  • Bug 35687892: Missing Alt text for terminal device model images and Oracle logo. 
1.4.10 Reflow (Level AA)Supports

The product was tested for 

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom.
  • An alternative mobile user interface is available and is accessed from the main application.
  • Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.
1.4.11 Non-text Contrast (Level AA)Supports

The product was tested for:

  • Non-text items have a contrast ratio of at least 3:1
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.

Exceptions:

  • Bug 35687088: Content loss issues observed in Payouts and Reports pages. 
    • Overlapping text in payout metrics section of Reports page
    • Truncated text in chargeback chart of Reports page
    • Truncated dates in Payouts page.
1.4.13 Content on Hover or Focus (Level AA)Not Applicable

The product was tested for

  • There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)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.
2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for

  • Movement of focus through controls 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)Not Applicable

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 extended with at least 20 seconds warning up to 10 times.
2.2.2 Pause, Stop, Hide (Level A)Not Applicable

The product was tested for

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

  • A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
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.

Exceptions:

  • Bug 35687466: In the Chargebacks page > Defend Chargeback drawer:
    • After selecting the defense reason, the focus does not shift to the upload icon in the action column of the documentation table. 
    • After selecting the defense reason, the focus does not shift to the delete icon in the action column of the documentation table against a specific document row.
  • Bug 35696487: In the Terminals page:
    • When selecting Terminal to view terminal details drawer, then select Reassign Terminal button, focus shifts incorrectly to 'connect the terminal' link instructions after 'device name' field. Focus should shift to the buttons instead to maintain the order.
    • When selecting terminal to view details, then select 'connect the terminal' link, then click 'Back to Details' button within the drawer, focus does not return back to 'connect to terminal' link. 
    • During terminal registration, after click register and close button in drawer, focus does not return back to Register terminal button in Terminals page.  
    • When select 'Orders and Returns' button to open a pop up, focus is not shifting within popup when selecting Tab key in the keyboard 
  • Bug 35697575: After selecting buttons in a drawer or a pop up or a filter or selecting ellipse actions menu button, focus is not returning back to the element in the Account Holder page, Account page, Reports page, Chargebacks page, and Transactions page.
  • Bug 35697665: In the Locations page:
    • After click Assign/Reassign button in Assign/Reassign location drawer, focus does not get back to ellipse actions menu button against the same location
    • Manage Users drawer: Clicking Save button does not return focus back to ellipse actions menu button against the same location 
    • Edit locations detail drawer: Clicking save button does not return focus back to ellipse actions menu button against the same location
    • Open/Close location pop up: Focus is not shifting within popup when using keyboard keys. Then when select open/close buttons, does not return focus back to ellipse actions menu button against the same location
    • After select Add button in Add location drawer, focus does not return back to Add Location button
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)Partially Supports

The product was tested for

  • Pages are fully inter-linked to one another.
  • Page contains controls that enable reaching all pages.

Exceptions:

  • Bug 35683649: In Terminals page list view, after selecting an account there is no visible link to navigate back to previous Terminals page. However users can navigate back to Terminals page by selecting their Organization name in the global page header, then select 'Terminals' from Dashboard or bottom navigation tab to get to the Terminals page.
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:

  • Bug 35682679: Location column header label in Locations page is not a descriptive label. 'Location' column header displays the location name and location reference. 
  • Bug 35687595: Label 'Location' in the Locations page search text box is not descriptive.
  • Bug 35683260: Incorrect Search Labels
    • Locations page > Manage Users drawer: Search text box label should be 'Search Users' instead of 'Search Report' 
    • Assign Location Drawer within Accounts Page: Search text box label should be 'Search' instead of 'Search Report' 
    • Terminals page card and list view: Search text box label should be 'Search' (like it is in the Locations page). Currently search text box label displays ‘List Search’ in the Terminals page list view and when in Terminals page card view displays label as ‘Search’.
2.4.7 Focus Visible(Level AA)Partially Supports

The product was tested for:

  • Visual indication of the location of the focus.

Exceptions: 

  • Bug 35696487: Terminals page: Using keyboard tab key when select the 'Orders and Returns' button in Terminals page to open a pop up, the focus indicator is not visible within the popup that displays a message with a Cancel button.
2.5.1 Pointer Gestures (Level A)Not Applicable

The product was tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Not Applicable

The product was tested for:

  • There are no single pointer operations.
2.5.3 Label in Name (Level A)Supports

The product was 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.
2.5.4 Motion Actuation (Level A)Not Applicable

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 a 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.
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.
3.2.4 Consistent Identification(Level AA)Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product.
3.3.1 Error Identification(Level A)Supports

The product was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.
3.3.2 Labels or Instructions (Level A)Supports

The product was tested for:

  • Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)Supports

The product was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Partially 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.

Exceptions: 

  • Bug 35687529: When defending a chargeback transaction, there is no confirm checkbox. 
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)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’.
  • 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
  • Frames have a meaningful title specified in the title attribute.

Exceptions:

  • Bug 35688026: Terminal details drawer is missing a title.
  • Bug 35688094: Missing label for the select records on below pages.
    • Assign Location drawer in the Account page for an account
    • Edit User drawer in Users page against a user
    • Filter Locations drawer in Reports page
    • Manage Users drawer in Locations page against a location
4.1.3 Status Messages (Level AA)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.

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 EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

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

There are no accessibility or compatibility features to document.

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

The product documentation is 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.