The 5 Layers of Web Accessibility
•Descargar como ZIP, PDF•
48 recomendaciones•27,243 vistas
In this month's YDN Tuesday Dirk Ginader, Web Developer and part of the Accessibility Task Force at Yahoo!, will talk about Web Accessibility. Starting with basic markup and ending with accessible javascript and WAI ARIA he'll cover best practices and lots of tips and tricks to make your websites and web applications accessible to everyone. Get more information about the event here: http://skillsmatter.com/event/ajax-ria/web-accessibility
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a The 5 Layers of Web Accessibility
Similar a The 5 Layers of Web Accessibility (20)
Más de Dirk Ginader
Más de Dirk Ginader (13)
Último
Último (20)
The 5 Layers of Web Accessibility
- 2. Ogres = Onions = Web Standards?
- 3. LAYERS!
- 4. Common Frontend Development knows 3 Layers
- 6. The 5 Layers of Web Accessibility YDN Tuesday 5.5.2009 Dirk Ginader http://ginader.com http://twitter.com/ginader
- 8. The Markup is the most important Layer of all
- 9. Source order = tab order
- 10. Best matching HTML Element for the job?
- 11. Is the page understandable and usable without CSS?
- 12. Interaction using links, forms and reloads
- 14. CSS can make inaccessible too
- 15. display:none and visibility:hidden hide from everyone
- 16. :hover only works for a mouse
- 17. :focus to the rescue!
- 18. always use them combined: a:hover, a:focus{ /*awesome CSS*/ }
- 19. CSS is for Design not for Interaction
- 21. Javascript is the icing on the cake
- 22. Does anything, you need the user to do, work without Javascript?
- 23. then we can add some Magic
- 25. create new buttons for JS only interactions
- 26. Screenreaders do know JS. They often just don’t know what happens...
- 27. focus() to the rescue!
- 28. mind the tab order
- 29. focus() to the rescue!
- 30. tabindex=0 makes even divs keyboard accessible
- 31. tabindex=-1 for JS only tab access
- 32. yeah focus()
- 33. Ajax = delays = tricky to communicate
- 34. inform about what happens!
- 35. you guessed it: focus()
- 36. Screenreaders update their Virtual Buffer “regularly”
- 37. while in Forms Mode they update in realtime
- 38. use the Forms Mode to update the Buffer when you need to
- 40. another layer: different CSS if Javascript is available
- 41. Change the interface for the JS version
- 42. CSS is much faster than Javascript
- 43. Tell CSS that there’s JS: document.documentElement.className += ” js”;
- 44. .module{ /* nice CSS for the non JS Layout */ } .js .module{ /* awesome CSS for the JS Layout*/ }
- 45. How does your CSS react when the text size changes?
- 46. Screen Magnifier only show a very small part of the screen
- 47. make sure everybody knows what happens right now
- 48. yellow fades + focus() help to find and understand
- 49. the last Layer the new Hotness
- 51. WAI-ARIA maps existing and well known OS concepts to custom Elements in the Browser
- 52. Adds semantics to non semantic Markup
- 53. provides instant updates and notifications
- 54. Roles
- 55. • alert • banner • button • menuitem • slider
- 56. Document Landmark Roles
- 57. • application • banner • complementary • contentinfo • main • navigation • search
- 59. • aria-valuemin • aria-valuemax • aria-valuenow • aria-valuetext • aria-labelledby
- 60. Live Regions informing about changes
- 61. • off • polite • assertive • (rude)
- 62. You can use it today
- 63. • it does no validate • you can simply add the properties using Javascript as it depends on it anyway
- 64. • everybody can add Landmark roles now • aria-required=”true” makes a dream come true
- 65. Don’t rely on it
- 66. • There are no stats but we know that still a lot of Screenreader users are stuck on old versions without ARIA support • Progressive Enhancement all over again...
- 68. Examples
- 76. more • http://cli.gs/wai-aria • http://cli.gs/accessible-tabs • http://cli.gs/accessibilitytips • http://cli.gs/wai-aria-video
Notas del editor
- over 90 different roles to map existing OS concepts onto your Markup
- article Content that makes sense in its own right, such as a complete blog post, a comment on a blog, a post in a forum, and so on. banner Site-orientated content, such as the title of the page and the logo. complementary Supporting content for the main content, but meaningful in its own right when separated from the main content. For example, the weather listed on a portal. contentinfo Child content, such as footnotes, copyrights, links to privacy statement, links to preferences, and so on. main Content that is directly related to or expands on the central content of the document. navigation Content that contains the links to navigate this document and/or related documents. search This section contains a search form to search the site.
- aria-valuemin Stores the lowest value a range may have. aria-valuemax Stores the highest value a range may have. aria-valuenow Stores the current value in a range. aria-valuetext Stores readable text to help the user understand the context. For example, \"30 dollars\" . aria-labelledby Stores the id attribute of a text label containing an appropriate prompt for this widget.
- off This is the default value, and indicates that the region is not live. <ul aria-live=\"off\"> polite This is normal operation and the expected behaviour for live regions. A value of polite indicates that it is not necessary to respond until user completes their current activity. <ul aria-live=\"polite\"> assertive This value is a higher priority than normal but does not necessarily interrupt the user immediately. <ul aria-live=\"assertive\">
- off This is the default value, and indicates that the region is not live. <ul aria-live=\"off\"> polite This is normal operation and the expected behaviour for live regions. A value of polite indicates that it is not necessary to respond until user completes their current activity. <ul aria-live=\"polite\"> assertive This value is a higher priority than normal but does not necessarily interrupt the user immediately. <ul aria-live=\"assertive\">
- off This is the default value, and indicates that the region is not live. <ul aria-live=\"off\"> polite This is normal operation and the expected behaviour for live regions. A value of polite indicates that it is not necessary to respond until user completes their current activity. <ul aria-live=\"polite\"> assertive This value is a higher priority than normal but does not necessarily interrupt the user immediately. <ul aria-live=\"assertive\">