Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Real World Web Accessibility

2,312 views

Published on

Ever wonder what web accessibility really looks and feels like? Join Rob Geddes and Sean Yo, analysts with Computing and Communication Services, as they present a case study of their recent project is in the process of migrating the University of Guelph Chief Information Officer website. Rob and Sean share their common-sense approach to accessibility and the story of how they engaged web accessibility in moving the CIO website to Drupal platform, a popular open source content management system. Join us for this real world report from the trenches of web accessibility.

Published in: Technology, Design
  • Be the first to comment

Real World Web Accessibility

  1. 1. Aiming for Accessibility Conference 2009
  2. 2. Real World Web Accessibility Robert Geddes Senior Analyst & Cluster Lead of CCS Web Solutions Our Story Sean Yo System Analyst & Web Hosting Service Lead Our Approach In this presentation we share the case study of a real web design Our Strategies project and tell the story of how we engaged accessibility as part of that project. Our Tools
  3. 3. We Are Not Experts
  4. 4. We Are Not Saints
  5. 5. Real World Web Developers
  6. 6. Web Solutions Computing & Communications Services, University of Guelph
  7. 7. Inline Images Workflow Real Time Communication Integrated Video PDF Creation Blogging Pingback Trackback Twitter Document Search Feeds podcasts Rich Commenting Interactive
  8. 8. What about the CIO Web Site?
  9. 9. Accessibility is about Common Sense
  10. 10. What is the purpose of a website?
  11. 11. People Before Compliance
  12. 12. Section 508, §1194.24(c) says: All training and informational video and multimedia productions which support the agency’s mission , regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned.
  13. 13. Ok, we’re using video. Which of our users does this affect? Well, for users who can’t see the video, we should add audio descriptions, and we’ll add captions for people with hearing disabilities. Hmmm – some of our users might not have the video player we’re asking for. We should also add a transcript of the video. Is there anyone else we might be missing?
  14. 14. Right Thing To Do
  15. 15. Avoid Assumptions…
  16. 16. …Except About Text
  17. 17. Clear Content is Good Content
  18. 18. Be Semantic Separate Presentation and Content
  19. 19. Our Users Should Drive the Bus…
  20. 20. …It’s their web. We’re just building it.
  21. 21. Accessibility is a Good Thing
  22. 22. Include Accessibility From Day One
  23. 23. Policy, Validation and Requirements
  24. 24. User Testing
  25. 25. Reuse Proven Code
  26. 26. Content Management System
  27. 27. Join The Conversation
  28. 28. CIO Website
  29. 29. Accessibility is a Team Sport
  30. 30. drupal.org
  31. 31. Test… …with People
  32. 32. Validation
  33. 33. http://tinyurl.com/jaws-sr
  34. 34. Session 2 Rm 103 An Introduction to Web Accessibility Athol Gow, Library Ctr for Students with Disabilities, UofG Session 3 Rm 105 Web Content Accessibility Guidelines Explained Stuart Robertson, Communications and Public Affairs, UofG Session 4 Rm 106 Accessibility for Rich Internet Applications: Fluid, jQuery, Dojo, and Beyond Colin Clark, Adaptive Technology Resource Centre, U of T

×