User`s guide

recommends simple navigation that uses the least number of navigation links possible. Either approach
can be effective for your reports, as long as you maintain clarity and consistency.
You may want to use report parts to navigate a report (or to connect several reports). If you provide a
series of links in a page header, keep in mind that screen-reading software will reread the navigation
information every time the user refreshes the page or views a new page. In this case, simple navigation
is preferable.
For a large report, you could provide a list of navigation links as a table of contents in the report header.
More extensive navigation can be useful when you have a large volume of data. To allow users to skip
the list, you could start with a "Skip the table of contents" link that jumps ahead to the first page header.
In general, report navigation should follow these guidelines:
• Identify the target of each link.
• Provide information at the start of the report that describes the layout and navigation.
• Use navigation consistently.
• Provide the opportunity to skip repetitive navigation links.
D.2.5 Parameter fields
When you include parameter fields in a report, make sure they are clear and simple. Although parameter
fields can be a useful tool for providing accessible content, they can also introduce several accessibility
concerns. It is important to test all parameter fields for accessibility.
Parameter fields should follow these guidelines:
• Provide a list of default values for the user to choose from.
Avoid requiring the user to type a value for a parameter. When users provide their own values, they
need to make sure the format of the value will be recognized by the parameter field. A list of default
values is easier to use, and it ensures that the user chooses from values with valid formats.
• Try to avoid complex parameter fields.
A complex parameter field may be more accessible when it is broken down into multiple parameters.
When you test the accessibility of your parameter fields, pay particular attention to parameters that
require a range. It may be easier to understand if you provide two parameter fields that prompt for
discrete values for the top and bottom of the range, rather than ask the user to choose both values
in the same parameter field.
• For date fields, do not allow users to choose their own values.
The calendar used to select date values is not currently accessible. Provide a pick-list of default
date values. Using a list of default values also helps avoid invalid date formats.
2012-03-14689
Creating Accessible Reports