Accessibility Minutes 2012 05 14

From MemberWiki

Jump to: navigation, search

Contents

Present

  • Jon Gunderson (University of Illinois - Co-Chair)
  • Richard Schwerdtfeger (IBM - Co-Chair)
  • Ann Abbott (IBM)
  • Marc Johlic (IBM) Scribe
  • Prasanna Bale (UIUC)
  • Nick Hoyt (UIUC)
  • Philip Ackermann (Fraunhofer Institute for Applied Information Technology)

Minutes

scribe marjohlic

JG: /member/wiki/Accessibility_Ruleset_Rule_and_NLS_Format_2.0

AA: Attending: Jon Gunderson, Ann Abbott, Marc Johlic, Nick Hoyt, Philip Ackermann, Prasanna Bale, Richard Schwerdtfeger

TOPIC: Adding Node level and Page level rules

JG: Page level rules pass / fail once on a page - whereas an image or form labeling rule ; there's a lot more opportunities to fail that rule.

JG: With Page rules, either you have that rule or you don't.

JG: If Page rules pass, you can usually point to nodes that helped pass, but when they fail you can't typically point to a node that caused the page failure

JG: As Ann pointed out, will probably have to report them differently - but we're not sure how those reports will look yet

RS: Need to have some guidance around proper use of headings on a page - particularly for more complex pages (cover nesting, usage, labeling etc)

JG: Need to update rule format and terminology on our web page

JG: /member/wiki/WCAG_2.0_Principle_4_Robust_Rules

JG: /member/wiki/WCAG_2.0_Principle_4_Robust_Rules#Requirement_4.1.2_Name.2C_Role.2C_Value

TOPIC: ARIA validation rules

JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.6_Headings_and_Labels

JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.6_Headings_and_Labels

JG: Related techniques - An example would be 2.4.6 Headings and Labels and the rule HEADING_2T. The primary technique is 2.4.6, but 1.3.1 would be a related technique as would 2.4.10 (AAA).

JG: Added an object to capture related techniques

AA: It will be like a cross reference

NH: Will help to show a fuller picture from a compliance standpoint

JG: /member/wiki/WCAG_2.0_Principle_4_Robust_Rules#Requirement_4.1.2_Name.2C_Role.2C_Value

JG: WIDGET_1 is another example - where 4.1.2 is the primary technique, but 3.3.2 would be related.

JG: /member/wiki/WCAG_2.0_Principle_3_Understandable_Rules#Requirement_3.3.2_Labels_or_Instructions

JG: "RELATED REQUIREMENTS: 1.3.1, 2.4.6, 3.3.2 "

JG: /member/wiki/WCAG_2.0_Principle_1_Perceivable_Rules#Requirement_1.3.1_Info_and_Relationships

AA: http://www.w3.org/WAI/WCAG20/quickref

AA: Using WCAG quickref to help map sufficient techniques to success criteria

JG: http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H44

RS: http://dev.w3.org/html5/spec/forms.html#category-label

RS: Some elements, not all of them form-associated, are categorized as labelable elements. These are elements that can be associated with a label element.

RS: button

RS: input (if the type attribute is not in the Hidden state)

RS: keygen

RS: meter

RS: output

RS: progress

RS: select

RS: textarea

Personal tools