Accessibility Minutes 2009 12 09
From MemberWiki
Participants
- Michael Squillace (IBM - chair)
- Ann Abbott (IBM)
- David Todd (IBM)
- Rich Schwerdtfeger (IBM - co-chair)
- Vio Onut (IBM)
- Shawn Lauriat (IBM)
- Nathan Jukubiak (Parasoft)
- Jon Gunderson (University of Illinois)
- Sandy Foltz (University of Illinois)
Minutes
Mike: Dedicate one of these calls after first of year to coordinate CSUN presentations.
Mike: will contact CSUN to see if we can affect scheduling of both presentations
Sandy: OAA wiki page for Accessibility Reporting Best Practices [1]
Mike: first agenda item = Reporting Best Practices
Mike: presentation of results, what we think ought to be presented (content), when to present
Rich: every vendor will have specific style, but should have suggested techniques for presenting
Rich: how to respresent structural problem with widget
Rich: those are for developer tools
Rich: for FVT, how to provide report for later processing
Rich: ability to annotate report (what's being tested) and push results to data store
Rich: xpath statement plus guidance to author - may not need to imiplement but guidance would be good
Rich: Web crawler - only does sniff -test, still needs FVT or manual test to complete
Rich: Reporting Best Practices should not be proscriptive but include bare minimum to support rule sets
Jon: important to have consistency of messages for coding practice or how to fix
Jon: should be part of rule structure and messaging should include part of rule.
Jon: is there mechanism to point to more resources?
Mike: get path back with message and URL for more info
Mike: coiuld be different between WCAG 2.0 and Section 508
Jon: hoped way to fix either would be consistent/same = technique message
David Todd: generate two different reports: WCAG & 508
Vio: RPT does this
Vio: differences between WCAG 1.0 and 2.0 so rule set needs to be flexible enough to accommodate
Mike: need to also implement differences with WCAG 2.0 and ARIA vs. WCAG 1.0
Mike: volunteers to write Reporting?
Mike: taking Developer tool oriented Reporting Best Practices
Rich: taking FVT oriented Reporting Best Practices
Jon: taking crawling oriented Reporting Best Practices
Mike: Rich mentioned rules to record mapping table?
Rich: this is format of record
Rich: rename to Error Record format
Rich: have other vendors submitted rules?
Nathan: yes - have plans to help, but got slammed past weeks - will help
Mike: next agenda item: Rule requirements
Mike: xpath conversion utility available plus xpath library for IE
Mike: event triggers
Mike: divided up table and assigned
Mike: add extra column for events most appropriate to trigger rule
Nathan: have we enumerated all events?
Mike: listed at bottom of wiki page
Mike: other issue is how to specify those triggers?
Mike: list event type and target
Rich: can make for any widget type, correct?
Mike: correct
Rich: should be looking for divs/spans that gets focus with no semantics should generate error
Rich: have to do structural analysis like done staticly
Mike: rule logic should take care of structure
Mike: send suggestions, if any, to list
David Todd: link to events already listed?
Mike: on wiki on requirements page
Mike: OAA wiki page for Accessibility Valication Rule Codification Requirements [2]
Mike: others should add events as necessary
Sandy: Note: eventTypes are: DOMFocusIn, DOMMutation, DOMNodeInserted, DOMNodeDeleted, User
Nathan: what login to use to modify wiki?
Mike: same as originally recv'd
Mike: one more meeting this year, next week and resume 1/06/2010
Rich: separate call for CSUN coordination?
Jon: rather do on this call
Vio and Nathan: agree
Call ended 9:39
