Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Building accessible forms
You can use the Forms Designer to make your system more accessible. In addition to the accessible attributes, you can customize forms for easier readability and information manipulation.
| Attribute name | Definition |
|---|---|
| accessiblename option | Give a form element a name compatible with a screen reader. |
| accessibledescription option | Give a form element a description compatible with a screen reader. |
Accessible Web client forms
The accessible mode of the Web client allows users that require different levels of accessibility to apply personal preferences to improve their user experience. The accessible Web client also enables accessibility tools, such as screen readers, to work with Service Manager. The accessible Web client omits the graphical workflow feature, and thread navigation links, which are the tabs that identify open forms in the Windows client.
If you are designing forms for accessible use, these are the most important design requirements:
- High-contrast color graphics
- Larger default fonts
- Larger form spacing (more white space)
- Simplified navigation (fewer buttons, objects and icons)
- Browser settings must be able to control
- Resizing fonts
- Foreground and background color selection
A visually impaired user might want a well–designed form that reads left to right with labels announcing the name of the subsequent form object and tables with row labels that read horizontally (not by column). This user might also want to specify a black background with white text in a 14–point bold font, instead of the default color and font combinations.
Putting the HTML Editor on accessible forms
The HTML Editor must be the last widget in its form for reverse tabbing to work properly. Widgets placed under it cannot be tabbed.
The Accessible Web client ignores the tab stop information set in the Form definition. Instead, the tabbing always moves from left to right and top to bottom so that the tabbing order matches the order in which the widgets are described by a screen reader.
For complex editing requiring 508 compliance, edit the text in a 508 compliant HTML Editor and then paste it into the HTML Editor.
