HTML5 Accessibility | CSUN 2011


Published on

What is HTML5 and how does it affect accessibility? This presentation was given at the 26th Annual International Technology & Persons with Disabilities Conference (CSUN 2011)

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Logo is the new HTML5 icon with braille:\n
  • \n
  • \n
  • Original internet pages were text based and accessible.\nImages were introduced and pages were still easy to read.\nYahoo! circa 197\n
  • “Geocities 1996” a tribute to Geocities web designs on CSS Zen Garden\nanimated gifs, clashing colors, flashing images, and more\n“Creating Killer Web Sites” released in 1997 by David Siegel introduces the spacer gif, table-based layout, and so much more\n
  • Jeffrey Zeldman and friends introduce web standards\nReturn to semantic, structural markup.\ndesign and interactions are separated from markup.\n
  • Web 2.0 introduced application-like web sites. \nAJAX for dynamic content changes, drag and drop interfaces, semantic elements transform into forms\nelements no longer behave naturally.\n
  • \n
  • \n
  • HTML5 is the result of recognizing web sites were moving from documents to web applications.\nInitial spec written by WHATWG\nCombine best of XHTML with HTML\nEnthusiasts began lumping the various elements under the HTML5 moniker\n
  • The spec is still accepting feedback.\nBrowser implementation is increasing.\nOlder IE browsers need JS shim for CSS support of new elements\nBackwards compatibility actually makes HTML5 easier to use than HTML4 + XHTML\n
  • XForms became HTML5 forms\nCSS3 has been under development for years, browsers are rapidly adopting it.\nCanvas and SVG are not new, browser support is allowing them to replace flash\nAudio and Video specs are still devloping. \nJavaScript enhanced with web workers, sockets, local storage, browser api\n
  • browsers handle interactions natively, no need for JS\nimproved form structure\nnew tags\n\n
  • consistent interactions across the web as browsers replace adhoc js and plugins\nbrowsers provide hooks for extending experience via CSS and JS\n
  • New input types: email, url, date, number...\n New attributes: placeholder, autofocus, required...\n Combine with ARIA: aria-require...\n Backwards compatible\n\n
  • the generic div and span tags have been abused. HTML5 introduces new semantic containers to avoid a page filled with nothing but divs.\n
  • ARIA and new elements can be combined for fallback. Avoid wrapping element in a div with the same role, <div role=”navigation”><nav>\n\ntime also uses datetime and optional pubdate attributes for expanding publish date in machine readable timestamp.\n
  • <script>document.createElement("header")</script>\n\nIAccessible2 is an engineered accessibility interface allowing application developers to leverage their investment in MSAA while also providing an Assistive Technology (AT) access to rich document applications such as the IBM Workplace productivity editors and web browsers such as Firefox. The additional functionality includes support for rich text, tables, spreadsheets, Web 2.0 applications, and other large mainstream applications.\n
  • the data-foo pattern avoids placing related information in hidden divs, rel/rev/title attributes.\n - similar to microformats, uses itemtype, itemprop, itemscope\nadd pubdate to the time tag to show this was a published event <time datetime=”” pubdate>\nNative drag and drop, integrate with aria\n
  • W3C Web Accessibility Initiative: Accessible Rich Internet Applications\nTodd’s lecture: Yahoo! Mail: An Accessible Hub for Your Connected Life Wednesday March 16 10:40 - 11:40\n\n
  • role=”banner” | role=”search” | role=”main” | role=”complementary”\n\n
  • Use role=”button” on links that trigger an action, not take the user to a new page\naria-label for adding a label to an input that has no label.\naria-describedby is similar to longdesc. points to a section of content with id\nrole=”presentation” on layout table tells the screen reader its not for data.\n
  • \n
  • - SVG accessibility\n
  • Wednesday, March 16, 1:50 PMVideo Accessibility in User Agents - Panel\n Thursday, March 17, 10:40 AM HTML 5 Accessibility - Panel\nphoto of John Foliot by Dirk Ginader\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Web workers: multi threading\nWeb sockets: comet, push data\nLocal storage: cookies on steroids\nOffline support: gmail without internet\nGeolocation: and other access to computer resources\n
  • \n
  • \n
  • \n
  • HTML5 Accessibility | CSUN 2011

    1. 1. HTML5 Accessibility Ted Drake Yahoo! Accessibility Lab
    2. 2. Big Questions 1.What is HTML5? 2.Does it help or hurt?Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    3. 3. In the good ol’ days...Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    4. 4. We had textYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    5. 5. Then came designYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    6. 6. Salvation ArrivedYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    7. 7. “Design” returnedSome rights reserved by DanCentury on Flickr
    8. 8. Take a deep breathYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    9. 9. What is HTML5?Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    10. 10. a reality checkYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    11. 11. HTML5 is not...• Finished• Difficult• Fully Supported Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    12. 12. HTML5 includes• More powerful forms • JavaScript tools• CSS3 • Device Integration• Canvas and SVG • Semantic structure• Audio and Video • WAI-ARIA Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    13. 13. Good Stuff• Native Interactions• Enhanced Form Elements• Better Semantic Structure• ARIA Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    14. 14. Native Support• Browsers replace plugins and JavaScript• Consistency• Extensible Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    15. 15. Super FormsYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    16. 16. Super FormsYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    17. 17. No More ‘Divitis’Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    18. 18. Semantic Tags• New containers: article, section, aside, footer, header, nav• New & improved tags: dl, time, hgroup, mark• Shift from document to modular design: multiple h1, header, footer tags Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    19. 19. New Attributes• Custom data attribute: data-ticker=”yhoo”• Timestamps: datetime=”2011-03-16”• Drag & Drop: • draggable=”true” • dropEffect=”move” • dropEffect=”copy” Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    20. 20. ARIA• Web application functionality• Landmark structure: navigation, banner, search, main• Meta information: aria-required, aria-label• Live regions for dynamic content Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    21. 21. ARIA LandmarksYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    22. 22. ARIA Quick Fixes• <a href=”#” role=”button”>• <input aria-label=”enter search term” ...>• <img aria-describedby=”stockinfo” ...>• <table role=”presentation> Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    23. 23. New ConcernsYahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    24. 24. Canvas• Blank canvas for JavaScript to draw upon• Problems: • Text within canvas is not accessible • Images within canvas have no alt text • User interactions lack roles, states, and properties Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    25. 25. Closed Captioning• Flash wasn’t great, but at least it supported closed captioned videos• Multiple caption formats• See John Foliot for details Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    26. 26. longdesc• HTML5 spec deprecates the longdesc attribute• This is not final• HTML5 is backwards compatible. It should still work. Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    27. 27. ARIA Longdesc Replace longdesc with aria-describedby<img src="foo.jpg" ... aria-describedby="dHustler"><a href="hustler.html" id="dHustler"> Image Description</a> Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    28. 28. Headers• Module hierarchy, not headers.• Each section and article can have an h1• Pages may have no h2,h3,h4... Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    29. 29. Autoplay & Autofocus• Built in support for auto behaviors • Video autoplay • Form input autofucus• Native support avoids adhoc JavaScript Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    30. 30. What you can do• Participate in HTML5 specifications• Begin using HTML5 Form elements• Combine ARIA with HTML5 tags• Start using HTML5 and test, test, test Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    31. 31. More Talks• Wednesday, March 16, 10:40 AM WEB-2033 Accessible HTML5 Media Players, Captions, Audio Description, and Search• Wednesday, March 16, 10:40 AM Building Fully Accessible Social Software and Rich Web Applications with WAI-ARIA• Wednesday, March 16, 1:50 PM Video Accessibility in User Agents - Panel• Thursday, March 17, 10:40 AM HTML 5 Accessibility - Panel• Thursday, March 17, 1:50 PM WEB-3065 HTML5 – What’s new for Accessibility • Friday, March 18, 1:50 PM WEB-2063 Web Media Accessibility with HTML5• Friday, March 18, 1:50 PM HTML 5 and Flash – An Accessibility Comparison Yahoo! Accessibility Lab Accessibility.Yahoo.Com | @yahooaccess |
    32. 32. Ted DrakeYahoo! Accessibility Lab Accessibility.Yahoo.Com