Name of Product: Oracle Application Framework Release 12.2.4

Last Updated: 19-Sep-2014

This VPAT applies to only version 12.2.4. It does not apply to any versions of Oracle Application Framework after this.
This VPAT has been superseded by Oracle Application Framework Release 12.2.5

Oracle Application Framework (OA Framework) is an integrated platform for developing and deploying Oracle E-Business Suite HTML-based applications.

This VPAT only covers OA Framework runtime user interface components, user interface interactivity and functional administration pages.

For additional information, refer to My Oracle Support Knowledge documents and E-Business Suite documents:

  • Oracle Application Framework Developer's Guide, Document 1315485.1
  • Oracle Application Framework Profile Options, Document 1315510.1
  • Oracle Application Framework Release Notes for Release 12.2.4, Document 1676223.1
  • Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Documents,  Document 1302189.1
  • Oracle Application Framework Personalization Guide, Part No. E22031
  • Oracle E-Business Suite User's Guide, Part No. E22956

The following are known exceptions:

  • The Favorites, Navigator and Settings menus in the global header and Table Settings image need to be marked up as wai-aria buttons and menus with menu items. (Bugs 17214194, 18688497) 
  • Read-only checkboxes are images and need wai-aria checkbox role. (Bug 18978347)
  • Tab pages are links and need wai-aria tab role. (Bug 19501349)
  • The home page navigator tree needs to be a wai-aria tree view widget. (Bug 17214262)
This VPAT does not cover the following product areas:
  • Oracle JDeveloper with OA Extension (an Oracle E-Business Suite design-time extension) that makes up the integrated development environment (IDE) for OA Framework.
  • Inline Pop-Ups allows applications to update or display contextual information in a small pop-up window on top of an OA Framework page. This pop-up capability helps to minimize the number of Detail drilldown interactions a user has to make. The Inline Pop-Ups feature is disabled in both 'Standard' and 'Screen Reader Optimized' accessibility modes.  The user may drilldown to the detail to achieve the same functionality. (Bug 12583117)
  • The Look Ahead List of Values (LOV) has type-ahead search capabilities. When an end-user types in a few characters (generally at least three) into an LOV search field, all matching results for the characters are fetched and displayed inline to the LOV component in a Look Ahead LOV window. The Look Ahead LOV is disabled in 'Screen Reader Optimized' accessibility mode. The user may open the classic LOV modal window to search for and select a value and achieve the same functionality. (Bug 17656938)
  • The Inline Attachments pop-up window allows a user to add, edit, delete, or view attachments to a business entity on the same page as the base entity itself. The Inline Attachments feature is disabled in both 'Standard' and 'Screen Reader Optimized' accessibility modes.  The user may navigate to the Add and View attachments pages to achieve the same functionality. (Bug 8996793)
  • The Inline Date Picker is disabled in 'Screen Reader Optimized' accessibility mode. The date can be entered manually into the field without using the inline date picker. (Bug 3822637)
  • A Rich Content Container is a component designed to hold external content such as ADF Faces within an OA Framework page . The rich content may be embedded within an OA Framework page directly, or enclosed within an iFrame depending on the rich content source. The Rich Content Container does not pass an accessibility mode to the external application. (Bug 18888719)

For Web UI, the user needs to enable accessibility mode either from the Login page or Preferences page by choosing one of these values for the Accessibility poplist value:

  • ‘Screen Reader Optimized’
  • ‘Standard Accessibility’

Explanation of how the Login screen works:

  • The accessibility mode only needs to be set once by the user to a value other than 'None' if needed.  If a screen reader user forgets to set the mode to 'Screen Reader Optimized' then on the main navigator page, the screen reader will speak "The application is running in inaccessible mode. This can be changed from the preferences screen."
  • If on the Login page the user selects 'Standard Accessibility' or 'Screen Reader Optimized', a profile gets automatically set to that value which can be seen on the Preferences page.
  • If user selects 'None' on the Login page, the value on the Preferences page stays to whatever it was last set to.
  • The Login page itself runs as GUEST user and by default is set to 'Standard Accessibility' accessibility mode.  A System Administrator can set it to a different value such as 'Screen Reader Optimized' accessibility mode via the System Profiles page.

Please review the Oracle E-Business Suite Accessibility  white paper for more information.

The information below describes this product's ability to support the applicable U.S. Section 508 standards and the Web Content Accessibility Guidelines (WCAG) 1.0 Double-A Guidelines, subject to Oracle's interpretation of those standards and the remarks in this document.

For more information regarding the accessibility status of this product or other Oracle products, see https://www.oracle.com/accessibility/ or contact: accessible_ww@oracle.com.

 


Note: 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.

Section 1194.21 Software Applications and Operating Systems

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.21(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls
  • proper operation of unique keystrokes and access keys, including those listed in the product documentation.

Exception:

  • Decorative read-only rating bar images missing empty alt tags. (Bug 17572247)
1194.21(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for response to the following operating system accessibility features:

  • Sticky Keys, Filter Keys and Toggle Keys
  • Sound Sentry
  • High Contrast.
1194.21(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Visual indication of the position of the cursor
  • Current focus location is programmatically exposed.
1194.21(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • 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, such as whether a field is ‘required’.
  • Images that convey information have meaningful alternative text.

Exception:

  • Mandatory forms elements which have an asterisk do not always have '(Required)' within the label. (Bug 12777518)
1194.21(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Images that convey information have meaningful alternative text using ALT and if necessary, LONGDESC
  • Images that are decorative are marked so as to be ignored by assistive technology, either by using ALT=”” or CSS background images
  • Images are used consistently throughout the product.

Exceptions:

  • When implementing a corporate branding image, it is not possible to set the alt text. (Bug 17644101)
  • Images within rows of a data table have duplicate alt text and are not meaningful enough. (Bugs 18978263, 18977743, 18978309)
  • The Favorites and Navigator menus in the global header have decorative images missing empty alt tags (Bugs 17214194, 18688497) 
1194.21(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Text is supplied through HTML or injected into the browser DOM; the browser is responsible for exposing all such content in a way that is usable by assistive technology on the platform.
1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Response to the operating system High Contrast mode
  • Response to the operating system Large Fonts mode
1194.21(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Moving, blinking, or scrolling information that is designed to last for more than three seconds can be paused.
  • Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden.
1194.21(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Information conveyed by color or font styles is available in alternative formats, such as shape and text.
1194.21(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested with the default colors specified in the associated style sheet for:

  • Text and images of text in non-disabled controls have a luminosity contrast ratio of at least 4.5:1. Large scale text has a minimum ratio of at least 3:1

Colors can also be set by:

  • choosing different operating system color schemes and specifying that the browser should use them
  • changing the skins or web page layout Look and Feel (LAF) themes that are provided. Please review the Oracle E-Business Suite Accessibility  white paper for more information.

Exceptions:

  • 'Login Assistance' link on the Login page (Bug 19065589)
  • selected date in the date picker (Bug 18140354)
  • worklist notification count in the global header menu (Bug 18852031)
1194.21(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
1194.21(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL and TITLE.


Exceptions:

  • Buttons have different meanings but same label. A workaround is to change the label via Personalization. (Bug 17401269)
  • Mandatory forms elements which have an asterisk do not always have '(Required)' within the label. (Bug 12777518)
  • The Navigator menu in the global header has a search form element without a label (Bug 17214194)

back to top
 

Section 1194.22 Web-based Internet Information and Applications

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.22(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • A textual equivalent for complex graphics such as charts is provided.
  • An empty alt for decorative images, including images used for spacers is used.
  • An alt description for all images that convey content (e.g. pictures) or indicate actions (e.g. buttons) is provided.

 

Exceptions:

  • When implementing a corporate branding image, it is not possible to set the alt text. (Bug 17644101)
  • Images within rows of a data table have duplicate alt text and are not meaningful enough. (Bugs 18978263, 18977743, 18978309)
1194.22(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Product has been developed to conform to this standard subject to the remarks on the right.

There is no multimedia content.

1194.22(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Where color or font changes are used to highlight an object, the significance of this (e.g. "this tab is highlighted") is provided either with at text or with text hidden using a style sheet.
  • Any information conveyed with color is also presented without color.
1194.22(d) Documents shall be organized so they are readable without requiring an associated style sheet. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Documents have been organized so they are readable and linearize without requiring an associated style sheet.
1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. Product has been developed to conform to this standard subject to the remarks on the right.

Server-side image maps are not used.

1194.22(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Product has been developed to conform to this standard subject to the remarks on the right.

Client-side image maps are not used.

1194.22(g) Row and column headers shall be identified for data tables. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Table usage – only data tables, as opposed to layout tables, use table elements of TH and CAPTION and table attributes of SUMMARY, SCOPE, HEADERS and AXIS
  • Each column of a data table is marked up with TH and SCOPE=”COL”
  • Each row of a data table has at least one column marked as the row header with SCOPE=”ROW”

Exceptions:

Rich tables are missing default row headers. (Bug 18153933)

Two workarounds are:

  • Sort on a column
  • Rearrange the columns via Table Settings

Classic and Advanced tables by default have the first column set as row header but if the column is hidden or there is no data in that column then there is no row header. (Bugs 12366533 and 13522659)  

Two workarounds are:

  • Set the row header through Personalization
  • Reorder the table column (shifting first column of table to one that is displayed on screen or keeping first column where data exists) through Personalization.

HGrid tables by default have the column next to the hierarchy column set as the row header but if there is no data in the cell then there is no row header. (Bug 12593836)

Gantt chart tables do not have row headers. (Bug 16811950)

Form controls  inside a table should have a unique label in the format of <column-header>: <row-header>.  (Bug 12921526)

Column has empty header on a table with an empty cell at position 1,1. (Bug 18304777)

1194.22(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • For data tables, markup is used to associate data cells with header cells.
  • For simple tables the scope attribute is used, where the table is more complex, headers and data cells are associated using the headers attribute.
1194.22(i) Frames shall be titled with text that facilitates frame identification and navigation. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Each frame has a title to facilitate frame identification and navigation.
  • Purpose frames and how frames relate to each other are described if it is not obvious from frame titles alone.
  • Each page/window has a title to facilitate identification of purpose and context.

Exception:

  • Pages with iframes do not contain title and/or lang tags. (Bugs 16812596, 18858999)
1194.22(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Use of blinking text/objects or animated gifs that blink are avoided.
  • Movement in pages (e.g. marquees, moving Flash content, etc.) are also avoided.
  • No portion of the screens flicker with a frequency between 2 Hz and 55 Hz.
1194.22(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. Product has been developed to conform to this standard subject to the remarks on the right.

Text–only pages are not necessary because pages have been coded to meet other applicable standards, to the extent indicated.

1194.22(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Keyboard access is provided to all functions of the application. Logical event handlers are specified rather than device-dependent event handlers.
  • Event handlers are input-device independent.
  • Operations supported by scripts are accessible from the keyboard or have accessible equivalents (e.g. links equivalent to pop-up menus).
  • Content conveyed by scripts is textual and rendered in an accessible fashion.
1194.22(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Content rendered by required plug-ins or applications has been coded to meet other applicable standards, to the extent indicated.
  • Links are provided for downloading non-standard applets or plug-ins.
1194.22(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Form elements have labels associated with them in the markup (i.e. the id and for attributes).

Exceptions:

  • Buttons have different meanings but same label. A workaround is to change the label via Personalization. (Bug 17401269)
  • Mandatory forms elements which have an asterisk do not always have '(Required)' within the label. (Bug 12777518)
  • The Navigator menu in the global header has a search form element without a label (Bug 17214194)
1194.22(o) A method shall be provided that permits users to skip repetitive navigation links. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • A ‘Skip Navigation Elements to Page Contents' link is provided to skip repetitive navigation links at the top of the page.
  • Structure and hierarchy is marked up with Header elements.

Exceptions:

  • When running E-Business Suite pages in 'Standard' accessibility mode for keyboard-only users, the anchors are there but not visible (Bug 16218308).
  • All IDs are not unique. (Bugs 17763505, 17640053, 17729384, 18066960, 18403160, 18459266, 18465060, 18494339, 18496888, 18770724, 18886807, 19137946, 18458344)
  • The global header menu is marked up as a list but is not a list. (Bug 18999168)
1194.22(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Product has been developed to conform to this standard subject to the remarks on the right.

Profile option 'ICX: Session Timeout' is used to enforce an inactivity time-out. If a user performs no Oracle E-Business Suite operation for a time period longer than the time-out value (specified in minutes), the user's session is disabled. The user is provided an opportunity to re-authenticate and re-enable a timed-out session. If re-authentication is successful, the session is re-enabled and no work is lost. Otherwise, Oracle E-Business Suite exits without saving pending work.

  • If this profile option to 0 or NULL, then user sessions will never time out due to inactivity.

Profile option 'ICX: Limit Time' is used  to specify the absolute maximum length of time (in hours) of any user session, active or inactive.

The 'User Session Limits' and 'Session Timeout Behavior' are documented in the Oracle E-Business Suite System Security Guide.

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.

back to top
 

Section 1194.23 Telecommunications Products

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.23(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use. Not Applicable  
1194.23(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols. Not Applicable  
1194.23(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs. Not Applicable  
1194.23(d) Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required. Not Applicable  
1194.23(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays. Not Applicable  
1194.23(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided. Not Applicable  
1194.23(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use. Not Applicable  
1194.23(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided. Not Applicable  
1194.23(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product. Not Applicable  
1194.23(j) Products that transmit or conduct information or communication, shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery. Not Applicable  
1194.23(k)(1) For products which have mechanically operated controls or keys, controls and keys shall be tactilely discernible without activating the controls or keys. Not Applicable  
1194.23(k)(2) For products which have mechanically operated controls or keys, controls do not require tight grasping, pinching or twisting of the wrist to operate. Not Applicable  
1194.23(k)(3) If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character. Not Applicable  
1194.23(k)(4) The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound. Not Applicable  

back to top
 

Section 1194.24 Video and Multimedia Products

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.24(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. Not Applicable  
1194.24(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. Not Applicable  
1194.24(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned. Not Applicable  
1194.24(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described. Not Applicable  
1194.24(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. Not Applicable  

back to top
 

Section 1194.25 Self Contained, Closed Products

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.25(a) Self contained products shall be usable by people with disabilities without requiring an end-user to attach assistive technology to the product. Personal headsets for private listening are not assistive technology. Not Applicable  
1194.25(b) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable  
1194.25(c) Where a product utilizes touchscreens or contact-sensitive controls, an input method shall be provided that complies with Section 1194.23 (k) (1) through (4). Not Applicable  
1194.25(d) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not Applicable  
1194.25(e) When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at anytime. Not Applicable  
1194.25(f) When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45 dB, a volume gain of at least 20 dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use. Not Applicable  
1194.25(g) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Not Applicable  
1194.25(h) When a product permits a user to adjust color and contrast settings, a range of color selections capable of producing a variety of contrast levels shall be provided. Not Applicable  
1194.25(i) Products shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Not Applicable  
1194.25(j)(1) The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls. Not Applicable  
1194.25(j)(2) Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor. Not Applicable  
1194.25(j)(3) Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor. Not Applicable  
1194.25(j)(4) Operable controls shall not be more than 24 inches behind the reference plane. Not Applicable  

back to top
 

Section 1194.26 Desktop and Portable Computers

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.26(a) All mechanically operated controls and keys shall comply with Section 1194.23 (k) (1) through (4). Not Applicable  
1194.26(b) If a product utilizes touchscreens or touch-operated controls, an input method shall be provided that complies with Section 1194.23 (k) (1) through (4). Not Applicable  
1194.26(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not Applicable  
1194.26(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards. Not Applicable  

back to top
 

Section 1194.31 Functional Performance Criteria

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.31(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards.
 
1194.31(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 

back to top
 

Section 1194.41 Information, Documentation and Support

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.41(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. Documentation for this product is available in accessible electronic format.  
1194.41(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Documentation for this product is available in accessible electronic format.  
1194.41(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html. 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