Accessibility Minutes 2009 04 22
From MemberWiki
Contents |
Participants
- Ann Abbott (IBM)
- Jon Gunderson (University of Illinois)
- Nathan Jakubiak (ParaSoft)
- Preety Kumar (Deque)
- Vio Onut (IBM)
- Tony Salcedo (ParaSoft)
- Rich Schwerdtfeger (IBM - chair)
- Mike Squillace (IBM)
- Derk Stegemann (FIT)
- David Todd (IBM)
Minutes
Event rules review
Team: Accepts elements with onMouseOver and onMouseOut event handlers must either: move hover effects to CSS or include onFocus and onBlur event handlers
Rich: Team ok with: Elements that include a ROLE attribute must include a keyboard event handler (onKeyDown, onKeyUp or onKeyPress) in the container element for the widget: example the element with ROLE="TREE" in a tree widget?
Jon: Updating Wiki for following rule: Team: Elements that include onMouseXXX event handlers must include a ROLE and a TABINDEX value if
David: the element is not a link or form control (what about active descendant???). Rich: Can use activedescendant or tabindex to put focus on the active child element in a widget. Jon: When activedescendant is used, focus is placed on widget. When tabindex is used, focus is placed on child element in widget. Jon: If not using activedescendant all child elements should have a tabindex value.
Rich: Widget container must have a tabindex=0.
Jon: Widget using activedescendant does not need tab index=0 because events on child elements will bubble up.
Jon: updated rule on Wiki
Rich: Question about grid mouse handler?
Jon: In general the grid will have mouse handler.
Jon: Need onfocus and onblur event handlers to update styling on grids.
Action: Rich Ask Becky how Dojo handles event handlers.
Rich: tabindex rules may be different for menus.
Rich: Managing focus is based on the type of widget.
Action: Jon go through different aria containers and determine appropriate use of tab index.
Jon: Discussing rule "Rules when event handlers cannot be programmatically determined (but may be visible in markup) "
David: related to links: All elements with onMouseOver and onMouseOut events defined in HTML markup must either: move hover effects to CSS or include onFocus and onBlur events
Jon: This should be a violation: "A elements with onMouseOver and onMouseOut events defined in HTML markup must either: move hover effects to CSS or include onFocus and onBlur events "
RESOLUTION: Team agrees should be a violation: "A elements with onMouseOver and onMouseOut events defined in HTML markup must either: move hover effects to CSS or include onFocus and onBlur events "
Jon: IE ignores focus outlines.
Preety: cannot not edit Wiki.
Rich: sending note to get Preety access.
Preety: XULRunner enumerates event handlers.
David: Stopping rule discussion with the following rule, Jon edited it: "A elements with onMouseOver and onMouseOut events defined in HTML markup must either: move hover effects to CSS or include onFocus and onBlur events "
Rules Engine Progress
Mike: Due to shortcomings of the Java plug-in we are focusing on a Mozilla specific implementation for now. We had hoped to be browser agnostic.
Summary of Action Items
Rich: Ask Becky how Dojo handles event handlers.
Jon: go through different aria containers and determine appropriate use of tab index.