ADF Faces Component Accessibility Guidelines

Developing Accessible ADF Faces Pages 22-7 you can mark multiple columns as row headers. When you mark multiple columns as row headers, they appear as the initial columns of the table, and they are frozen. Sometimes, for display purposes, you may not want to have a row header. In such a case, you must define one column in the table to have the rowHeader attribute set to unstyled. In screen reader mode, the table or the tree table component with the unstyled row header column is moved to the starting position with displayIndex set to 0, and it is frozen. In default mode, the table or tree table component with the unstyled row header column is not moved to the starting position, it is not frozen, and it is rendered without any row header CSS style.

22.3.3 ADF Data Visualization Components Accessibility Guidelines

To develop accessible ADF Data Visualization components, follow the accessibility guidelines described in Table 22–2 . Components not listed do not have accessibility guidelines. Table 22–2 ADF Data Visualization Components Accessibility Guidelines Component Guideline dvt:projectGantt dvt:resourceUtilizati onGantt dvt:schedulingGantt Specify the summary property. The summary should describe the purpose of the Gantt chart component. dvt:gauge Specify the shortDesc property. 22-8 Web User Interface Developers Guide for Oracle Application Development Framework dvt:areaGraph dvt:barGraph dvt:horizontalBarGrap h dvt:bubbleGraph dvt:comboGraph dvt:funnelGraph dvt:lineGraph dvt:paretoGraph dvt:pieGraph dvt:radarGraph dvt:scatterGraph dvt:stockGraph Specify the shortDesc property. The shortDesc property should describe the purpose of the graph. Note that in screen reader mode, an instance of pivot table component substitutes the graph component, and the end user can then use the standard cursor keys to navigate through the data. In screen reader mode, the following visualization features of the graph component are not supported: ■ Data change animation during partial page rendering. ■ Zoom and Scroll. Scrolling is supported in pivot table. ■ The seriesRolloverBehavior and hideAndShowBehavior properties on simple graph tags. ■ The interactiveSliceBehavior property on pie graphs. ■ Precise control of data marker shapes and colors, including the following: ■ Declarative properties on the Series child tag ■ Declarative markerShape and markerColor properties on Scatter graphs ■ Callback APIs ■ Conditional formatting rules from a backing bean ■ Marker underlays for bubble and scatter graphs In screen reader mode, the following interactive features of the graph component are not supported: ■ Context menu facets ■ Popups ■ TimeSelector functionality through the dvt:timeSelector child tag ■ The drillingEnabled property of simple graph tags ■ ShapeAttributes support, and access to fine-grained mouse and key events from all graph components ■ Drag and drop in bubble and scatter graphs ■ DataSelection in bubble and scatter graphs ■ Programmatic TickLabelCallback support dvt:pivotTable Specify the summary property. The summary should describe the purpose of the pivot table component. dvt:sparkChart Specify the shortDesc property. Table 22–2 Cont. ADF Data Visualization Components Accessibility Guidelines Component Guideline Developing Accessible ADF Faces Pages 22-9

22.3.4 How to Define Access Keys for an ADF Faces Component

In the Property Inspector of the component for which you are defining an access key, enter the mnemonic character in the accessKey attribute field. When simultaneously setting the text, label, or value and mnemonic character, use the ampersand character in front of the mnemonic character in the relevant attribute field. Use one of four attributes to specify a keyboard character for an ADF Faces input or command and go component: ■ accessKey: Use to set the mnemonic character used to gain quick access to the component. For command and go components, the character specified by this attribute must exist in the text attribute of the instance component; otherwise, ADF Faces does not display the visual indication that the component has an access key. Example 22–1 shows the code that sets the access key to the letter h for the af:goLink component. When the user presses the keys ALT+H, the text value of the component will be brought into focus. Example 22–1 AccessKey Attribute Defined af:goLink text=Home accessKey=h ■ textAndAccessKey: Use to simultaneously set the text and the mnemonic character for a component using the ampersand character. In JSPX files, the conventional ampersand notation is amp;. In JSP files, the ampersand notation is simply . In the Property Inspector, you need only the . Example 22–2 shows the code that specifies the button text as Home and sets the access key to H, the letter immediately after the ampersand character, for the af:commandButton component. Example 22–2 TextAndAccessKey Attribute Defined af:commandButton textAndAccessKey=amp;Home ■ labelAndAccessKey: Use to simultaneously set the label attribute and the access key on an input component, using conventional ampersand notation. Example 22–3 shows the code that specifies the label as Date and sets the access key to a, the letter immediately after the ampersand character, for the af:selectInputDate component. Example 22–3 LabelAndAccessKey Attribute Defined af:inputSelectDate value=Choose date labelAndAccessKey=Damp;ate ■ valueAndAccessKey: Use to simultaneously set the value attribute and the access key, using conventional ampersand notation. Example 22–4 shows the code that specifies the label as Select Date and sets the access key to e, the letter immediately after the ampersand character, for the af:outputLabel component. Note: The dvt:hierarchyViewer and dvt:map components do not have built-in accessibility support, and therefore do not have accessibility guidelines. You must provide alternate, accessible access for these components.