Getting Started With Web Accessibility
•Download as PPTX, PDF•
5 likes•3,724 views
This document provides an introduction to web accessibility. It defines web accessibility as making websites usable by people of all abilities and disabilities. It discusses the diversity of abilities that people have and why web accessibility is important. It outlines some key principles of web accessibility from organizations like the W3C and AODA. It also provides tips for both managers and developers on how to approach web accessibility, noting that it is important to consider from the beginning of a project and that automated tools and open standards can help.
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (20)
Similar to Getting Started With Web Accessibility
Similar to Getting Started With Web Accessibility (20)
More from Sean Yo
More from Sean Yo (18)
Recently uploaded
Recently uploaded (20)
Getting Started With Web Accessibility
- 1. Getting Started with Web Accessibility @seanyo SeanYo.ca sean.yo@uoguelph.ca
- 2. What is Web Accessibility? Web accessibility refers to the practice of making websites usable by people of all abilities and disabilities. When sites are correctly designed developed and edited all users can haveequal access to information and functionality. http://en.wikipedia.org/wiki/Web_accessibility
- 3. Diversity of Abilities Web Accessibility Barriers Auditory 1 Cognitive and Neurological 2 Physical/Motor 3 Speech 4 Visual 5
- 5. Why Web Accessibility Makes Sense
- 7. Why Have a Website?
- 8. To Connect With People
- 11. People Have Experiences Checklists Don’t
- 13. The Only One That Matters People First
- 15. Dignity
- 16. Integration
- 18. Operable
- 19. Understandable
- 22. Lots of great, free info & recommendations
- 23. Using web standards is good for accessibility
- 24. Tools: WAVE, FAE, TAW, FANGS, NVDA
- 25. Info: WAI, WCAG, WebAIM, WaSP
- 27. Automated testing needs user testing
- 28. Websites are not fire &forget – they are a process
- 29. Which Standard? WCAG, 508, AODA
- 30. Lots of platforms: IE, Gecko, Webkit + Mobile
- 32. Google is a Screen Reader
- 33. CMS tools are a strong investment – Open & free
- 34. The best tools are Open & free
- 35. Development best practices are Open & free
- 37. Accessibility is challenging and doesn’t end
- 38. Leaving it to the end is costly – in time and money
- 39. Web development is a mature profession
- 40. Accessibility is a critical dimension of webdev
- 43. Accessibility is Complicated and Expensive…
- 44. …When Fixing Accessibility Problems
- 46. Plan for Accessibility From the Beginning
- 47. Most errors are introduced during requirements analysis and design. The later they are removed, the most expensive it is to take them out. Boehm et al (1975): “Some Experience with Automated Aids to the Design of Large-Scale Reliable Software.” Diagram Source: http://blogs.windriver.com/vxworks/device-management/
- 48. Accessibility is not an option.An inaccessible website is incomplete.
- 49. A vendor claiming a product is accessible does not make it accessible.
- 50. Avoid Assumptions About Your Audience
- 51. Count on Text Provide Alternatives in Text
- 52. Don’t take control of your visitor’s experience
- 54. Testing Is Hard Real People Different Needs Assistive Technology
- 56. Be Usable, Searchable and Navigable
- 57. Be Semantic
- 58. Separate Content & Presentation
- 59. Progressive Enhancement is the new graceful degredation
- 60. Do Periodic A11y Sanity Testing Turn off CSS All Alt Text in Place Test with FANGS/Screen Reader
- 61. Testing Is Fun Real People Different Needs Assistive Technology
- 62. 5:00 PM The Bullring Wednesday, June 1st
Editor's Notes
- http://en.wikipedia.org/wiki/Web_accessibility
- http://www.w3.org/WAI/intro/people-use-web/diversity
- http://accessites.org/why/http://www.webaim.org/intro/
- Makingaccessibile websites can be challenging – and we’ll all make mistakesChecklists are not a bad thing – they can be a useful toolHowever, if you rely solely on checklists – you will generate false positive reports that a site is accessibleChecklists are about as smart as a spellchecker – try and keep that in mind
- http://en.wikipedia.org/wiki/Web_accessibility
- Perceivable - Information and interface must be presentable to users in ways they can perceive.This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses)Operable - User interface components and navigation must be operable.This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform)Understandable - Information and the operation of user interface must be understandable.This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding)Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible)