Name of Product: ADF: Application Development Framework, 11.1.1.4.0 (output of JDeveloper) 11.1.1.4 Last Updated: 28-Mar-2011 This VPAT applies to only version 11.1.1.4.0. It does not apply to any versions of ADF: Application Development Framework (output of JDeveloper) after this. This VPAT has been superseded by ADF: Application Development Framework, 11g PS4 (output of JDeveloper) 11.1.1.5 This VPAT only covers Application Development Framework (ADF) components (tags), output from Oracle JDeveloper 11.1.1.4.0. For the JDeveloper user environment, refer to the Oracle JDeveloper (11.1.1.4.0) VPAT. ADF is capable of rendering content as described below, when an application developer uses it according to guidance provided in the reference manual, and follows all other applicable accessibility standards and guidelines, and in conjunction with the following 3 runtime modes: To provide content that is optimized for screen reader users, then 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, then the "accessibility-profile" option should be set to "high-contrast" in the trinidad-config.xml file. To view content in large font that works in conjunction with browser zoom, then the "large-fonts" option should be set in trinidad-config.xml file. These options can all be dynamically specified on a per-user basis. For more information, see the Apache Trinidad Developer's Guide. The information provided in this VPAT only applies when the relevant mode is enabled for each applicable technical standard. Also, 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. 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/corporate/accessibility/templates/ 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 VPAT addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses. |
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. | The product is composed of components that were tested for:
Expanding and Collapsing nodes of af:treeTable: 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. This issue exists in AS 11g ver. 11.1.1.4.0, but will be fixed in ver. 11.1.1.5.0. (bug 10260275 PS3 backport of 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. | The product was tested for response to the following operating system accessibility features:
Note: these feature names are the terms used on Windows; other platforms have their own unique terminology. |
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 product was tested for:
|
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 product was tested for:
|
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. | The product was tested for:
|
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. | The product was tested for:
|
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. | The product was tested for:
|
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. | The product contains the following instances of animation:
|
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. | The product was tested for:
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. | The product was tested for:
|
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. | The product does not use flashing or blinking text, objects or other elements. |
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 product was tested for:
|
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. | The product was tested for:
|
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. | If an application using this product contains multimedia functionality provided by a third party product, then please refer to the third party product for further information.
|
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. | The product was tested for alternative means used for conveying color related information. 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. | The product was tested for:
|
1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. | Product has been developed to meet this standard subject to the remarks on the right. | This product contains no server-side image maps. |
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. | Graph components that are configured to render in PNG format can generate an image map with the ALT attribute on each AREA element. If the application is configured in screen reader mode, graph components will render data in a pivot table format. Gauge components that are configured to render in PNG format may generate a simple image map with the ALT attribute on each AREA element 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)
|
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. | The product was tested when using simple data tables for:
|
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. | The product was tested for more complex elements in a data table:
|
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. | The product was tested for:
|
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. | The product does not use flickering text, objects or other elements. |
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 meet this standard subject to the remarks on the right. | An equivalent text only page is not needed since information and functionality is available within the product, to the extent indicated in each applicable standard. The Hierarchy Viewer (hv) component uses a Tree Model/Binding to render the data when in accessibility mode, which provides a different view of the same page and is the text equivalent to the flash object. 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(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. | Content generated by JavaScript has been coded to meet other applicable standards, to the extent indicated. Please see www.oracle.com/accessibility/standards.html on use of JavaScript. |
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 meet this standard subject to the remarks on the right. | If the platform supports Flash and the Flash player is not detected, the user will be prompted to install the Flash player.
|
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 product was tested for:
Read-only input components, such as af:inputText, are currently rendered by ADF Faces as plain text. As such, there is a loss of information that may be meaningful to screen reader users - ie. screen reader users have no way to determine that the text in question corresponds to a input control. In addition, since plain text content is not included in the tab navigation order, screen reader users may fail to recognize that this read-only content is present on the page. This issue exists in JDEVADF ver. 11.1.1.4.0, but has been fixed in ver. 11.1.1.5.0 version to be released later in 2011. (bug 5889673) Keyboard user needs ability to move the keyboard focus to a new node without also selecting that node. Enhancing attribute may enable opt-in behavior to support separate focus and selection capabilities. (bug 6407364) |
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. | When in screenreader mode, the application contains a "skip to main content" navigation link. Structure and hierarchy can be marked up with Header elements. |
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. | Application timeout options to continue or exit are provided after a period of application inactivity. |
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.
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. |