Accessibility Minutes 2012 02 06
From MemberWiki
Present
- Jon Gunderson (University of Illinois - Co-Chair)
- Nicholas Hoyt (University of Illinois)
- Rich Schwerdtfeger (IBM - Co-Chair)
- Prasanna Bale (University of Illinois) - Scribe
- Marc Johlic (IBM)
- Ann Abbott
Minutes
Jon: The web best practices group with which Jon is working want to have their own rule set
Jon: This ruleset would be based on the WCAG 2.0 and similar to the ARIA except for some rules
Jon: The name of this ruleset isn't decided yet. Is this okie to add a column in the wiki for this new ruleset\
Ann: yes
Jon: CONTROL 4:Button elements must have text content and input type button must have a value attribute with content
Jon: It is more like bad markup and can be a warning / if it is treated as Accessibility issue then it can be recommendation
Nick: sufficient techniques on CONTROL4 isn't making much sense
Jon: can take out technique H44 from CONTROL 4 as it doesn't work with it
Prasanna: http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-identified
Rich: stepping away briefly
Rics: back
Prasanna: group consensusto make CONTROL4 as violation
Ann: Can we go back to CONTROL3
Jon: CONTROL3 is all about grouping requirement and made as Recommendation
Nick: WCAG is very clear on technique H71
Anna: http://www-03.ibm.com/able/guidelines/web/webstructure.html
Anna: HTML example 6
Nick: Any consensus Checkboxes should need to be included?
Marc: we don't call checkboxes specifically than other controls to group buttons
Nick: I can see programatically in a JSON object for check boxes n talk further next week
Anna: WAI-ARIA group and radiogroup roles
Anna: As an alternative to the HTML <fieldset> and <legend> elements, the WAI-ARIA group and radiogroup roles may be used to group radio buttons and other controls.
Anna: radiogroup: http://www.w3.org/WAI/PF/aria/roles#radiogroup
Prasanna: Will discuss CONTROL3 next week
