Adobe 65030089 User Guide - Page 279

WebHelp features that support compliance

Page 279 highlights

USING ROBOHELP HTML 9 273 Generating Help and printed documents Text-to-speech utilities read the contents of the active window, available options, or text you type. These utilities and screen review aids translate onscreen text to speech or to a dynamic, refreshable, Braille display. This technology can provide keyboard assistance or shortcuts, captions for speech and sound, and visual warnings such as flashing toolbars. Consider the following when you create Section 508-compliant WebHelp: • WebHelp systems generated with the Section 508 option open in all supported browsers. However, view output with Internet Explorer to ensure compliance. • For master projects generated using pure HTML or Section 508-compliant WebHelp, the subprojects are available only from the TOC if you merge WebHelp systems. They are not available from the index or full-text search. Subprojects appear as a book in the TOC. When users click the subproject TOC book, the subproject opens in a new browser window. WebHelp features that support Section 508 compliance • A Section 508 Compliant option that provides alternative text for images, dynamic elements, frames, forms, and so on. Visually impaired users using assistive software can hear where they are in the output and what they are selecting. • Alternative text is provided for images of TOC books, pages, and the plus/minus icons, TOC/Search/Index tabs or panes, navigation buttons, and buttons from design-time controls. • Other elements with alternative text include expanding and drop-down text, triggers and targets, and pop-up menus. • Navigation frames that assistive software can read. • Generation of HTML tables so that assistive software can identify row and column headers. • Online forms that assistive software can read. • Output that more than one mode of operation and information retrieval can use. For example, mobility-impaired users can use the keyboard or mouse. No features require auditory, visual, or mobility ability alone. Guidelines to ensure Section 508 compliance in Help systems • WebHelp is compliant for framesets and navigation. Make sure that other elements in topics are compliant. • If the Help system contains form buttons or multimedia elements, such as images and audio, provide visual equivalents, such as screen tips so that assistive software can read from the screen. • Construct information with multiple methods of access to accommodate disabilities. Offer information in color in an alternative way that doesn't use color. • Use basic external style sheets so that documents are readable if the style sheet is unavailable. • If a web page uses applets, include a link to the location where users can download the appropriate reader. • Document keyboard shortcuts and other methods of accessibility. • Do not use HTML Help controls. More Help topics "Generate, view, and publish output" on page 291 "Microsoft HTML Help layout" on page 276 "Create custom skins for WebHelp and WebHelp Pro projects" on page 337 "Merging Help projects" on page 96 Last updated 12/14/2011

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380

273
USING ROBOHELP HTML 9
Generating Help and printed documents
Last updated 12/14/2011
Text-to-speech utilities read the contents of the active window, available options, or text you type. These utilities and
screen review aids translate onscreen text to speech or to a dynamic, refreshable, Braille display. This technology can
provide keyboard assistance or shortcuts, captions for speech and sound, and visual warnings such as flashing toolbars.
Consider the following when you create Section 508-compliant WebHelp:
WebHelp systems generated with the Section 508 option open in all supported browsers. However, view output
with Internet Explorer to ensure compliance.
For master projects generated using pure HTML or Section 508-compliant WebHelp, the subprojects are available
only from the TOC if you merge WebHelp systems. They are not available from the index or full-text search.
Subprojects appear as a book in the TOC. When users click the subproject TOC book, the subproject opens in a
new browser window.
WebHelp features that support Section 508 compliance
A Section 508 Compliant option that provides alternative text for images, dynamic elements, frames, forms, and so
on. Visually impaired users using assistive software can hear where they are in the output and what they are
selecting.
Alternative text is provided for images of TOC books, pages, and the plus/minus icons, TOC/Search/Index tabs or
panes, navigation buttons, and buttons from design-time controls.
Other elements with alternative text include expanding and drop-down text, triggers and targets, and pop-up
menus.
Navigation frames that assistive software can read.
Generation of HTML tables so that assistive software can identify row and column headers.
Online forms that assistive software can read.
Output that more than one mode of operation and information retrieval can use. For example, mobility-impaired
users can use the keyboard or mouse. No features require auditory, visual, or mobility ability alone.
Guidelines to ensure Section 508 compliance in Help systems
WebHelp is compliant for framesets and navigation. Make sure that other elements in topics are compliant.
If the Help system contains form buttons or multimedia elements, such as images and audio, provide visual
equivalents, such as screen tips so that assistive software can read from the screen.
Construct information with multiple methods of access to accommodate disabilities. Offer information in color in
an alternative way that doesn’t use color.
Use basic external style sheets so that documents are readable if the style sheet is unavailable.
If a web page uses applets, include a link to the location where users can download the appropriate reader.
Document keyboard shortcuts and other methods of accessibility.
Do not use HTML Help controls.
More Help topics
Generate, view, and publish output
” on page
291
Microsoft HTML Help layout
” on page
276
Create custom skins for WebHelp and WebHelp Pro projects
” on page
337
Merging Help projects
” on page
96