Accessibility involves making your application usable by persons with disabilities such as low vision or blindness, deafness, or other physical limitations. In the simplest of terms, this means creating applications that can be used without a mouse (keyboard only), used with a screen reader for blind or low-vision users, and used without reliance on sound, color, or animation and timing.
Oracle software implements the standards of Section 508 and WCAG 1.0 AA using an interpretation of the standards at http://www.oracle.com/accessibility/standards.html
.
This section describes accessibility features that are specific to WebCenter Portal. For general information about creating accessible ADF Faces pages, see Developing Accessible ADF Faces Components and Pages in Developing Web User Interfaces with Oracle ADF Faces. For information about accessibility features in JDeveloper, select the JDeveloper Accessibility node under JDeveloper Basics in the online help table of contents.
This appendix includes the following topics:
WebCenter Portal provides several Composer components that you can add to your application pages to make them editable at runtime. These components provide attributes that are used to generate accessible HTML. To ensure that the pages you create are accessible, you must set the attributes listed in Table B-1.
Table B-1 Accessibility Attributes for WebCenter Portal's Composer Components
Component | Accessibility Attributes |
---|---|
|
No accessibility attributes. |
|
No accessibility attributes. |
|
|
|
No accessibility attributes |
|
|
|
No accessibility attributes |
|
|
When you give users the ability to customize a page at runtime, you must ensure that any customizations are accessible to all users. For all components that users can create at runtime, all accessibility-related attributes are shown in the Property Inspector where users can set them appropriately.
For a list of accessibility-related attributes for WebCenter Portal components, see Table B-1. For a list of accessibility-related attributes for other components, see Developing Accessible ADF Faces Components and Pages in Developing Web User Interfaces with Oracle ADF Faces.
IFrames are not very well accommodated by today's screen readers and so are not permitted by some accessibility standards.
Note:
Portlets created using the Oracle JSF Portlet Bridge have the requireIFrame
container runtime option set to true
because, due to JavaScript issues, these portlets are too complex to render directly on Oracle ADF pages.
WebCenter Portal provides an optional attribute in the adf:portlet
tag called renderPortletInIFrame
. You can set this attribute to false
to avoid ever using IFrames.