This chapter provides information about how to configure and use accessibility features for Oracle BI Enterprise Edition. It contains the following topics:
This section contains the following topics:
The accessibility features in Oracle BI EE aim to make aspects of navigating and using the product easier for persons with disabilities and for the aging population. The accessibility features support the use of standards-based assistive-technology hardware and software (such as Freedom Scientific JAWS or Microsoft Narrator). The accessibility features are grouped into these general categories:
Features used by third-party assistive-technology products. These features center on providing a user interface that consists of standard HTML elements that can be easily interpreted by third-party assistive technology products.
Accessibility mode, as described in "Changing to Accessibility Mode".
Keyboard shortcuts that make it easier to navigate content for users with limited or no ability to use a mouse.
For information, see "Keyboard Shortcuts".
Content design capabilities that make it possible for content creators to create content that supports users with accessibility needs. While Oracle BI EE provides accessibility mode that offers many features automatically, you as the designer must create content that meets the accessibility requirements of your user community.
Use the following procedure to sign into Oracle BI EE using keystrokes rather than the mouse.
To sign into Oracle BI EE using keystrokes:
In a browser, display the Sign In page for Oracle BI EE.
Press TAB until you place the insertion point in the User ID field.
Enter the ID and press TAB to place the insertion point in the Password field.
Enter the password and if you are ready to complete the sign-in process, then press ENTER to activate the Sign In button.
If you want to change the language that Oracle BI EE uses, then proceed to the next step.
Press TAB twice to place the insertion point in the Language field.
Use the arrow keys to select the desired language.
Press SHIFT+TAB, then press Enter to activate the Sign In button.
Accessibility mode in Oracle BI EE makes the rendering of the user interface more compatible with screen readers while allowing only that functionality that is supported for users with disabilities to be visible. The following list provides information on accessibility mode:
The "BI Composer wizard" is displayed in place of the "Analysis editor". For more information on BI Composer, see Chapter 14, "Using BI Composer to Work with Analyses."
The Home page does not contain links for accessing the Administration page or for performing most editing functions, such as for editing dashboards.
Graphs and map views are not displayed but are instead converted to one or more annotated tables.
Tables and pivot tables are rendered with appropriate internal annotations to enable screen readers to describe the contents of cells.
Refer to your assistive technology documentation for all applicable table navigation shortcuts.
You cannot use the mouse to modify the layout of a table or pivot table.
The collapse icon is included in the upper-left corner of each section on a dashboard page, even if that section is marked as not collapsible in the Dashboard builder. This allows the icon to be the first element that receives focus when using the keyboard to navigate on a dashboard page.
If the dashboard page is refreshed, even if you navigate to another page, then the location of the focus is not preserved. You must press TAB to navigate through the focusable items.
By default, Oracle BI EE does not use accessibility mode. Each user can decide whether to enable accessibility mode by using the following procedure.
To enable accessibility mode using keystrokes:
Sign into Oracle BI EE, as described in "Signing In Using Keystrokes".
Press TAB multiple times to navigate through the global header, until the focus is on your user name in the Signed In As area.
Press ENTER, then TAB to highlight the My Account link.
Press ENTER to display the "My Account dialog".
Press TAB to select the "My Account dialog: Preferences tab".
Press TAB to navigate through the fields on the tab until you reach the Accessibility Mode options.
Use the arrow keys to select the On option.
Press ENTER to save your changes and close the dialog.
Refresh the page to see it displayed in accessibility mode.
This section provides the following information about shortcuts:
Both Oracle BI EE and BI Publisher support standard keyboard shortcuts that are used in many software applications. In addition, both components offer shortcuts to perform tasks that are specific to those components. Table C-1 describes general keyboard shortcuts for use with Oracle BI EE and BI Publisher.
Navigates to the first focusable element in the global header, which is the Skip to Content link. This link enables you to bypass the options that are available in the global header and to move to the features that available in the main part of the Home page.
Navigates to the Dashboards popup menu in the global header. You can then press ENTER to display a menu from which you select a dashboard to display.
Navigates to the current dashboard page tab, if the tab is displayed. If there is only one page in the dashboard, then the page tab is not displayed.
Navigates to the first focusable element in the next section. For a dashboard page, the first element is the collapse icon.
Navigates to the first focusable element in the previous section. For a dashboard page, the first element is the collapse icon.
Navigates to the next focusable element.
SHIFT + TAB
Navigates to the previous focusable element.
Navigates to the next menu option.
Navigates to the previous menu option.
Triggers the activity, when the focus is on a link, an image, or a button with an associated URL or activity.
Closes the menu that has the focus.
Table C-2 describes keyboard shortcuts for navigating in dashboards in Oracle BI EE and reports in BI Publisher.
ALT + Up or Down Arrow
Opens drop-down and combo boxes.
CTRL + Up or Down Arrow
Shows the next or previous item in a combo box.
Note:If you use Freedom Scientific JAWS or other screen reader programs, then you must first disable the virtual PC cursor before using the keystroke combinations to navigate the dashboard. You must enable the virtual PC cursor at other times, such as when navigating within table objects on a dashboard.
Table C-3 describes keyboard shortcuts for navigating the "BI Composer wizard". (For more information on BI Composer, see Chapter 14, "Using BI Composer to Work with Analyses.")
Note:The Catalog tree that is displayed in the Catalog tab of the BI Composer wizard is interpreted as a table. To navigate the tree, use the table keystrokes for your screen reader program.
ALT + SHIFT + b
Navigates to the Back button.
ALT + SHIFT + c
Navigates to the Cancel button.
ALT + SHIFT + l
Navigates to the Finish button.
ALT + SHIFT + x
Navigates to the Next button.
ALT + CTRL + m
Navigates to the context menu. For example, selecting an item in the Catalog tree and pressing ALT + CTRL + m displays a menu with options to expand and collapse menu items.
ALT + Down Arrow
Reads the messages in a pop-up window, one by one.
If you display the Home page after signing into Oracle BI EE or by navigating from another location in Oracle BI EE, then you must press CTRL+ALT+G to place the focus on the Skip to Content link in the upper-left corner of the Home page.
To navigate on the Home page with keystrokes:
Sign into Oracle BI EE, as described in "Signing In Using Keystrokes".
Press CTRL+ALT+G to display the Skip to Content link in the upper-left corner of the Home page.
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.
Continue to press TAB to navigate through the elements on the Home page.
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:
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.
Navigate to the desired dashboard page as follows:
Press CTRL+ALT+G to display the Skip to Content link.
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.
Press ENTER when the focus is on the appropriate page tab to open that page of the dashboard.
Press CTRL+SHIFT+S to navigate to the first focusable element in the next section, which is the collapse icon.
Press TAB to navigate to the next focusable element in the current section.
Press CTRL+SHIFT+S to navigate to the first focusable element in the next section.
While the section collapse and expand icon has focus, press ENTER to collapse the current section.
To navigate in a table or pivot table:
Press TAB to select the table.
Press TAB to move through the headers of the table and to select any menus that exist there.
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.
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:
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.
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.
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.
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:
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.
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.
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."
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:
This site offers a tool for viewing how a Web site is displayed for individuals with various types of color vision deficiency:
Use the guidelines in the following sections for designing accessible dashboards:
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."
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.
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.
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.
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.
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:
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.
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.
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.
This section contains the following topics that provide examples of using objects to enhance accessibility:
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.
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:
<H3>My HR Report</H3><HR WIDTH=650 ALIGN=LEFT>
To install and configure BI Composer for Oracle BI EE:
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".
Create the MDS data source to allow modifying connection post deployment. To do so:
Launch WebLogic Server Administration Console.
In the Change Center, click Lock & Edit.
In the Domain Structure pane, expand Services, and then click Data Sources. The Configuration tab of the Summary of JDBC Data Sources pane is displayed.
Click New, and then select Generic Data Source. The JDBC Data Source Properties page is displayed.
In the Name field, enter mds-bicomposer.
In the JNDI Name field, enter jdbc/mds/bicomposer.
In the Database Type box, select Oracle.
In the Database Driver field, select Oracle's Drive (Thin) for Service connections; Versions:9.0.1 and later.
Click Next. The Transactions Options page is displayed.
Accept the default options and click Next. The Connection Properties page is displayed.
Define the connection properties. Use the same properties as those from the mds-owsm data source).
Click Next. The Test Database Connection page is displayed.
Click Test Configuration to verify the connection.
Click Next. The Select Targets page is displayed.
Select the appropriate server targets for the domain.
In the Change Center, click Activate Changes.
Install the BI Composer application. To do so:
Launch Fusion Middleware Control.
Expand Weblogic Domain, right-click bifoundation_domain, select Application Deployment and then Deploy.
In the Select Archive page, use Browse to select the <ORACLE_HOME>/modules/oracle.bi.presentation_11.1.1/bicomposer.ear file.
In the Select Target page, select the appropriate server targets for the domain.
In the Application Attributes page, under Target Metadata Repository, click the pencil icon and select mds-bicomposer from the list, and enter bicomposer for Partition.
In the Deployment Wizard, Deployment Settings page, click Deploy.
Modify the Business Intelligence Presentation Services (BIPS) connection. To do so:
Launch Fusion Middleware Control
Expand Application Deployments, right-click bicomposer, and select System MBean Browser.
In System MBean Browser, expand oracle.adf.share.connections, expand Application:bicomposer, and then click bi-default.
Change the attributes for the connection bi-default to use the installed Oracle BI EE attributes, for example, Host, Port, Username, Password, and click Apply.
Note:For the value of the User field, enter user, and for the value of the Password field, enter password. These values will be substituted with the values for the current user who is signed in to Oracle BI EE.
Click the tree node ADFConnections, click the Operations tab, click save, and click Invoke.
Enable BI Composer in Oracle BI EE by manually adding the following Oracle Business Intelligence configuration setting within the <ServerInstance> element:
<BIComposer> <Enabled>true</Enabled> </BIComposer>
For information on manually adding an Oracle Business Intelligence configuration setting, see "Using a Text Editor to Update Configuration Settings" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To extend a WebLogic Server domain to install BI Composer runtime implementation shared libraries:
Stop the WebLogic Server.
Launch the Configuration Wizard.
Select Extend an existing Weblogic domain, and then click Next.
Select the domain folder (for example, <mw_home>/user_projects/domains/bifoundation_domain), and then click Next.
Select Extend using extension template, and then use Browse to select the following template:
When prompted to override the installed template, click Yes.
Continue clicking Next and change any settings if needed.
Click Extend, and then Done.
Start the WebLogic Server.