Oracle Voluntary Product Accessibility Template Name of Product: Oracle JDeveloper and Application Development Framework 11g (11.1.1.2)
Last Updated: 14-DEC-2009
Version: This VPAT is no longer valid. 11.1.1.2 For ADF/Faces generated applications: To provide content that is optimized for screen reader users the "accessibility mode" option should be set to "screenReader" in the application's trinidad-config.xml file. To provide content that is optimized for users who leverage platform high-contrast capabilities, the "accessibility-profile" option should be set to "high-contrast" in the trinidad-config.xml file. Both of these options can be dynamically specified on a per-user basis. For more information see the Apache Trinidad Developer's Guide.
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, please 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 VPAT addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses. | back to top
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 meet this standard subject to the remarks on the right | When developing a swing desktop application, if the user is in the structure pane for a frame/dialog, there is no keyboard-only method to go from the structure pane to the source code editor. (In other places in JDeveloper, there is a 'go to source' item in the context menu of the structure pane, but not here.) A possible workaround is to use Ctrl+ Tab which pops up a navigation popup showing all views. While the Ctrl key is pressed, keep pressing the Tab key and move the selection to the Frame. Release the Ctrl key and the focus will be in the code editor. To shift between code editor and UI designer (or any other editor for the same file) use Alt+Page Up/Down. (8890171) The data that is to be displayed in the Geographic Map can easily be rendered in a table component. Given that Geographic Map Theme bindings take a collection to display data, the same collection can be bound to a table component. Bug 8216242 Given the visual nature of the Geographic Map and the tools on the toolbar, we recommend providing alternate renderers like ADF Faces Tables for the data to allow selections in accessible mode. Bug 8368925,8216257 The Application Navigator Display Options can only be reached via a dropdown menu which is not keyboard accessible. (Bug 6073055,6196889) The Refactoring dialog for renaming a Java class member offers to show the extent of this operation in a preview window to allow the user to access the impact. If the user decides it is OK to proceed the user has to press a button in this preview window to actually perform the refactoring operation. However, it is not possible to access this button from the keyboard only. To workaround this issue deselect the option 'Preview' in the Refactoring dialog when using keyboard only. (Bug 6080130) The Tasks window, opened by selecting the menu item 'Tasks' from the main menu 'View', allows the user to add filters to narrow the number of tasks displayed. The construction of such a filter is done in the 'Filter Tasks' dialog. However, if using the keyboard only it is only possible to add a new filter but not to modify its configuration. (Bug 6788671) Using the Advanced Search context menu option from the Resource Palette, adding or removing of search criteria can not be accomplished via the keyboard. (Bug 6790898) It is not possible to add or remove code templates using the keyboard when working in the Preferences - Code Editor: Code Templates page. (Bug 6792631) When disabling row selection in the af:treeTable by setting the rowSelection attribute to 'none', the resulting af:treeTable content is not keyboard navigable. In particular, it is not possible to use the keyboard to navigate to and expand/collapse nodes in the af:treeTable. This issue can be avoided by not disabling row selection for this component. (bug 8295444) | | 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 meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | The Application Navigator Display Options can only be reached via a dropdown menu which is not keyboard accessible. (Bug 6073055,6196889) It is not possible to add or remove code templates using the keyboard when working in the Preferences - Code Editor: Code Templates page. (Bug 6792631) | | 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 meet this standard subject to the remarks on the right | The Hierarchy Viewer component uses a Tree Model/Binding to render the data. The same binding can be wired to a TreeTable component to render an accessible version. The TreeTable will provide the expand and collapse capability to drill down into the hierarchy. ADF Faces components that are used within the Hierarchy Viewer Nodes can be used within the TreeTable stamps to render the data. Bug 8368141 The Application Navigator Display Options can only be reached via a dropdown menu which is not keyboard accessible. (Bug 6073055,6196889) The Refactoring dialog for renaming a Java class member offers to show the extent of this operation in a preview window to allow the user to access the impact. If the user decides it is OK to proceed the user has to press a button in this preview window to actually perform the refactoring operation. However, it is not possible to access this button from the keyboard only. To workaround this issue deselect the option 'Preview' in the Refactoring dialog when using keyboard only. (Bug 6080130) The Tasks window, opened by selecting the menu item 'Tasks' from the main menu 'View', allows the user to add filters to narrow the number of tasks displayed. The construction of such a filter is done in the 'Filter Tasks' dialog. However, if using the keyboard only it is only possible to add a new filter but not to modify its configuration. (Bug 6788671) Using the Advanced Search context menu option from the Resource Palette, adding or removing of search criteria can not be accomplished via the keyboard. (Bug 6790898) When editing Table Columns for a sf html readonly table, the screen reader fails to read the first column, 'Display Table', data for each row in the table. (Bug 8206320) When an application is deployed from JDeveloper, the Deployment Log details all the events during deployment. It is not currently possible for the screen reader to read these details. (Bug 8214814) It is not currently possible to read from the Swing designers using a screen reader. (Bug 8216345) It is not possible to add or remove code templates using the keyboard when working in the Preferences - Code Editor: Code Templates page. (Bug 6792631) For ADF/Faces generated applications: Tree leaf node level is not identified (Bug 8407966). | | 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 meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | | | 1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Product has been developed to meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | For ADF/Faces generated applications: The active data solution currently uses color as the only way to let end users know that a piece of data has been updated (or inserted). Bug 7593356 | | 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 meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | The Application Navigator Display Options can only be reached via a dropdown menu which is not keyboard accessible. (Bug 6073055,6196889) The Refactoring dialog for renaming a Java class member offers to show the extent of this operation in a preview window to allow the user to access the impact. If the user decides it is OK to proceed the user has to press a button in this preview window to actually perform the refactoring operation. However, it is not possible to access this button from the keyboard only. To workaround this issue deselect the option 'Preview' in the Refactoring dialog when using keyboard only. (Bug 6080130) The Tasks window, opened by selecting the menu item 'Tasks' from the main menu 'View', allows the user to add filters to narrow the number of tasks displayed. The construction of such a filter is done in the 'Filter Tasks' dialog. However, if using the keyboard only it is only possible to add a new filter but not to modify its configuration. (Bug 6788671) Using the Advanced Search context menu option from the Resource Palette, adding or removing of search criteria can not be accomplished via the keyboard. (Bug 6790898) When editing Table Columns for a sf html readonly table, the screen reader fails to read the first column, 'Display Table', data for each row in the table. (Bug 8206320) When an application is deployed from JDeveloper, the Deployment Log details all the events during deployment. It is not currently possible for the screen reader to read these details. (Bug 8214814) It is not currently possible to read from the Swing designers using a screen reader. (Bug 8216345) It is not possible to add or remove code templates using the keyboard when working in the Preferences - Code Editor: Code Templates page. (Bug 6792631) | 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 meet this standard subject to the remarks on the right | | | 1194.22(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Product has been developed to meet this standard subject to the remarks on the right | The HierarchyViewer component can only be displayed inside the Adobe Flash Player and in it's current state is not accessible to screen readers. Another component like a tree or a tree table that can output HTML has to be used to provide accessibility support for HierarchyViewer. The Hierarchy Viewer component uses a Tree Model/Binding to render the data. The same binding can be wired to a TreeTable component to render an accessible version. The TreeTable will provide the expand and collapse capability to drill down into the hierarchy. ADF Faces components that are used within the Hierarchy Viewer Nodes can be used within the TreeTable stamps to render the data. Bug 8368141 | | 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 meet this standard subject to the remarks on the right | For ADF/Faces generated applications: The active data solution currently uses color as the only way to let end users know that a piece of data has been updated (or inserted). Bug 7593356 | | 1194.22(d) Documents shall be organized so they are readable without requiring an associated style sheet. | Product has been developed to meet this standard subject to the remarks on the right | | | 1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. | Not Applicable | | | 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 meet this standard subject to the remarks on the right | | | 1194.22(g) Row and column headers shall be identified for data tables. | Product has been developed to meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | | | 1194.22(i) Frames shall be titled with text that facilitates frame identification and navigation. | Product has been developed to meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | | | 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. | Not Applicable | | | 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 meet this standard subject to the remarks on the right | | | 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 Section 1194.21 (a) through (l). | Product has been developed to meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | The Application Navigator Display Options can only be reached via a dropdown menu which is not keyboard accessible. (Bug 6073055,6196889) The Refactoring dialog for renaming a Java class member offers to show the extent of this operation in a preview window to allow the user to access the impact. If the user decides it is OK to proceed the user has to press a button in this preview window to actually perform the refactoring operation. However, it is not possible to access this button from the keyboard only. To workaround this issue deselect the option 'Preview' in the Refactoring dialog when using keyboard only. (Bug 6080130) The Tasks window, opened by selecting the menu item 'Tasks' from the main menu 'View', allows the user to add filters to narrow the number of tasks displayed. The construction of such a filter is done in the 'Filter Tasks' dialog. However, if using the keyboard only it is only possible to add a new filter but not to modify its configuration. (Bug 6788671) Using the Advanced Search context menu option from the Resource Palette, adding or removing of search criteria can not be accomplished via the keyboard. (Bug 6790898) When editing Table Columns for a sf html readonly table, the screen reader fails to read the first column, 'Display Table', data for each row in the table. (Bug 8206320) When an application is deployed from JDeveloper, the Deployment Log details all the events during deployment. It is not currently possible for the screen reader to read these details. (Bug 8214814) It is not currently possible to read from the Swing designers using a screen reader. (Bug 8216345) It is not possible to add or remove code templates using the keyboard when working in the Preferences - Code Editor: Code Templates page. (Bug 6792631) For ADF/Faces generated applications: Error messages for form fields are not read until tabbing past the field. Bug 6662290. | | 1194.22(o) A method shall be provided that permits users to skip repetitive navigation links. | Product has been developed to meet this standard subject to the remarks on the right | | | 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 meet this standard subject to the remarks on the right | For ADF/Faces generated applications:
There is no ability to extend session timeout for generated applications. BUG 7119644 | 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 Multi-media 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 meet 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 meet 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 meet 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. | Not Applicable | There is no reliance on sound. | | 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 meet 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 meet 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 | Support 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. | Information about accessibility features of Oracle products is available in HTML format at www.oracle.com/accessibility. | | | 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 |