Topic- Architecting and Designing for Accessibility.ppt

1、Topic: Architecting and Designing for Accessibility,Information Architecture and Design (LIS 385T)Heejung LimThe University of Texas at Austin School of Information March 7, 2003,Architecting and Designing for Accessibility,What is Accessibility?,Groundwork of universal information architecture for

2、the people having various levels of physical, cognitive, and economic abilities.Accessibility enables every the use of software and hardwareno matter what peoples level of ability is, and where and when they use it,Architecting and Designing for Accessibility,Accessibility is the Law,Section 508 (In

3、formation Technology and People with Disabilities) All federal agencies electronic and information technology is accessibleto people with disabilities.All vendors providing information to federal sites be fully accessible to the disabled.,Websites are no longer the province of a few privileged peopl

4、e: “the Web has become obligatory for anyone who wants to succeedin our information-driven culture” (Lazzaro, 1998),Architecting and Designing for Accessibility,Who are the disadvantaged people?,People with visual impairment.People who are blindPeople who are color blind.People with hearing impairme

5、nt.People with a learning or cognitive impairment (such as dyslexia)People who have outdated equipment (such as older computers, older version of browsers, and slower modems),“The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.“ - Tim Bern

6、ers-Lee, W3C Director and inventor of the World Wide Web,W3C and WAI,Web Accessibility Initiative (WAI) Pursues accessibility of the Web through five primary areas of work: Technology guidelines, tools, education and outreach, and research development,Architecting and Designing for Accessibility,Wor

7、ld Wide Web Consortium (W3C) Develops interoperable technologies to lead the Web to its full potential.,Guidelines for Accessibility,Text and Coding issues Use of Colors Textual link issues Image, graphic, and chart on websites Image maps and PDF file,Architecting and Designing for Accessibility,Gui

8、delines for Accessibility,1. Text and Coding issues,Use logical styles for tags Examples of logical tags : DFN(definition), EM(emphasis- italics),Strong (bold), H1, H2, BIG, SMALLExamples of Physical tags : Font size =14, B(bold), I (Italics)Avoid fixed font sizehttp:/No moving textAvoiding using BL

9、INK and MARQUEE. Use another method to draw attention, such as text size or color.http:/ / http:/ clear and simple language.http:/www.w3.org/WAI/wcag-curric/sam113-0.htm,Architecting and Designing for Accessibility,2. Use of Colors,Guidelines for Accessibility (Cont.),Be careful of colors used again

10、st each otherTest for color deficiencyhttp:/www.toledo- color to convey meaning. http:/www.delta.edu/emptrain/usability/color.html,Architecting and Designing for Accessibility,3. Textual link issues,Words on your links http:/www.utexas.edu/web/guidelines/file_naming.htmlLength of links : Keep your l

11、inks less than 10 words.http:/www.w3.org/WAI/wcag-curric/sam97-0.htmNavigating without a mouse/The order of the linkshttp:/www.w3.org/WAI/wcag-curric/sam74-0.htmhttp:/oc.nci.nih.gov/web508/tabexample.html,Guidelines for Accessibility (Cont.),Architecting and Designing for Accessibility,4. Image, gra

12、phic, and chart on websites,Guidelines for Accessibility (Cont.),ALT attribute of imageshttp:/www.w3.org/WAI/wcag-curric/sam2-0.htmhttp:/www.w3.org/WAI/wcag-curric/sam13-0.htmAnimations : the animations should be stopped after one or two rotations.Use LONGDESChttp:/www.w3.org/WAI/wcag-curric/sam3-0.

13、htmhttp:/www.w3.org/WAI/wcag-curric/sam92-0.htm,Architecting and Designing for Accessibility,5. Image maps and PDF file,Guidelines for Accessibility (Cont.),Client-side image maps : more accessible.http:/www.reeusda.gov/1700/statepartners/usa.htm Server-side image mapshttp:/agprogram.tamu.edu/agropo

14、lis http:/www.extension.iastate.edu/Counties/state.htmlhttp:/www.w3.org/WAI/wcag-curric/sam19-0.htmhttp:/www.w3.org/WAI/wcag-curric/sam24-0.htm“Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape”Using the adob

15、e access sitehttp:/ Provide equivalent HTML files,Architecting and Designing for Accessibility,Bobby http:/www.cast.org/bobby/Netmechanic http:/ HTML Validation Service http:/validator.w3.org4. CSS Validatorhttp:/jigsaw.w3.org/css-validator/,Testing in your website,Architecting and Designing for Acc

16、essibility,“Much information architecture work is focused on helping people findinformation of complete tasks efficiently and effectively”( Rosenfeld & Morville, 2002, p312),Conclusion,Architecting and Designing for Accessibility,Architecting and designing accessibility of the website will not invol

17、ve anymore expense if it is considered at the very beginning.,Brewer, J. (2001). How People With Disabilities Use the Web. Retrieved February 1, 2003 from http:/www.w3.org/WAI/EO/Drafts/PWD-Use-Web/.Brewer, J & Chuter, A. (2003). Policy relating to Web Accessibility. Retrieved February 1, 2003 from

18、http:/www.w3.org/WAI/Policy/. Chisholm, W. & Vanderheiden, G. & Jacobs, I. (1999). Web Content Accessibility Guidelines 1.0. Retrieved February 1, 2003 from http:/www.w3.org/TR/WAI-WEBCONTENT/. Lazzaro, J. (1998). Web Accessibility. Retrieved February 1, 2003 from http:/.Rosenfeld & Morville (2002).

19、 Information Architecture for the World Wide Web. Sebastopol, CA: OReilly & Associates, Inc.Slatin, J.M. & Rush, S. (2003). Maximum accessibility. Boston: Addison-Wesley.Solomon, K. (2002). Building Accessible Web sites in Seven Steps. Retrieved February 1, 2003 from http:/ by Design (2003). Benefit

20、s of Usability. Retrieved February 1, 2003 from http:/.Vaas, L. (2000). Web blind spots. Retrieved February 1, 2003 from http:/ W (2003). Website Accessibility. Retrieved February 1, 2003 from http:/ J. & Ffolliott, L. (2001). Web Site Accessibility. Retrieved February 1, 2003 from http:/www.lgta.org/accessibility. Williams, M. (1999). Accessibility. Adobe magazine: Summer, 39-41.,References,Architecting and Designing for Accessibility,