Accessibility Minutes 2009 04 29
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)
- David Todd (IBM)
- Sueann Nichols (IBM)
Minutes
Event Handlers
Rich: starting call with event handlers discussion
Rich: checked with becky; keyboard handlers are put on Dojo containers not child elements; mouse handlers on the children however
Rich: tree, tablist, menubar, menu, button, checkbox, listbox, list, etc. - do not test for keyboard handlers
Jon: However, need onfocus and onblur handlers on children.
Jon: Ask Becky what they do for Dojo regarding handlers on child elements.
Rich: Dont't events bubble up to the container?
Rich: Becky says any element with keyboard support has a handler on the container.
Jon: Managing styling from the parent container is sometimes difficult.
Jon: Opera and Safari have built in visible focus. However FF and IE doesn't. Managing focus on children is sometimes difficult from parent container.
Rich/Jon: A manual check for keyboard focus should be done when elements have keyboard handlers like onmousedown, onmouseup, onfocus, onblur.
Rich: Elements like buttons are not containers but a keyboard handler is necessary.
Jon: If checking keyboard support, check for focus also.
Jon: What's the trigger for checking for role?
Rich/jon: Trigger would be: Element must have a role if not a form or anchor and element has an event handler.
Incorrect Role Values
Jon: incorrect role values should be flagged (e.g.,menuitem not in a menu, treeitem not in a tree, etc.)
Rich: A container role (e.g., tree, grid, menu, etc.) must have at lease one child with an clickable role as defined by aria. Otherwise generate a violation.
Coding Patterns
Rich: Moving on to Coding Patterns
Jon Can we assume that for example if one item in a tree has a treeitem role, all child items without a specified role are treeitems. Or, do we want to warn people when child element roles are missing.
Rich: We should stick to best practices. Yes we should flag a violation.
David: Maybe we should flag a potential violation for this instead of violation.
Preety: Question about tree and treeitem example (i.e., if missing treeitem roles on child elements should missing roles be assumed treeitems?).
Rich: yes
Tabindex
Rich: Moving on to -> Elements of role values must have tabindex defined with the correct value.
Rich Unless the container has an activedecendent.
Jon: Does tabindex need to be set to -1 for child elements using activedescendent?
Rich: Not necessarily.
Other Rules
Rich: Moving on to Other Rules
Jon: Why is frame title used? Is it needed?
Rich: If looking to be WCAG 2.0 compliant applications need title.
David Agree, need title to be WCAG 2.0 compliant.
Jon: Okay let's rephrase. If frame doesn't have a landmark, a title is needed.
Rich: Rewording frame title rule.
Jon: If a frame is marked presentational it doesn't need a title.
Team: no
Different chair for next two weeks
Rich: traveling next 2 weeks
Jon: chair next 2 weeks
Action Items
none