Accessibility Minutes 2009 08 26

From MemberWiki

Revision as of 15:08, 26 August 2009 by Schwer (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Participants

  • Anne Abbott (IBM)
  • Jon Gunderson (University of Illinois)
  • Nathan Jacobiak (ParaSoft)
  • Michael Squillace (IBM)
  • Rich Schwerdtfeger (IBM - chair)
  • Sandy Foltz (University of Illinois)

Minutes

Sandy: FF 3.7 has added event handling checkers and is adding support for grids

Mike: possible to create generic code store

Nathan: should probably establish name convention/spaces to avoid colliding with content on page.

Sandy: must have name spaces for Firebug

Mike: should use OAA name spaces

Rich: sending note to John F about name spaces

Nathan: needs to be logic for attaching rules and determining when & how they fire - is this group creating that logic or leaving it up to tool developers

Rich: this group probably needs to create that logic

Rich: on focus change events, only analyze changes, not entire DOM

Rich: include accessibility in HTML 5

Mike: will set up separate call with Nathan, Preety, Sandy and Vio

Rich: check with Adam Peller for localization for javascript

Rich: Best Practices for error reporting

Best Practices

Best Practices Page: /member/wiki/Accessibility_Reporting_Best_Practices

Rich: probably different scenarios for different test tools: Dev, Test, Crawler

Rich: need ability to annotate report so can determine where error occurred

Sandy: Firebug includes where in DOM error was found

Rich: can that be converted to a log?

Sandy: want that much detail?

Rich: include info on specific role/attirbutes

Mike: should strive to make generic for branding/look feel/privacy/etc

Jon: added kbd event handlers checking

Jon: anyone using HTML 5?

Rich: browsers implementing various portions of HTML 5

Rich: wait till Dec/Jan to incorporate HTML 5 in our work

Rich: working with Apple to make Canvas accessible

Nathan: can get competitive advantage with reporting

Mike: when discussing reporting - what does a violation look like?

Rich: have rule set, envisioning having specified what data store looks like and what is actually being tested based on event trigger

Sandy: need version of rule as well