Accessibility Minutes 2011 06 13

From MemberWiki

Jump to: navigation, search


  • Jon Gunderson (University of Illinois - Co-Chair)
  • Prasanna Bale (University of Illinois)
  • Nick (University of Illinois)
  • Rich Schwerdtfeger (IBM - Co-Chair)
  • Marc Johlic (IBM)
  • Ann Abbott (IBM)
  • David Todd (IBM) - minutes


Jon would like to create version 2.0 of rule set.

Good to get feedback on use cases for version 2.0.

How do we organize repository?


Above link goes to some of the use cases for 2.0.

Discussing "Generate an accessibility report for a document" in above link.

XPath may be one way to id nodes that fail.

Inspect a particular node - which rules passed or failed on the node.

"Presentation" elements - rule doesn't process these roles.

Link text must be unique.

Context will become more XPath like. But event handler rules could problematic using XPath.

In 2.0 a much higher level API will be developed.

Return rule results in a standardized format.

When a node is accessed and it's not in the cache, refresh the cache.

My have to have periodic update of the cache.

Reports (Nick): filter on severity of rules and have summary.

Would have 2 filters. A rules filter and a filter for reports.

Marc tried the cache inspector but couldn't get it working. Jon will update with new version.

We want to create a new 2.0 repository for OAA 2.0 rules.

Archive version 1.0 of the rules.

Marc commenting on WCAG WG view of link guidance.

Marc says they are discussing.

Key about link guidance is programmatically identified context.

Personal tools