Derek Featherstone: Web Accessibility (Webdagene 2013)
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
283
On Slideshare
283
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
8
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Why should that interface be accessible?
  • 2. How would we make that accessible?
  • 3. To whom should it be accessible?
  • 4. • blind • low-vision • hearing • mobility/dexterity • cognitive • speech
  • 5. erceivable perable nderstandable obust P O U R w3.org/WAI
  • 6. P O U R Focuses on user needs, not technology.
  • 7. Web Accessibility is a Design Tool
  • 8. Derek Featherstone feather@simplyaccessible.com @feather
  • 9. Accessibility is part of User Experience.
  • 10. extremes extremes
  • 11. Accessibility is not binary, all-or-nothing, black and white. We have every shade of grey in between. How you view this point frames everything that you learn and do about accessibility.
  • 12. The checklist is a starting point, not an end point.
  • 13. Just because something is compliant, doesn’t mean it will be easy to use.
  • 14. How can we get beyond the checklist?
  • 15. Great design, technical excellence, the right content and functionality.
  • 16. Great design, technical excellence, the right content and functionality.
  • 17. PRINCIPLE 1 Start with content
  • 18. Content specific to people with disabilities?
  • 19. PRINCIPLE 2 Move from what to why.
  • 20. Overlapping Map Polygons: Non-visual access
  • 21. Different method to get the same information (Fictitious) proposed boundary changes, City of Ottawa Does this change affect you? Use our Postal Code lookup: Postal code: Search
  • 22. PRINCIPLE 3 Out of sight, out of mind.
  • 23. GROUP CLOSELY RELATED ITEMS
  • 24. Layout: Proximity for Low-vision users
  • 25. Layout: Proximity for Low-vision users
  • 26. Use layout to create the right "chunks"
  • 27. Use layout to create the right "chunks"
  • 28. PRINCIPLE 4 Design for Quick Consumption
  • 29. Front-loaded content
  • 30. USE HEADINGS FOR QUICK CONSUMPTION
  • 31. PRINCIPLE 5 Keyboard.Keyboard.Keyboard.
  • 32. PRINCIPLE 6 Design for forgetfulness.
  • 33. Summary and Field-level errors
  • 34. These principles help make better, more accessible designs for everyone.
  • 35. simplyaccessible.com/newsletter
  • 36. Derek Featherstone feather@simplyaccessible.com @feather
  • 37. Accessibility consulting, strategy and assessments Accessible development and remediation services Training courses, workshops and conferences simplyaccessible.com feather@simplyaccessible.com @feather on twitter Derek Featherstone