Presentation is loading. Please wait.

Presentation is loading. Please wait.

 Accessibility & Information Architecture Presented by Liz Molleur INF385E April 5 th, 2009.

Similar presentations


Presentation on theme: " Accessibility & Information Architecture Presented by Liz Molleur INF385E April 5 th, 2009."— Presentation transcript:

1  Accessibility & Information Architecture Presented by Liz Molleur INF385E April 5 th, 2009

2 What is Accessibility?  “Web accessibility means that people with disabilities canperceive, understand, navigate, and interact with the Web,and that they can contribute to the Web.” – W3C: WebAccessibility Initiative  “Web accessibility is about making your website accessibleto all Internet users (both disabled and non-disabled),regardless of what browsing technology they're using.” –Webcredible.com

3 Who needs to do this?  All covered entities must be ADA compliant in providing effectivecommunication unless doing so creates an undue burden.  State and Local Governments & Places of Public Accommodation  http://www.justice.gov/crt/foia/tal712.txt http://www.justice.gov/crt/foia/tal712.txt  Government entities receiving Federal Funding - RehabilitationAct of 1973  Anyone wanting to make their site more usable and accessible toa larger population.

4 Who Benefits…  Visual Disabilities  Hearing Impairments  Physical Disabilities  Speech Disabilities  Cognitive and Neurological Disabilities  Multiple Disabilities  Aging-related Conditions  Users of older technology  Users with slower Internet connections  You! http://www.w3.org/WAI/intro/people-use-web.php

5 Information Architecture & Accessibility  (a) Text Tags  (b) Multimedia Presentations  (c) Color  (d) Readability  (e) Server-Side Image Maps  (f) Client-Side Image Maps  (g)&(h) Data Tables  (i) Frames  (j) Flicker Rate  (k) Text-Only Alternative  (l) Scripts  (m) Applets and Plug-Ins  (n) Electronic Forms  (o) Navigation Links  (p) Time Delays Web-based Intranet and Internet Information and Applications (1194.22) http://www.access-board.gov/sec508/guide/1194.22.htm - (e)

6 Text Tags for Non-Text Elements  Navigation Actions  Images with content  Audio Clips  Video Clips  Good for screen readers and crawlers HTML Source Code:

7 Multimedia Presentations Provide captioning for audio portions of site Sync captioning with video to retain full value

8 ColorColor “Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.” - Web-based Intranet and Internet Information and Applications (1194.22) About 7% of the male population in the US is affected by color blindness. - Howard Hughes Medical Institute, 2006

9  Readability  Style Sheets can help clean up HTML making the page more compatible with screen readers and easier to navigate  Recommend using CSS when possible  Keep page layout consistent and organized  Keep text appropriate to your audience  http://www.standards-schmandards.com/exhibits/rix/index.php http://www.standards-schmandards.com/exhibits/rix/index.php  Do not over-ride user defined style sheets http://www.w3.org/TR/CSS-access

10 Image Maps Client-Side  Allows the author to assign text to different “hot spots” on the map for easy navigation with a screen reader  Preferred over server-side image maps for accessibility Server-Side  Use redundant text links for each active region for navigation without a mouse  Only use when regions can not be defined with an available geometric shape

11 Making Tables Accessible  Identify headers for columns and rows  Associate data cells with row and column headers  Use the Scope Attribute  Add a summary  Can make the table more useful but does not replace the need for cell association with headers

12 Frames  Include Text in the body of the frame to identify the contents  Provide Titles for Navigation and Identification   Not supported by all assistive technology yet  Provide a “No Frames” link

13 Frequency of Flicker  “Pages shall be designed to avoid causingthe screen to flicker with a frequencygreater than 2 Hz and lower than 55 Hz.” Text Only Pages  Equivalent information and functionality  Updated with the primary page  Option to meet other compliance needs

14 Scripting Language  Information provided by script must also appear in functional text  Label all images with “alt” attribute  Label images with “title” attribute  Not yet supported for all assistive technologies  Status lines  Can be replaced with an event handler  This information must also be reflected in the “alt” attribute

15 Applications Applets & Plug-ins  Link to a complaint application  Responsibility of the author to do this research before requiring the use of a plug- in  Provide alternative content  Important for users with disabilities as well as those with slower connections

16 Online Forms  Need to allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form  Includes all directions and cues  Use associative labels adjacent to input fields or use an “Explicit Label” tag Explicit Label Tag FIRST NAME: Implicit Label Tag FIRST NAME:

17  Skip Navigation Links  Offer users the chance to skip repetitive navigation menus  Should be Visible at the top of the page  Option of making the link invisible until a user tabs to the space

18 Time Prompt users when time limit is almost expired Allow option for extended time Allow adequate time for users to indicate when additional time is required

19 Testing Your Work  Check the Validity of your site  http://www.webcredible.co.uk/user-friendly-resources/web- accessibility/basics.shtml http://www.webcredible.co.uk/user-friendly-resources/web- accessibility/basics.shtml  Test with users  Use Accessibility Checking Software  http://www.w3.org/WAI/ER/tools/ http://www.w3.org/WAI/ER/tools/  Not a replacement for Human Testing

20 Make a Plan  Establish a policy and create a process for implementation.  Ensure that all new and modified web pages and content are accessible.  Develop a plan for making your existing web content more accessible. Consider making the more popular web pages a priority.  Train staff and contractors responsible for web page and content development.  Provide a way for visitors to request accessible information or services by posting contact information on your home page.  Periodically enlist disability groups to test your work. http://www.ada.gov/websites2.htm

21 Resources W3C Web Accessibility Initiative - http://www.w3.org/WAI/http://www.w3.org/WAI/ Guide to the Section 508 Standards for Electronic and Information Technology (1194.22) – http://www.access-board.gov/sec508/guide/1194.22.htm Webcredible: User experience research & design – http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/ WebAIM: Web Accessibility in Mind – http://www.webaim.org/ Accessibility of State and Local Government Websites to People with Disabilities – http://www.ada.gov/websites2.htm Questions?


Download ppt " Accessibility & Information Architecture Presented by Liz Molleur INF385E April 5 th, 2009."

Similar presentations


Ads by Google