Enabling an Accessible Web 2.0

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    6 Favorites

    Enabling an Accessible Web 2.0 - Presentation Transcript

    1. Enabling an Accessible Web 2.0 Becky Gibson Web Accessibility Architect
      • Web 2.0 Overview
      • Web 2.0 Accessibility Concerns
      • Addressing Web 2.0 Accessibility
        • Technologies
        • Tooling
        • Testing
      • Demo
      • Summary
      Agenda
    2. What is Web 2.0?
      • Dynamic
        • Incremental updates, multimedia
      • Interactive
        • Maps, web services
      • Collaborative
        • Wikis, blogs
        • Crowdsourcing – http:// www.istockphoto.com
        • Collective intelligence
          • Amazon Mechanical Turk - http:// www.mturk.com/mturk/welcome
          • Digg - http:// www.digg.com /news
          • del.icio.us - http:// del.icio.us /
      “ Thus, mastery of architectures of participation to create real value will be essential to success in the Web of the future.” Dion Hinchcliffe
    3. Google Maps
    4. iStockPhoto
    5. Web 2.0 Technologies
      • JavaScript
      • CSS – Cascading Style Sheets
      • Ajax – Asynchronous JavaScript and XML
      • Multimedia
    6. Yahoo! – February 29, 2000
    7. Yahoo! – May 2, 2007
    8. AOL – February 29, 2000
    9. AOL – May 2, 2007
    10. Web 2.0 Accessibility Concerns
      • Rich Interface controls
        • Reliance on Mouse
        • Lack of Semantics
      • Incremental Updates via Ajax
        • Unexpected / Unaware
        • Unable to locate
      • Changes in focus
      • Excessive Navigation
      • Multimedia
        • Lack of captioning
        • Interaction issues
    11. Addressing Web 2.0 Accessibility
      • Updated Web Technologies
        • Accessible Rich Internet Applications (ARIA)
        • IAccessible2
      • Development Tools
        • Integrated Development Environments
        • Toolkits
      • Testing Tools
        • Rule-based Accessibility Validation Environment (RAVEN)
        • Functional Web Accessibility Evaluator (FAE)
      • Assistive Technologies
    12. Updated Web Technologies - ARIA
      • Allows creation of rich user interface components
      • Full keyboard navigation
      • Non-intrusive notification of updated content
    13. Need for ARIA
      • Navigation
        • All components must be keyboard Accessible
        • Remove reliance on tab key navigation
      • Notification of updated content
      • Assistive Technology (AT) Support
        • AT work via platform accessibility APIs
          • Only basic HTML elements are supported
          • Scripted Web content is not supported
        • Assistive Technology needs to:
          • Know active roles of scripted user interface components
          • Monitor states of scripted user interface components
    14. ARIA Overview
      • Add role semantics to scripted user interface (UI) elements
      • Update state information dynamically
      • Make items focusable via tabindex attribute
      • Add keyboard event handling
        • Mimic the keyboard behavior of the rich client UI
        • Minimize tab key navigation
      • Add live region information and notification behavior*
      • Extensible via RDF in future
      *Live region support coming in Firefox 3
    15. ARIA Support
      • Support for HTML and XHTML
      • Implemented in Firefox 1.5 and later versions
      • Supported by Window-Eyes and Jaws
        • Window-Eyes 5.5 or later
        • Partial support in JAWS 7.1, more in JAWS 8.0
    16. ARIA Demo Available at http://www.weba11y.com/AjaxDemo/sample.html
    17. Updated Web Technologies – Accessibility APIs
      • Each platform has Accessibility API to communicate with AT
        • Accessibility ToolKit (ATK) for GNOME
        • Java Accessibility API
        • Microsoft Active Accessibility (MSAA) for Windows
        • UI Automation for Vista
      • MSAA created many years ago
        • No access to advanced functionality
        • ATs rely on off-screen models and private application APIs
    18. Updated Web Technologies – IAccessible2
      • Extends MSAA to add missing functionality
        • rich text, tables, relations
        • ARIA Live Regions
      • Harmonizes with newer APIs of Java and Linux
      • Interface donated to The Linux Foundation as Open Standard
      • Will be implemented in Firefox 3
      • Being integrated into Eclipse
    19. Development Tools
      • Web Toolkits
        • Dojo
        • Scriptaculous
        • Prototype
        • Google Web Toolkit (GWT)
        • Yahoo! User Interface (YUI)
        • More…..
      • Integrated Development Environments
        • Rational Web Developer
        • Ajax Toolkit Framework
        • More…..
    20. Dojo
      • Open Source JavaScript Toolkit
        • “Easy” Ajax
        • Data Binding
        • Full event system
        • Browser abstraction layer
        • User Interface Widgets
        • Dual Licensed
          • Academic Free License v2.1
          • BSD License
    21. Dojo 1.0 Core Widgets (Dijit)
      • Fully Accessible via ARIA Techniques
      • Internationalized
      • Standard Look and Feel
      • Developer Documentation
        • API
        • User Manual
      • Supported Browsers
        • Firefox 2.0
        • IE 6+
        • Safari (latest)
      • Data Binding
        • Tree, Grid, Select
    22. Dojo Demo
    23. Accessibility Testing Tools
      • Test against published standards
      • Many tools evaluate the “over the wire” HTML
        • Bobby from Watchfire
        • WebKing from Parasoft
        • More …
      • Difficult to evaluate server side technologies
      • Issues with dynamic Web 2.0 content
      • Need more interactive solutions
    24. RAVEN Rule-based Accessibility Validation ENvironment
      • Set of Eclipse plug-ins
      • Originally developed for validating Java GUIs
        • Java AWT and Swing
        • Eclipse SWT
      • Integrates accessibility testing into development environment
      • Operates via an XML based set of rules
      • Supports Validation of Dynamic HTML
        • Uses IAccessible2
      • Being updated to support ARIA
    25. Summary
      • Web 2.0 is dynamic and constantly evolving
      • Accessibility of Web 2.0 is possible through
        • Updated Technologies
        • Toolkits and Development Environments
        • Testing Tools

    + bgibsonbgibson, 3 years ago

    custom

    2802 views, 6 favs, 0 embeds more stats

    Presentation from the International Cross-Disciplin more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 2802
      • 2802 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 6
    • Downloads 130
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories