Abstract

More documents

Recommendations

Info

Failing the Disabled Community 33 Web pages validate to their own published formal grammars for HTML and CSS, the W3C do not provide their own software tool to check Web pages against their accessibility guidelines. Given all the arguments we have made, we, among others, believe that the guidelines simply cannot be properly tested in an automated manner and that, for many of them, only a human check is possible. Publications of the UK Government (http://www.cabinetoffice.gov.uk/e-government/resources/handbook/introduction. asp) and Disability Rights Commission support this view (see Table 1). Web Aim, the Web Accessibility in Mind project, based at Utah State University, publicises its own tools and advice with the statement, “It is impossible for any program to fully check Web accessibility. Human judgment is needed” (Connecticut, 2004). As Peter Blair says on the Web Aim site itself, “Web accessibility requires more than just accessibility tools; it requires human judgment” (Blair, 2004). Not focussing on any one particular tool, the following table is a detailed list of issues that automatic software accessibility packages cannot deal with in a satisfactory way, along with the human check that is actually required. Table 1 shows some of the guidelines that cannot be tested satisfactorily by automated software in general. Some two thirds of the guidelines below are required to achieve the favoured Level AA. Table 1. Automated software failings Issue WC AG Imagery 1.1 Guideline Text (abbr) Provide a text equivalent for every nontext element. Explanatory remarks Visually impaired people use speech synthesis software that reads out the text on Web pages. “Screen readers” and “voice browsers” are perhaps the most commonly known “assistive technologies” used by disabled people to surf the Web. The IMG element of HTML is used to place an image on a Web page. The ALT attribute of this element was introduced in HTML 2 for Web authors to provide a text equivalent for images. The RNIB recommend five words (e.g., ALT= “dog leaps for a stick.” Speech synthesis software reads the ALT text. Automated Software Failing Will accept ALT=image. jpg in the code, as a valid ALT attribute. Human Requirement Alternative text for graphics and imagery must be meaningful, and only human comprehension can provide meaningful ALT text. Copyright © 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
34 Kreps & Adam Table 1. continued Issue WC AG Imagery 1.1 Text 3.5 Text 3.6 Text 4.1 Guideline Text (abbr) Provide a text equivalent for every nontext element. Use header elements to convey document structure and use them according to specification. Mark up lists and list items properly. Clearly identify changes in natural language of a document’s text. Explanatory remarks If the dog is leaping for a stick over a canal, and the paragraph of text below the picture is about how funny it is that the dog gets wet, it may be necessary to describe the picture in more detail. The LONGDESC attribute of the IMG element, introduced in HTML 4, allows Web authors to provide the URL of a page where a longer description may be found. Speech synthesis software enables users to “skim” pages in a similar way that sighted users “scan” pages. The software reads out only the headings and subheadings until a keypress stops the “skimming” process and the software reads out the paragraphs beneath the subheading selected. The HTML elements to create headings and subheadings, and denotes a paragraph. Speech synthesis software enables users to select different tones and genders of voice for reading out different elements including headers and subheaders, links, and lists. The HTML elements , , and denote unordered (bulleted), ordered (numbered), and definition (question and answer) lists. Speech synthesis software needs to be told when, for example, a French phrase appears in a paragraph of English text. “C’est la vie” will only be pronounced in an intelligible way if the appropriate language identifiers are used in the code. Automated Software Failing Cannot tell if graphic requires LONGDESC. Can only detect absence of – in code and recommend a human check. Cannot detect when a heading or subheading has been placed in a . Can only detect absence of ,,, etc. Cannot detect when a list has been placed in a series of paragraphs or in a table, which is a frequent practice. No automated accessibility checking software (currently available) contains full dictionaries of multiple languages to scan for such changes. Human Requirement Human comprehension of a page is required to decide whether a longer description of a graphic is needed. For headings and subheadings to be meaningful, human comprehension of a page of text is required, and human selection of headings made for appropriate mark-up. Marking up lists appropriately requires a human understanding of what is a list and what is not. Changes in natural language must be accurately identified by human comprehension – particularly for names that are unlikely to appear in dictionaries. Copyright © 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited.
Page 2 and 3: Advances in Universal Web Design an
Page 4 and 5: Advances in Universal Web Design an
Page 6 and 7: Section.V:.Accommodating.Disabiliti
Page 8 and 9: The book puts the emphasis on the u
Page 10 and 11: from the commercial and cultural fi
Page 12 and 13: Acknowledgments We would like to wa
Page 14 and 15: Web Access b l ty and the Needs of
Page 38 and 39: Chapter II Failing the Disabled Com
Page 40 and 41: Failing the Disabled Community 27 L
Page 42 and 43: Failing the Disabled Community 29 a
Page 44 and 45: Failing the Disabled Community 31 X
Page 48 and 49: Table 1. continued Issue WC AG Text
Page 50 and 51: Failing the Disabled Community 37 L
Page 52 and 53: Failing the Disabled Community 39 H
Page 54 and 55: Failing the Disabled Community 41 I
Page 56 and 57: Chapter III Designing Children’s
Page 58 and 59: Figure 1. Grace’s story Designing
Page 60 and 61: Designing Children’s Multimedia 4
Page 62 and 63: Sara Bridget: Do you use the comput
Page 68 and 69: Figure 3. Trouble on the Island by
Page 70 and 71: Figure 4. The Kitten Family and Cat
Page 80 and 81: Curriculum-Focused Design Designing
Page 86 and 87: Chapter.IV Bonded.Design: A.Methodo
Page 88 and 89: Bonded Des gn Contextual design cal
Page 90 and 91: Figure 1. Model of bonded design DE
Page 92 and 93: Table 1. Timetable for History Trek
Page 94 and 95: Group.Discussion Bonded Des gn A fr
Page 96 and 97:
Bonded Des gn Figure 3. Portal prot
Page 98 and 99:
Bonded Des gn Figure 7. Retrieval d
Page 100 and 101:
Bonded Des gn Figure 9. HTML mock-u
Page 102 and 103:
Bonded Des gn Bonded.Design.from. t
Page 104 and 105:
Bonded Des gn Figure 14. Results di
Page 106 and 107:
Bonded Des gn from the topics menu,
Page 108 and 109:
Bonded Des gn Proceedings of the Ca
Page 110 and 111:
Age ng and ts Impl cat ons for Elde
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Gender Issues in HCI Design for Web
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Cognition Layer Gender Issues in HC
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Action Man: http://www.actionman.co
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
(e.g., Web logs). Gender Issues in
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Introduction Interpret ng the Femal
Page 170 and 171:
Interpret ng the Female User gender
Page 172 and 173:
Interpret ng the Female User … co
Page 174 and 175:
Interpret ng the Female User of suc
Page 176 and 177:
Concept.Development.and.Brand.Desig
Page 178 and 179:
Interpret ng the Female User closur
Page 180 and 181:
Interpret ng the Female User sugges
Page 182 and 183:
Interpret ng the Female User standi
Page 184 and 185:
Interpret ng the Female User of per
Page 186 and 187:
Interpret ng the Female User in for
Page 188 and 189:
Interpret ng the Female User Vicker
Page 190 and 191:
Section IV Cultural Issues Interpre
Page 192 and 193:
From Computer-Mediated Colonization
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Introduction A Case Study For the p
Page 214 and 215:
A Case Study 0 professional positio
Page 216 and 217:
A Case Study 0 health services, hou
Page 218 and 219:
A Case Study 0 centers have compute
Page 220 and 221:
A Case Study 0 3. Information about
Page 222 and 223:
Figure 2. Information visual hierar
Page 224 and 225:
Figure 4. Site’s navigation schem
Page 226 and 227:
A Case Study •. Summary.of.the.se
Page 228 and 229:
A Case Study tors have a good under
Page 230 and 231:
A Case Study computer. Many Somalis
Page 232 and 233:
Section V A Case Study Accommodatin
Page 234 and 235:
Web S te Des gn for People w th Dem
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Avoid.Distractions Web S te Des gn
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Compar ng Comprehens on Speeds and
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Table 1. Basic demographic of the t
Page 280 and 281:
Figure 2. Median time vs. readabili
Page 282 and 283:
Page 284 and 285:
Implement ng Access ble Onl ne Lear
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
About the Authors About.the.Authors
Page 308 and 309:
About the Authors ment at the Scien
Page 310 and 311:
About the Authors puter officer at
Page 312 and 313:
About the Authors Bridget.Patel is
Page 314 and 315:
A AAMI (see age associated memory i
Page 316 and 317:
H HCI (see human-computer interacti
Page 318 and 319:
Single Journal Articles and Case St
show all

Abstract

Create successful ePaper yourself

Delete template?

Save as template?