Oracle Accessibility Conformance Report

The Point of Service product was tested for:

• Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription
• Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
• CAPTCHAs are not used

The documentation 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
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

Exceptions:

• BugID - 28701194:  In the application when a report is generated, it is displayed as an Image. This Image cannot be traversed through. The work around for this issue is that the report can be downloaded from the Xstore Office application.
• BugID - 28864397:  The application reads out the Image name, as the file name currently. This occurs with loyalty badge images, customer images and item images. For example, if we have a customer loyalty level as bronze and the bronze image is stored with a filename of customer loyalty, the screen reader reads "customer loyalty image" instead of bronze level.  If the end user wants to change what is being read out, then the file name needs to be changed. 

The Point of Service product was tested for:

• Labels are associated to components/fields
• Lists are contained within a List component
• Headings are marked as such with a Group relation from the header to the items beneath the header
• Tables are contained within a Table component, implement the AccessibleTable interface, provide an AccessibleSummary, and contain include row and column headers where appropriate

The documentation 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

Exception:

•  BugID - 31751519: Issue in the HTML files: No Row Headers Defined. The links in the footers work correctly.

The Point of Service product was tested for:

• The accessibility hierarchy is logical

The documentation was tested for:

• HTML markup and coding of text that provides a correct and logical reading sequence

The Point of Service product was tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics

The documentation was tested for:

• Instructions provided do not refer to things only based on their sensory characteristics, such as shape, size, visual location, orientation, color, or sound

The Point of Service product was tested for:

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

The documentation was tested for:

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

Exception:

• BugID - 31984853:  The application restricts Orientation

The Point of Service product was tested for:

• Text fields which collect information about the user were inspected for accessible name

The documentation was tested for:

• There are no text fields that collect information about the user

The Point of Service product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight

The documentation was tested for:

• Information conveyed by color has a contrast ratio of at least 3:1

The Point of Service 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 have a contrast ratio of at least 4.5:1

The documentation was tested for:

• Large-scale text, and images of large-scale text, have a contrast ratio of 3:1
• Other text and images of text have a contrast ratio of at least 4.5:1

Exceptions:

• BugID - 28701037:  The following screens have text that does not meet the ratio:  the login screen, item entry screen, send sale delivery address form, and the on hold transaction search screen. 

The Point of Service product was tested for:

• Text can be resized without assistive technology up to 200 percent

The documentation was tested for:

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

No images of text are used within the application

The documentation was tested for:

• Images of text are only used when the technology can't create the desired visual presentation

The Point of Service 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

The documentation 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

Exception:

• BugID - 31692500:  Reflow is not supported

The Point of Service product was tested for:

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

The documentation was tested for:

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

Exception:

• BugID - 31691714:  Non-text Contrast issues for noted graphics, icons and/or checkboxes in Customer Maintenance/Customer Wishlist, Associate Tasks, Inventory Adjustment, Disable/Enable Hardware, Till Maintenance and Employee Message Maintenance.

The Point of Service 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

The documentation 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 1.5 times the font size
  • Spacing following paragraphs to 2 times the font size
  • Letter spacing (tracking) to at 0.12 times the font size

Exception:

• BugID - 31804055:  Provide means to update text style settings for Text Spacing

The Point of Service product was tested for:

• There is no content that appears on hover or focus

The documentation was tested for:

• Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then 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

The Point of Service product was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

The documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

The Point of Service product was tested for:

• Movement of focus using only the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The documentation 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

The Point of Service product was tested for:

• Single character keyboard shortcuts can be turned off

The documentation was tested for:

• There are no single character keyboard shortcuts

The Point of Service product was tested for:

• Time limits in the product can be turned off before they are encountered

The documentation was tested for:

• Time limits are not used within the documentation

No information is presented using moving, scrolling or blinking in the application

The documentation was tested for:

• There is no moving, blinking or scrolling content

The Point of Service product was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The documentation was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

The documentation was tested for:

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

The Point of Service product was tested for:

• The name of the software application is meaningful

The documentation was tested for:

• Pages have meaningful titles specified with the TITLE element

The Point of Service product was tested for :

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

The documentation was tested for:

• Logical movement through the focusable components can be accomplished using only the keyboard, and in an order that follows a meaningful sequence

There are no links in the application

The documentation was tested for:

• The text of links and their surrounding paragraph, list, or table cell (with marked up table headers) are sufficient to describe their content

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

The documentation was tested for:

• Pages can be found using the provided "Search" function
• Pages are in a site table of contents
• Pages are fully inter-linked to each other

This Point of Service product was tested for:

• Headings and labels describe topic or purpose

The documentation was tested for:

• Headers describe the topic or purpose of the content below them
• Labels describe the purpose of the associated field

Exceptions:

• BugID - 28701571:  The labels are being read out, but they are being read out twice
• BugID - 28883149:  On the quick items tab, after the items are traversed, the items are read again

The Point of Service product was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Visual indication of the location of the focus

Exceptions

• BugID - 28947559:  When a field with data has focus, the data is highlighted in blue so you know the field has focus but it makes it difficult to see the flashing cursor. The screens which need the focus to be visible: sale screen, change item option,count summary screen and enter count screen, the extended transaction screens and their maintenance, customer maintenance screens,house account, shipping, receiving screens.   Also, if there is a check box on a form as in customer maintenance, there is no indication when the field has focus.

The Point of Service product was tested for:

• Multipoint or path-based gesture actions can be completed using a different input modality

The documentation has been tested for:

• There are no multipoint or path-based gesture actions

The Point of Service 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

The documentation 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

The Point of Service 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

The documentation 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

The Point of Service product was tested for:

• There are no functions that require motion of the device

The documentation was tested for:

• There are no functions that require motion of the device

The Point of Service product was tested for:

• At the time of setting up the application, the locale can be modified and the language specified will be used across the application

The documentation was tested for:

• Properly set "lang" attribute for each page

The Point of Service product was tested for:

• Properly set locale/language for text passages that are in a different language than that of the software

The documentation was tested for:

• Proper use of the "lang" attribute for text passages that are in a different language than that of the page

The Point of Service product was tested for:

• When a component receives focus it does not initiate a change of context

The documentation 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

The Point of Service product was tested for:

• Changes in the value of user interface components does not result in substantial change to the page

The documentation was tested for:

• Changes in the value of user interface components do not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

The documentation was tested for:

• Pages that are grouped together into sets with a common navigation mechanism use that mechanism in the same manner, with navigation elements appearing in the same relative order each time

The Point of Service product was tested for:

• Images and controls are used and identified consistently throughout the product

The documentation was tested for:

• Images and controls are used and identified consistently throughout the documentation

The Point of Service product was tested for:

• When input errors are detected, the error is described to the user in text and the field(s) in error identified

The documentation was tested for:

• The documentation does not have input fields, except for the Search field

The Point of Service product was tested for:

• Labels or instructions are provided when the product requires user input

The documentation was tested for:

• Content does not require user input

The Point of Service 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

The Point of Service 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

Markup languages are used internally in ways never available to assistive technology or to a user agent

The documentation 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

The Point of Service product was tested for:

• User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API
• State information, properties, and values are programmatically exposed for user interface components

The documentation was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes, including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Frames have a meaningful title specified in the title attribute

The Point of Service product was tested for:

• There are no status messages

The documentation was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes, including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Frames have a meaningful title specified in the title attribute

The Point of Service product was tested for:

• Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts.

This is not supported in Xstore, as the end user is not allowed to make platform setting changes, due to security restrictions.

The Xstore application, when launched, takes up the entire screen and the user is not given access to platform settings.

The specific controls for accessibility can be found in the Xstore Suite Implementation and Security Guide. 

Product documentation is in electronic format.