Accessibility Minutes 2012 01 23
From MemberWiki
Contents |
Present
- Jon Gunderson (University of Illinois - Co-Chair)
- Rich Schwerdtfeger (IBM - Co-Chair)
- Ann Abbott (IBM)
- Marc Johlic (IBM) - Scribe
- Nicholas Hoyt (University of Illinois)
- Prasanna Bale (University of Illinois)
Agenda
Link to agenda: http://openajax.org/pipermail/accessibility/2012-January/000659.html
Minutes
Nick will setup a weekly meeting on Doodle and send out a link for voting.
Agenda 1: 1. Using JSDoc 3 to document javascript code
/a11y/api_docs/version2/OpenAjax.a11y.html
Jon: Does this URL look OK?
Rich: Do they have a general API docs dir?
Jon: JF didn't say
Rich: Looks fine
Jon: Process is generate documentation, put in zip file, send to Jon Ferraiolo and he will put it here
Ann: Is this documentation likely only to make sense to a developer?
Jon: At this level yes. We'll probably want to have 2 versions of docs. One for public that a developer would want to use (so that methods etc don't clutter). The more consumer friendly version would be easier to read.
Jon: Does not preclude us from having usage info in wiki
Jon: If someone is building a tool, they can look and see what the properties are etc
Nick: From a dev standpoint, there are some terminology issues from jsdoc (ie js doesn't really have "classes"). We need to learn how to modify the template that produces this.
Rich: Was this designed for js?
Nick: It was, but but there are still some issues and clarifications to make
Nick: These are more functions that have members - so the better name would be that these are constructers for js objects
Jon: We can look to modify the template - and then even submit back as a bug fix.
Agenda 2: Update on OAA Cache and Ruleset Development
Jon: Been working on refactor of NLS objects and writing results
Jon: We need to have a WCAG centric view of the world in the ruleset because that's where it seems the world it going
Jon: With WCAG having different levels, it didn't fit in with the original simplified requirements
Jon: New system will be much more straightforward than old. We'll still be able to add custom rulesets
Jon: Last bits of v1 code are being changed
Jon: We'll have constructors for these objects - this will allow us to have documentation for objects created
Agenda 3: Continue rules discussion for following requirements: WCAG 2.4.6
/member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.6_Headings_and_Labels
Jon: We left off at the Controls Rules
/member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Control_Rules
Control_10
Nick: Possible clarification - term "accessible labels" maybe change to "Effective labels"
If we use "effective" we have to be sure to define it
/member/wiki/WCAG_2.0_Principle_3_Understandable_Rules#Requirement_3.3.2_Labels_or_Instructions
http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-cues
WCAG G131 uses "descriptive" - Providing descriptive labels
Jon: We'll come back and look at Control_1 for next week. Jon will put some notes in that we can review.
Call ended at 1pm Central --marcjohlic 23:28, 23 January 2012 (UTC)