Accessibility Minutes 2013 01 07

From MemberWiki

Jump to: navigation, search


  • Ann Abbott (IBM)
  • Jon Gunderson (University of Illinois)
  • Mike Scott (Illinois Department of Human Services)
  • Nicholas Hoyt (University of Illinois)
  • Marc Johlic (IBM)
  • Prasanna Bale (University of Illinois) - Scribe


Jon: /member/wiki/Version_2.0_WCAG_2.0_Summary

Jon: The above link specifies about which success criteria the rules developed. It also has WCAG 2.0 Rule Summary which specifies which rules come under what success criteria

JOn: specifies how the rule is included in different rulesets

Jon: This will be updated as we generated more rules

Jon: does this makes sense?

Group agrees

Nick: Can we link the Rule ID's with the full description of the rule if that is straight forward?

Jon: its probably possible in the near future

Jon: Next agenda item: Event Handler Rules


Jon: Widget Rule 11: Elements with mouse move events must/should have widget roles

Jon: If the event handler is on found on the elements then the rule passes

Jon: If it finds on the parent or any ancestor of the element, the rule triggers a manual check

Jon: when we have mouse based event handlers an interactive widget role has to be associated with it, then it passes

Jon: If the container of an element has an interactive widget role , then it is a manual check and it fails when the element and its child doesnot have an interactive widget role

Nick: Is widget rule primarily about click and drag?

Jon: yes

Nick: It would be good if the rule desc says that

Mike: It should be possible, people would use onMouseMove over onMouseOver

Jon: That might be a performance degrade

Jon: The reason behind making two different rules to avoid confusion and also lot of result messages

Jon: So, ONMOUSEDOWN, ONMOUSEMOVE and/or ONMOUSEUP are related to drag/click


Personal tools