ACR: Oracle Restaurants Suites Management Cloud Service 25.2

Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

 Oracle Restaurants Suites Management Cloud Service 25.2

Product Description:

Oracle Restaurants Suites Management Cloud Service is a responsive web application offering a comprehensive set of tools to streamline the management of accounts, menus, events, and venue operations at stadiums. The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the ACRs listed in the Dependent Products section for more information.

Report Date:

11-MAY-26

Contact Information:

accessible_ww@oracle.com

Dependent Products


This product interacts with or is built with the other Oracle products listed in this section. Click below to view information about the accessibility of these dependent products. Products listed are the versions available at the time of publication of this document; newer documents may be available that supersede these 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/

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.0Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.2Level 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.2 Report

Table 1 also documents conformance with:

Note: When reporting on conformance with the WCAG 2.2 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)Supports

The product and documentation were 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.
  • Titles for Objects and Applets are provided.
  • Controls have an associated name.
  • Non-text characters have meaningful alternative text.
  • CAPTCHAs include text alternatives that describe the purpose of the non-text content, and provide an alternative CAPTCHA serving the same purpose using a different modality.
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 and documentation were 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:
Bug 38614245 - Organizations Landing Pages Contains Non-Unique Landmark Labels

1.3.2 Meaningful Sequence (Level A)Supports

The product and documentation were tested for:

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

The product and documentation were 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.
1.3.4 Orientation (Level AA)Supports

The product and documentation were 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)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 and documentation were 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 and documentation were 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 39207974 - Venue Settings - Hyperlink color in the email preview template fails to meet the required contrast ratio for accessibility compliance.

1.4.4 Resize text (Level AA)Partially Supports

The product and documentation were tested for:

  • Text can be resized up to 200% without loss of content or functionality.

Exceptions:
Bug 38614248 - Create your first item text is lost in 200% Zoom 
Bug 38614554 - Ask Oracle Page | Feedback Submitted / Reset User Preference popup options are not visible on 200% Zoom 
Bug 38614664 - Suspend User / Reset Password / Send Welcome Email popups options are not visible on 200% Zoom
Bug 38614668 - Session extend / Session ended popup options are not visible on 200% Zoom 
Bug 38614680 - Suspend Venue / Terminate Venue popup options are not visible on 200% Zoom 
Bug 38614701 - Suspend Organization popup options are not visible on 200% Zoom

1.4.5 Images of Text (Level AA)Supports

The product and documentation were 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)Partially Supports

The product and documentation were 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:
Bug 38614553 - User Profile Page | User name is lost in 400% Zoom 
Bug 38614586 - Ask Oracle Page | Profile page content is lost in 400% Zoom 
Bug 38614591 - Ask Oracle Page content is lost in 400% Zoom 
Bug 38614605 - Suspend User / Reset Password / Send Welcome Email popups text is lost in 400% Zoom 
Bug 38614675 - Suspend/Terminate Venue popup text is lost in 400% Zoom 
Bug 38614698 - Suspend Organization popup text is lost in 400% Zoom
Bug 38614703 - Extend button text on session extend popup is lost in 400% Zoom
Bug 39207965 - Event Details page | All Tabs| Last record in each tab in event details page is overlapped by More Actions and Edit Event Options 
Bug 39207954 - Order Item detail page | Allergens data is partially visible as it is overlapped by Add To Order button when Item/package has more number of Choice groups configured
Bug 39207971 - PAR Restock Count Page | Options under More actions menu are not visible and Payment status is overlapped by More Actions menu

1.4.11 Non-text Contrast (Level AA)Partially Supports

The product and documentation were tested for:

  • Non-text items have a contrast ratio of at least 3:1.

Exceptions:
Bug 39207980 - Contrast of Edit Icons is Low for regular text size

1.4.12 Text Spacing (Level AA)Partially Supports

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

Exception:
Bug 38614253 - Create Single Item button is overlapped on Items Page

1.4.13 Content on Hover or Focus (Level AA)Supports

The product and documentation were 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.
  • Information appears on hover or focus using default browser behavior, such as the title attribute of components.
2.1.1 Keyboard (Level A)Supports

The product and documentation were tested for:

  • Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.
  • The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms).
2.1.2 No Keyboard Trap (Level A)Supports

The product and documentation were 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 and documentation were tested for:

  • There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable (Level A)Supports

The product and documentation were 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)Supports

The product and documentation were tested for:

  • There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold (Level A)Supports

The product and documentation were 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 and documentation were 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 and documentation were tested for:

  • Pages have a meaningful title specified in the TITLE element.
2.4.3 Focus Order (Level A)Supports

The product and documentation were tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.
2.4.4 Link Purpose (In Context) (Level A)Supports

The product and documentation were tested for:

  • The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose.
2.4.5 Multiple Ways (Level AA)Supports

The product and documentation were tested for:

  • Pages are in a site table of contents.
  • Pages are fully inter-linked to each other.
  • Page contains controls that enable reaching all pages.
2.4.6 Headings and Labels (Level AA)Supports

The product and documentation were tested for:

  • Headers describe the topic or purpose of the content below them.
  • Labels describe the purpose of the associated field.
2.4.7 Focus Visible (Level AA)Supports

The product and documentation were tested for:

  • Visual indication of the location of the focus.
2.4.11 Focus Not Obscured (Level AA)Supports

The product and documentation were tested for:

  • The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.
2.5.1 Pointer Gestures (Level A)Supports

The product and documentation were tested for:

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

The product and documentation were 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)Supports

The product and documentation were 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)Supports

The product and documentation were tested for:

  • There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA)Supports

The product and documentation were tested for:

  • There is no functionality that uses dragging movements.
2.5.8 Target Size (Minimum) (Level AA)Partially Supports

The product and documentation were tested for:

  • Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.
  • The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

Exception:
Bug 38614546 - Venue Settings - Insufficient Touch Target Size and Spacing Detected for First Name and Last Name Fields
Bug 39207977 - Email Templates - View Dialog touch Targets Do Not Meet Minimum Size and Spacing Requirements

3.1.1 Language of Page (Level A)Supports

The product and documentation were tested for:

  • Properly set lang attribute for each page.
3.1.2 Language of Parts (Level AA)Supports

The product and documentation were 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 and documentation were 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 and documentation were 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 and documentation were tested for:

  • Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time.
3.2.4 Consistent Identification (Level AA)Supports

The product and documentation were tested for:

  • Images and controls are used and identified consistently throughout the product.
3.2.6 Consistent Help (Level A)Supports

The product and documentation were tested for:

  • None of the following help mechanisms exist: Human contact details, human contact mechanisms, self-help options, automated contact mechanisms.
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.

The documentation was tested for:

  • The documentation does not have input fields, except for the Search field.
3.3.2 Labels or Instructions (Level A)Supports

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

The documentation was tested for:

  • Content does not require user input
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.

The documentation was tested for:

  • The documentation does not require user input that modifies user controllable data.
3.3.7 Redundant Entry (Level A)Supports

The product and documentation were tested for:

  • There are no occurrences of information that the user needs to enter which has been previously entered.
3.3.8 Accessible Authentication (Minimum) (Level AA)Supports

The product and documentation were tested for:

  • Steps which utilize a cognitive functional test have an alternative that does not rely upon a cognitive functional test.
4.1.1 Parsing (Level A)Not ApplicableThis criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)Partially Supports

The product and documentation were 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:
Bug 38614241 - Organizations Landing Page Session Expiration Dialog Does Not Provide Accessible Name

4.1.3 Status Messages (Level AA)Supports

The product and documentation were tested for:

  • Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

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.

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 Section

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionSupports

The product was tested for:

  • File conversions preserve accessibility information.
504.2.2 PDF ExportSupports

The product was tested for:

  • PDF files conform to PDF/UA-1
504.3 PromptsSupports

The product was tested for:

  • Prompts authors to create content that conforms to WCAG 2.0 AA.
504.4 TemplatesSupports

The product was tested for:

  • Templates are provided that allow content creation that conforms to WCAG 2.0 AA.

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:

  • Accessibility modes, either at installation or runtime.

Accessibility-related documentation can be found at: Oracle APEX Accessibility Guide

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 DocumentationSupports

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.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicable Standards/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.