Downloaded 40 times
Uploaded bySean Yo
Getting Started With Web Accessibility
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.
More Related Content
![How to create a performance-first culture [2018 WebPerfDays Amsterdam]](https://cdn.slidesharecdn.com/ss_thumbnails/2018-webperfdays-181116191738-thumbnail.jpg?width=640&height=640&fit=bounds)
![The hunt for the unicorn performance metric [DeltaV London 2018]](https://cdn.slidesharecdn.com/ss_thumbnails/2018-deltav-unicorn-metric-180511092516-thumbnail.jpg?width=640&height=640&fit=bounds)
![[Vietnam Mobile Day 2014] Touch the future of the web - Nguyễn Việt Anh – Cou...](https://cdn.slidesharecdn.com/ss_thumbnails/topic9nguyenvietanh-140526055316-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Getting Started With Web Accessibility
Getting Started With Web Accessibility
- 1. Getting Started withWeb Accessibility@seanyoSeanYo.casean.yo@uoguelph.ca
- 2. What is WebAccessibility?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 AbilitiesWebAccessibility BarriersAuditory1Cognitive and Neurological2Physical/Motor3Speech4Visual5
- 4.
- 5. Why Web AccessibilityMakes Sense
- 6.
- 7. Why Have aWebsite?
- 8. To Connect WithPeople
- 9.
- 10.
- 11. People Have ExperiencesChecklists Don’t
- 12.
- 13. The Only OneThat MattersPeople First
- 14. AODA Principles ofAccessibility Independence
- 15.
- 16.
- 17. Equality ofopportunityW3CPrinciples of Accessibility Perceivable
- 18.
- 19.
- 20. RobustUnderstading WebAccessibilityFor Managers & Developers
- 21. Accessibility is SimpleAutomatedTools and Best Practices Lots of great, free tools to measure accessibility
- 22. Lots ofgreat, free info & recommendations
- 23. Using webstandards is good for accessibility
- 24. Tools: WAVE,FAE, TAW, FANGS, NVDA
- 25. Info: WAI,WCAG, WebAIM, WaSP
- 26. Use valid,semantic code - Even better, use a CMSAccessibility is ComplicatedNo Single Path How to measure accessibility?
- 27. Automated testingneeds user testing
- 28. Websites arenot fire &forget – they are a process
- 29. Which Standard?WCAG, 508, AODA
- 30. Lots ofplatforms: IE, Gecko, Webkit + Mobile
- 31. Content willchange & break accessibilityAccessibility is CheapThe Best Stuff is Open & Free Being accessible improves search rankings
- 32. Google isa Screen Reader
- 33. CMS toolsare a strong investment – Open & free
- 34. The besttools are Open & free
- 35. Development bestpractices are Open & free
- 36. CMS toolscan automated compliance : alt tagsAccessibility is ExpensiveYou’re only as Accessible as your last a11y bug… Passing a checklist doesn’t make a site accessible
- 37. Accessibility ischallenging and doesn’t end
- 38. Leaving itto the end is costly – in time and money
- 39. Web developmentis a mature profession
- 40. Accessibility isa critical dimension of webdev
- 41. A11y isexpensive to retrofit, like schemas & securityAccessibility is Cheap & Simple…
- 42.
Editor's Notes
- #3 http://en.wikipedia.org/wiki/Web_accessibility
- #4 http://www.w3.org/WAI/intro/people-use-web/diversity
- #6 http://accessites.org/why/http://www.webaim.org/intro/
- #12 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
- #14 http://en.wikipedia.org/wiki/Web_accessibility
- #16 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)