Accessibility Minutes 2012 04 23
From MemberWiki
Contents |
Present
- Jon Gunderson (University of Illinois - Co-Chair)
- Ann Abbott (IBM)
- Marc Johlic (IBM)
- Richard Schwerdtfeger (IBM - Co-Chair)
- Philip Ackermann (Fraunhofer Institute for Applied Information Technology) scribe
Minutes
Conceptual Model
Jon: send sample code for ruleset and rule
Jon: not integrated into the tool yet, maybe until next Monday
Jon: created a branch in source code repository (SVN)
Jon: updated version of Accessibility Inspector, for example highlight elements in the graphical interface
Ann: had problems installing the new version due to Firefox/Firebug version
Jon: updated version of Accessibility Inspector contains new preference settings
Jon: any feedback to me or Prasanna
Marc: Firefox 11.0 and Firebug 1.9.1 seems to work with Accessibility Inspector 0.92
Jon: will check with Prasanna
Jon: updated to a lot more consistent look and feel of the UI (Windows/Mac)
Marc: IBM is now using Firefox ESR versions - currently Firefox ESR 10.0.3 is what has been pushed to IBM
Jon: wcag_primary_id rule evaluation results would be associated with
Jon: optional wcag_related_ids
Jon: to associate with other wcag requirements
Jon: cache_properties to create views on the data
Jon: cache_properties as kind of filter on the data
Jon: language: if empty string --> applies to all languages
Jon: or list of languages
Jon: Rule NLS example: Natural language support
Jon: example manual test for alternative text --> long message for describing the test
Jon: messages now much shorter
Jon: placeholder % == SHOULD or MUST
Jon: same for SUMMARY property
Jon: conceptual change from "what went wrong" to "what needs to be done"
Jon: --> ACTION
Jon: should we process the widget even if it is hidden from assistive technology
Marc: widget is only not visible at the moment or in general?
Jon: at the moment
Marc: then it should be processed / tested
Jon: maybe it is junk code that never gets visible
Rich: should not test hidden content for accessibility
Rich: display = none or HTML5 hidden
Jon: maybe a setting turn on/off processing/testing of hidden widgets
Jon: TARGET property describes the elements for which the rule applies
Jon: PURPOSE property list of strings, provide developers information about accessibility
Jon: TECHNIQUES property provides more details on what to do
Jon: RESOURCES property points to the WCAG techniques
Jon: Ruleset Example
Jon: "rules" property a list of rules
Jon: each rule associated with "name", "type" and status property "enabled"
Jon: might be another participant joining the group
Jon: interested in working on the rules
Jon: I will update all code to use this new code
Widget Rules
Jon: /member/wiki/WCAG_2.0_Principle_4_Robust_Rules#Requirement_4.1.2_Name.2C_Role.2C_Value
Jon: last week started discussing ARIA rules
Jon: WIDGET_1 must have 1.) labels or 2.) names?
Marc: would prefer 1.)
Philip: what would be a "label", something shown on the screen?
Jon: yes, similar to labels used in forms
Rich: for example checkbox, the text would be the label?
Jon: yes
Jon: would prefer 1.)
Jon: use 1.) for now
Ann: what about label/name?
Jon: think it is important to be concise
Ann: WCAG 2 says "name"
Rich: "name" is what is computed
Ann: for example 4.1.2
Jon: ok, then we will use 2.)
Ann: doesn't "title" only gives a tooltip?
Jon: "title" is kind of backup
Jon: for computing the name
Jon: is "title" used much in IBM tools?
Ann: I think not
Marc: agrees
Jon: WIDGET_2
Jon: ARIA properties and states must have valid values
Ann: what about changing the ACTION to "use value according to specification"?
Jon: ok
