1 / 14

Yahoo! / TPG Case Study

Yahoo! / TPG Case Study. Applying WAI-ARIA to Yahoo! Mail. Introductions: Yahoo & TPG. Yahoo Global Internet services company providing vast range of products, including a Web 2.0 email client TPG Provides accessibility related consultancy, development and auditing.

ponce
Télécharger la présentation

Yahoo! / TPG Case Study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Yahoo! / TPG Case Study Applying WAI-ARIA to Yahoo! Mail

  2. Introductions: Yahoo & TPG • Yahoo • Global Internet services company providing vast range of products, including a Web 2.0 email client • TPG • Provides accessibility related consultancy, development and auditing

  3. Introductions: Yahoo Mail • Yahoo Mail • Provides a rich, desktop like experience • Highly dependent on clientside scripting • Interface based on customized controls and interaction model • Advanced, integrated features, such as • Instant messaging • Text messaging • RSS feeds

  4. Introductions: ARIA • Solves a major accessibility problem with webapps: Role and state information • Role: what is the type of this widget? Examples: • Slider • Tree • Tab • menubar • State: What are it’s current features, what properties does it have? Examples: • Expanded • Selected • disabled • readonly • This information is Exposed to AT (e.g. Screen readers) • AT can correctly convey the control to the user, as if it was a desktop based control

  5. Introductions: the Project • Yahoo Mail is an ideal candidate for ARIA • Highly dynamic • Highly Customized • TPG contractor was brought in as an experimental project • Assess accessibility requirements • Make necessary changes for ARIA to work • Apply ARIA roles and states • Three months were spent at Yahoo Sunnyvale • Results: It’s a start, but not there yet.

  6. Challenges: Codebase • Up to 7 years old • Not standards compliant • Not geared towards accessibility in any way • Not build from the ground up, but constantly evolving • Mainly targeted at performance and X- browser compatibility • Why not fundamental accessibility first? • Yahoo mail classic • Would have to be redone from the ground up. With ARIA it wouldn’t.

  7. Challenges: Focus • Focus in Yahoo Mail is mostly simulated • Visually something appears to have focus • Programmaticaly, neither the browser, OS or AT are aware • For ARIA to work, proper focus must be applied: • Solution: Setting tabindex value: • tabindex=“0”: element becomes part of the tab order • Tabindex=“-1”: element just becomes focusable (through scripting or clicking)

  8. Focus (ctd.) • Focus loss often occurs due to • Rerendering of interface components • Destruction and recreation of currently focused control. • Loading of external (out of our control) content. • Tracking focus globally, forcing it back if needed.

  9. Challenges: Focus order • Tab key used in different ways • Pane to pane navigation • Control to control navigation • Default (element to element) tab navigation is suppressed. • Tab key currently loops main segments and toolbars • Toolbars considered too many stops by some, possibly moving to shortcuts. • Discoverability vs. Efficiency? • Arrow keys are used for subpart navigation • Rich text editor tab trap

  10. Challenges: Keyboard Shortcuts • Yahoo Mail overrides some browser –native shortcuts, e.g. • Closing tabs • Searching in messages • Set of shortcuts is provided for fast keyboard interaction. • Paradigm conflict: • webpage pretends to be a desktop application, but is in fact running inside another desktop application

  11. Challenges: Applying ARIA • Namespacing difficulties (no longer an issue since FF3) • Content handled as partial HTML text strings, difficult to determine where it becomes action DOM content • Controls are drawn multiple times • Roles and states are destroyed everytime, will have to be reapplied • Library was created similar to enable.js • Class based approach vs direct assignment • Apply to single or root container element: performance risk

  12. Challenges: Message Table • Both column and row navigation • Table header announcement problematic • JAWS: no announcement at all in PC cursor mode • WE: Correct heading announcement, breaks at focusable rows • Checkbox type cells • Selection announcement (alert role)

  13. Challenges: Screen Readers • Targeted at JAWS 9.0 beta & WindowEyes 6.1 • Designed for non-virtual mode (browse mode off) • Difficult to get a clear idea of compatibility • Ertratic behavior • Few ‘real world examples’ • Biggest issues: • Role = document vs role = application • Cell navigation • Cheats sometimes chosen: • Describedby

  14. Components • YUI components are sometimes used in Yahoo Mail, e.g. In Menu component • Currently ARIA is manually applied • Next upgrade will include built in ARIA for YUI

More Related