Press CTRL+ALT+G to display the Skip to Content link.

Accessibility Features C-5 1. Sign into Oracle BI EE, as described in Signing In Using Keystrokes . 2. Press CTRL+ALT+G to display the Skip to Content link in the upper-left corner of the Home page. 3. Press one of the following: ■ ENTER on this link to navigate to the default starting location on the Home page, which is the first link in the upper-left corner under the global header. ■ TAB to navigate to the first focusable element in the global header. 4. Continue to press TAB to navigate through the elements on the Home page. Navigating in Oracle Business Intelligence Dashboards The following procedure describes one way to navigate a dashboard using keyboard shortcuts. This procedure does not include all keyboard shortcuts and options but serves as an example. To navigate dashboards with keystrokes: 1. Sign into Oracle BI EE, as described in Signing In Using Keystrokes . ■ If the Home page is displayed first, then use keystrokes to display the dashboard. Press CTRL+ALT+D to navigate to the Dashboards menu in the global header, press ENTER to display the menu, press TAB or the arrow keys to navigate through the dashboard names, then press ENTER on the name of the dashboard to display. Proceed to the next step. ■ If a dashboard is displayed, then proceed to the next step. 2. Navigate to the desired dashboard page as follows: a. Press CTRL+ALT+G to display the Skip to Content link. b. Press TAB multiple times to navigate through the global header to the tab that corresponds to the first page of the dashboard. If there are no page tabs, then you navigate to the first focusable element on the dashboard page. Press TAB to move through the dashboard pages. After the last page, pressing TAB gives focus to the dashboard page menu. c. Press ENTER when the focus is on the appropriate page tab to open that page of the dashboard. 3. Press CTRL+SHIFT+S to navigate to the first focusable element in the next section, which is the collapse icon. 4. Press TAB to navigate to the next focusable element in the current section. 5. Press CTRL+SHIFT+S to navigate to the first focusable element in the next section. 6. While the section collapse and expand icon has focus, press ENTER to collapse the current section. 7. To navigate in a table or pivot table: a. Press TAB to select the table. b. Press TAB to move through the headers of the table and to select any menus that exist there. C-6 Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition c. When the table has focus, press the arrow keys to navigate among the columns and body cells of the table To access the drop-down menus in the header rows when a body cell has focus, press TAB, then ENTER to display the options for the menu in the first header row. Press TAB and use the arrow keys to highlight the options in the menu and press ENTER to select the desired option. Designing for Accessibility When creating content for consumption by a wide variety of users, you must plan to provide support for users with various disabilities. Such support is a legal requirement in many locations throughout the world. You can follow several general guidelines when designing content for consumption by a variety of people with differing abilities. These guidelines apply to any content that you create for Oracle BI EE or other applications. You must also be aware of features that are specific to Oracle BI EE that ensure that the content that you provide supports accessibility requirements. This section contains the following topics on designing for accessibility: ■ Obtaining General Information ■ Avoiding Common Misconceptions ■ Following Best Practice Recommendations ■ Following General Guidelines for Accessible Content ■ Designing Dashboards that are Accessible Obtaining General Information You can locate information about accessibility across the Information Technology industry in numerous published books. This guide does not intend to duplicate those works. Various standards and legislation are documented, especially as part of the World Wide Web Consortium W3C and Section 508 of the United States Rehabilitation Act. Avoiding Common Misconceptions Many designers make assumptions about technology and accessibility. Some of the more common misconceptions include: ■ HTML content automatically equals accessible content. ■ Accessible tools automatically create accessible content. ■ Automated testing tools can reliably determine accessibility. None of these assumptions, however, is correct. Developers can create non-accessible content using HTML. A tool that can produce accessible content might not do so by default, or might allow a developer to select options that turn off the accessible features within existing accessible content. Automated testing tools do not always interact with content the same way end that users do. As a result, they can erroneously report accessible elements as non-accessible. Therefore, accessibility is ultimately the responsibility of the content designer. When creating content, designers must be aware of certain common practices to ensure the content is accessible to all users. Accessibility Features C-7 Following Best Practice Recommendations When configuring or creating content for dashboard pages, consider the following best practice recommendations: ■ Refrain from using tickers, because they are not supported. ■ Reduce the interactivity and the complexity of pages. For example, restrict the number of prompts and drop-down menus, do not use the drill-inline feature for sections, and configure tables to show as many rows as possible. Following General Guidelines for Accessible Content Always consider the fact that multiple disabilities exist and that multiple disabilities might manifest in the same individual. You must also remember that there are varying degrees of certain disabilities such as the various types of color vision deficiency. Your designs must take all these possibilities into account. This section contains guidelines on the following general areas of design: ■ Font Selection ■ Color Selection ■ Color Contrast Font Selection Users with low visual acuity often use screen magnification software to make the screen easier to read. The fonts that you use should be readable even when magnified by accessibility tools by as much as 20 times. Some fonts do not display well when magnified, while others do. Oracle BI EE dashboards use style sheets to set standard display definitions. Ensure that these style sheets consistently use font selections that magnify well. That way, content creators automatically default to using fonts that are accessible. Color Selection Many different types of color vision deficiency exist, from an inability to see the difference between one common color pair such as red-green the most common deficiency, all the way to full color blindness where a person can see only varying shades of gray and black. Using only color to convey critical information means that certain users are not fully aware of all the pertinent information about a subject. And, of course, a blind user needs any information conveyed by color to also be present in an alternate textual format. As a developer, you must not create any content that provides key information by color alone. One example of a non-accessible design is to denote negative numbers solely by coloring the text red. Another example is a typical stoplight indicator where the only context information comes from its color — green for good and red for bad. Using Color with Text You can use color in designs if you also include another indication of the same information. For example, you can include a minus sign or parentheses to denote negative numbers in tables and pivots. For stoplight displays, you can add descriptive text or different shaped icons in addition to the color. You can include text such as Status: good. You can include green circles for good, yellow triangles for warning, and red octagons for bad. C-8 Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition Color Contrast Because color vision deficiency can also manifest as an inability to distinguish between subtle shades of similar colors, overall color design of all screen elements must provide a large amount of contrast. You should strive to achieve a minimum of a 4.5:1 color luminosity contrast ratio. For example, use black text on a white background instead of dark gray text on a light gray background. You can check the following Web sites for assistance: ■ This site offers a tool that can test for the proper level of contrast: http:www.paciellogroup.comresourcescontrast-analyser.html ■ This site offers a tool for viewing how a Web site is displayed for individuals with various types of color vision deficiency: http:colorfilter.wickline.org Designing Dashboards that are Accessible Use the guidelines in the following sections for designing accessible dashboards: ■ Promoting a Consistent Structure ■ Keeping Dashboard Pages Simple ■ Enhancing On-Screen Content ■ Providing Alternate Displays ■ Avoiding Prohibited Features Promoting a Consistent Structure Use the following guidelines to promote a consistent structure for dashboards: ■ If multiple dashboards contain similar functions or content, then keep those links or forms in the same place on all dashboards. ■ Use the same text and labels for buttons and links that have the same functions or destinations. When graphical elements are used to identify controls, status indicators, or other programmatic elements, ensure that the meaning assigned to each graphical element is consistent throughout the pages of the dashboard. ■ Associate the same text with icons and other graphics that are used for the same functions. Graphics cannot be read by assistive technologies, and low-vision users might be unable to discern the meaning of a graphic. Therefore, all graphics must have additional text to describe the functionality. Graphics must have ALT text, which is descriptive text associated with the graphic that adequately describes its purpose. This alternate text is specified using the ALT attribute for the element in HTML code. Even if a graphic is present for aesthetic purposes and has no functional value, then you must still specify null ALT text alt= for its element so that screen readers know that the text should be skipped. For other graphical elements that do not support creation of ALT text, you should include text fields at the top or side to denote functionality, such as Select a Display View Below. Accessibility Features C-9 Keeping Dashboard Pages Simple Try to keep dashboard pages simple. Do not try to include too many objects on one page. Include multiple pages that are easy to navigate rather than one page that is cluttered and difficult to navigate. Enhancing On-Screen Content Use the following guidelines to enhance on-screen content for dashboards: ■ As you do in graphs to promote a high color luminosity contrast ratio, do not use colored or patterned backgrounds for dashboard pages. ■ Use styles that support high contrast between the background and the text, both in the dashboard header area and in the tabs on multi-page dashboards. ■ Place the most important content at the top of the page so that users of screen readers can access that content without having to navigate the entire screen. Providing Alternate Displays For displays that are inherently visual, such as interactive GIS maps or audio-video feeds, no method might exist for making these elements directly accessible. When you deploy this kind of content, you must also provide a text-based equivalent display of the same information with similar interaction capabilities. Typically this means either creating an equivalent table or pivot table of the related data if applicable, or providing a caption and text description for audio-visual content. Including Descriptions for Analyses Dashboard pages generate explanatory text for objects based on their description fields. Ensure that each analysis that you create includes a short description of its functionality. You specify this description in the Description field of the Save dialog for the analysis. Working with Styles for Dashboards The set of styles and skins that are available for the Oracle BI EE system controls the overall look and feel of any dashboard. You can work with styles and skins for accessibility, as described in the following sections: ■ Creating Custom Styles and Skins ■ Applying a Style to a Dashboard Creating Custom Styles and Skins You can create custom styles and skins to implement standard settings that support accessibility, such as default font selections, high-contrast color schemes, and so on. You can start by copying and modifying the default styles. By modifying these files, you can select default colors, contrast, and fonts that can benefit users with certain disabilities. Applying a Style to a Dashboard You can set a default style for all dashboards and you can also select a style to apply to an individual dashboard. You might want to create a set of dashboards with content that is specifically optimized for users with accessibility needs. You might also want to apply a special accessibility style to one or more individual dashboards for those users who need it. You specify a style on the Dashboard Properties dialog for a particular dashboard. C-10 Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition Avoiding Prohibited Features Certain features should not be used at all, such as elements that blink with a frequency between 2Hz and 55Hz, or that use excessive animation such as a stock ticker display widget. Ensure that you are familiar with all legally mandated design prohibitions that apply in your locality and avoid including those elements on dashboard pages. Using Objects to Enhance Accessibility This section contains the following topics that provide examples of using objects to enhance accessibility: ■ Switching Content with View Selectors ■ Using Static Text Objects for Custom HTML Markup Switching Content with View Selectors In some cases, you might want to create additional content that is specifically optimized for users with accessibility needs. The view selector is a useful tool for providing the most feature-rich content for all user communities. For example, suppose that you have a view called HR Pie Graph that uses color to show job categories in slices. This graph can be the default view for the dashboard page. You can include a view selector on the page that allows users to select either a table or a graph with cross-hatching instead of color for displaying the data. The graph can also add text elements that display the actual values that each slice represents, can simplify the background grid, and can include a descriptive title. Using Static Text Objects for Custom HTML Markup Screen readers generally use standard HTML markup to provide information for navigating on a page. One of the most commonly used markup tags is the Header tag. The default title view on an Oracle BI EE dashboard includes a Title tag when Accessibility mode is turned on. However, you cannot add other tags to the design of a title view. You can use the static text view to replace the title view and supply the necessary HTML tag at the same time. Select the Contains HTML Markup box in the Results tab: Static Text editor and enter the appropriate HTML code. You can access the styles that are contained in the style sheets for your Oracle BI EE system to ensure consistency with the rest of your dashboards. For example you can create a header for a dashboard that enables you to enter a title marked with the H3 tag and a horizontal rule line underneath. Enter the following HTML code for the static text view: H3My HR ReportH3HR WIDTH=650 ALIGN=LEFT Installing and Configuring BI Composer for Oracle BI EE To install and configure BI Composer for Oracle BI EE: 1. Install the BI Composer shared libraries. For information on installing the shared libraries, see Extending a WebLogic Server Domain to Install BI Composer Runtime Implementation Shared Libraries . Accessibility Features C-11 2. Create the MDS data source to allow modifying connection post deployment. To do so: a. Launch WebLogic Server Administration Console.

b. In the Change Center, click Lock Edit.