Accessibility Minutes 2010 06 02

From MemberWiki

Jump to: navigation, search

Present

  • Rich Schwerdtfeger (IBM)
  • Ann Abbott (IBM)
  • David Todd (IBM)
  • Jon Gunderson (University of Illinois)
  • Nathan Jukubiak (Parasoft)
  • Shawn Lauriat (IBM)

Minutes

Rich: let's talk about press release

Rich: talking about changes that were made to pr

http://openajax.org/pipermail/accessibility/2010-May/000289.html

http://openajax.org/pipermail/accessibility/2010-June/000290.html

Rich: First draft -- IBM had too many quotes, other members added quotes to make it a community announcement vs. an IBM announcement

Rich: Preddy quote was added

Rich: Any comments on press release?

Ann: Regarding comment from Jon -- double quote problem, Rich fixed it.

Press release looks good to everyone

http://www.openajax.org/member/wiki/Accessibility_Validation_Rule_Codification_Requirements

Rich: Accessibility codification requirements. Are people happy with the format, etc?

Jon: What's the performance hit with exceptions vs. an error code?

Rich: Not sure.

Nathan: never noticed performance hits. Let's try it and see about performance.

Jon: Browser specific code will through the most exceptions.

Rich: Let's go with accessibility codification requirements for now.

Rich: Do we want to call our group a "working group" ?

Jon: More credibility if we publish the rule set as an approved rule set under the OAA.

Nathan: what's the difference?

Rich: working groups produce something

Rich: task forces don't actually have to produce documents.

Rich: We will produce a document so best name for us is working group.

Rich: our documentation is in Wiki format. Probably will have to produce that content in an HTML document.

Rich: Call our group the "Accessibility Working Group"

Rich: Talk to John F. about style guides for OAA documents.

Rich: How will we track bugs for rules?

syntactically correct, performance, clarity

and documentation, submitted test case, WCAG2 compliance v. best practice,

browser neutrality, etc.

Suggestion: bugzilla, with review of registered defects/changes before

commital?

Group: We will use Sourceforge for code repository.

Rich: Do we want to setup a process for contributing code.

Jon: Will draft a process for addressing code issues in Sourceforge .

Rich: Break up ARIA state/property/structural validation by role (performance issue)

Jon: Break up by category (e.g., multimedia, etc.).

Jon: Example, tree should have treeitems. Else a warning or error should be generated.

Rich: Break up by patterns commonly used by developers.

Jon: This will help developers to see what the options are.

Rich: How do Rich and Jon coordinate work?

Jon: Is updating his ARIA examples and Rich was going to work on ARIA as well.

Rich: We want to try to prototype rules.

Jon & Rich will talk off-line about coordinating their work.

Rich: Working on new draft of ARIA

Rich: Must do an overall rule review to evaluate performance

Jon: performance is something that must addressed at some point but rule development should be first priory

Nathan: Once rules are running, Parasoft will test performance. But we don't need to focus on it at the moment.

Rich: Should not address performance at this point.

Rich: discuss browser neutrality

Nathan: Parasoft is looking at browser neutrality.

Nathan: need to build code that does browser sniffing. (Working item for Nathan)

Shawn: we're doing feature sniffing not browser sniffing. (Working item for Nathan)

Retrieved from "http://www.openajax.org/member/wiki/Accessibility_Minutes_2010_06_02"
Personal tools