Web AccessibilityPrinciples<br />Sean Yo • Guelph Web Makers Meetup 1.0<br />@seanyo• seanyo.ca • syo@uoguelph.ca <br />
Web Analyst<br />Accessibility Advocate<br />
Pop Quiz:<br />What is A11y?<br />
What is Web Accessibility?<br />
Web accessibility refers to the practice of making websites usable by people of all abilities and disabilities. When sites...
Visual<br />Hearing<br />Motor<br />Cognitive<br />
Why Web Accessibility?<br />
<ul><li>Doing the Right Thing
Beneficial Standards
Save Internet Resources
Be Recognized
It’s the Law… Or it Will Be
Ease of Maintenance
More Aging Visitors
Care and Sleep Well
Google Will Love You</li></ul>http://accessites.org/why/<br />http://www.webaim.org/intro/<br />
User Experience<br />
Accessibility Experience<br />
People Have Experiences<br />Checklists Don’t<br />
http://manwithnoblog.com/2010/05/20/kill-accessibility/<br />
Principles<br />Foundations of Web Accessibility<br />
The Only One That Matters<br />People First<br />
AODA Principles<br />Independence<br />Dignity<br />Integration<br />Equality of opportunity<br />
W3C Principles<br />Perceivable<br />Operable<br />Understandable<br />Robust<br />
Plan for Accessibility…<br />…From the Beginning<br />
Most errors are introduced during requirements analysis and design.<br />The later they are removed, the most expensive it...
Plan for Accessibility…<br />…at every step<br />
Accessibility is not an option<br />It is completing a website<br />
Avoid Assumptions About Your Visitors<br />
Count on Text <br />Provide Alternatives in Text<br />
Don’t take control of your visitor’s experience<br />
Use Clear Language<br />
Be Usable, Searchable and Navigable<br />
Be Semantic <br />
Upcoming SlideShare
Loading in …5
×

Web accessibility Principles

2,759 views

Published on

A brief introduction to Web Accessibility Principles. Presented at the Guelph Web Maker Meetup 1.0 on March 16, 2011.

Published in: Technology
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,759
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide
  • A11y is anabbr for accessibility – a numeronymLike i18n for internationalization We’ll come back to this later…
  • 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
  • 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
  • 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
  • “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”
  • 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&apos;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)
  • Providing an Accessible Experience requires contintuous and iterative design and testing
  • Web accessibility Principles

    1. 1. Web AccessibilityPrinciples<br />Sean Yo • Guelph Web Makers Meetup 1.0<br />@seanyo• seanyo.ca • syo@uoguelph.ca <br />
    2. 2. Web Analyst<br />Accessibility Advocate<br />
    3. 3. Pop Quiz:<br />What is A11y?<br />
    4. 4. What is Web Accessibility?<br />
    5. 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.<br />http://en.wikipedia.org/wiki/Web_accessibility<br />
    6. 6. Visual<br />Hearing<br />Motor<br />Cognitive<br />
    7. 7. Why Web Accessibility?<br />
    8. 8. <ul><li>Doing the Right Thing
    9. 9. Beneficial Standards
    10. 10. Save Internet Resources
    11. 11. Be Recognized
    12. 12. It’s the Law… Or it Will Be
    13. 13. Ease of Maintenance
    14. 14. More Aging Visitors
    15. 15. Care and Sleep Well
    16. 16. Google Will Love You</li></ul>http://accessites.org/why/<br />http://www.webaim.org/intro/<br />
    17. 17. User Experience<br />
    18. 18. Accessibility Experience<br />
    19. 19. People Have Experiences<br />Checklists Don’t<br />
    20. 20. http://manwithnoblog.com/2010/05/20/kill-accessibility/<br />
    21. 21. Principles<br />Foundations of Web Accessibility<br />
    22. 22. The Only One That Matters<br />People First<br />
    23. 23. AODA Principles<br />Independence<br />Dignity<br />Integration<br />Equality of opportunity<br />
    24. 24. W3C Principles<br />Perceivable<br />Operable<br />Understandable<br />Robust<br />
    25. 25. Plan for Accessibility…<br />…From the Beginning<br />
    26. 26. Most errors are introduced during requirements analysis and design.<br />The later they are removed, the most expensive it is to take them out.<br />Boehm et al (1975): “Some Experience with Automated Aids to the Design of Large-Scale Reliable Software.”<br />
    27. 27. Plan for Accessibility…<br />…at every step<br />
    28. 28. Accessibility is not an option<br />It is completing a website<br />
    29. 29. Avoid Assumptions About Your Visitors<br />
    30. 30. Count on Text <br />Provide Alternatives in Text<br />
    31. 31. Don’t take control of your visitor’s experience<br />
    32. 32. Use Clear Language<br />
    33. 33. Be Usable, Searchable and Navigable<br />
    34. 34. Be Semantic <br />
    35. 35. Separate Content & Presentation<br />
    36. 36. Progressive Enhancement <br />Is the new <br />Graceful Degredation<br />
    37. 37. Demo Testing<br />All Alt Text in Place<br />Test with Screen Reader<br />Turn off CSS<br />
    38. 38. Final Testing<br />Real People<br />Different Needs<br />Assistive Technology<br />
    39. 39. Services:<br />http://wave.webaim.org/<br />http://fae.cita.uiuc.edu/<br />http://www.contentquality.com/<br />http://www.tawdis.net/ingles.html<br />
    40. 40.
    41. 41. http://www.accessconf.ca<br />

    ×