Web accessibility Principles
5 likes2,560 views
The document discusses web accessibility, emphasizing its importance for users of all abilities and disabilities. It highlights principles and practices to ensure equal access to information and functionality, underscoring the need to plan for accessibility from the beginning of the design process. Additionally, it provides resources and guidelines to improve user experience and compliance with accessibility standards.
Web accessibility Principles
- 1. Web AccessibilityPrinciplesSean Yo • Guelph Web Makers Meetup 1.0@seanyo• seanyo.ca • syo@uoguelph.ca
- 3. Pop Quiz:What is A11y?
- 4. What is Web Accessibility?
- 5. 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 have equal access to information and functionality.http://en.wikipedia.org/wiki/Web_accessibility
- 8. Doing the Right Thing
- 11. Be Recognized
- 12. It’s the Law… Or it Will Be
- 15. Care and Sleep Well
- 16. Google Will Love Youhttp://accessites.org/why/http://www.webaim.org/intro/
- 17. User Experience
- 19. People Have ExperiencesChecklists Don’t
- 21. PrinciplesFoundations of Web Accessibility
- 22. The Only One That MattersPeople First
- 23. AODA PrinciplesIndependenceDignityIntegrationEquality of opportunity
- 25. Plan for Accessibility……From the Beginning
- 26. 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.”
- 27. Plan for Accessibility……at every step
- 28. Accessibility is not an optionIt is completing a website
- 29. Avoid Assumptions About Your Visitors
- 30. Count on Text Provide Alternatives in Text
- 31. Don’t take control of your visitor’s experience
- 33. Be Usable, Searchable and Navigable
- 34. Be Semantic
- 35. Separate Content & Presentation
- 36. Progressive Enhancement Is the new Graceful Degredation
- 37. Demo TestingAll Alt Text in PlaceTest with Screen ReaderTurn off CSS
- 38. Final TestingReal PeopleDifferent NeedsAssistive Technology
Editor's Notes
- #4: A11y is anabbr for accessibility – a numeronymLike i18n for internationalization We’ll come back to this later…
- #7: VisualBlindness low vision color-blindnessHearingDeafnessMotorInability to use a mouse slow response time limited fine motor controlCognitiveLearning disabilities distractibility inability to remember or focus on large amounts of information
- #8: Making a web site accessible is work – but so is following all types of coding best practices like keeping presentation code in CSS, using HTML semantically, and using readable white space in your code There is the simple motivation of pride in craft…but more important the purpose of a web site is to communicate If you ignore accessibility, your website will be less successful When you pay attention to accessibility, in my experience, the whole website is better for everyone Let’s look to the built environment – ramps, powered doors and extra railings are an accessibility features – but they can potentially help anyone in that building
- #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
- #13: “considering accessibility as a separate item is the wrong approach. We really need to be considering the ideals of universal design, in which everything is designed for everyone. Let’s just for a minute forget about accessibility as a separate issue. We need to design and develop for people using AT just like we do for any other usability issue”
- #17: 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)
- #20: Providing an Accessible Experience requires contintuous and iterative design and testing