Accessibility Minutes 2012 07 16
From MemberWiki
Contents |
Present
- Jon Gunderson (University of Illinois - Co-Chair)
- Ann Abbott (IBM)
- Prasanna Bale (University of Illinois)
- Nicholas Hoyt (University of Illinois) - Scribe
- Richard Schwerdtfeger (IBM - Co-Chair)
Minutes
Update on OAA Library
JG: Implemented some of the heading and landmark rules
JG: Need to discuss adding to each rule and explicit Rule Category property
JG: Also some API issues re. filtering and getting a group of rules from a rule category
JG: Some issues with updating the format of the rules documentation
JG: Plan to release an update of Cache Inspector with some newly implemented rules
JG: Seems to be a bug with hidden/visible determination of elements in CI
NH: Recommend looking at new version of Cache Inspector with new dialogs for element properties and rule information
Rational Policy Tester
JG: Rational Policy Tester question: invited to demo this afternoon: there is a different ruleset used internally within IBM; if I were to recommend that they use that ruleset, what could I tell them
RS: Tell them that you understand that IBM is updating the WCAG 2 compliance ruleset that IBM uses for its internal products and making that available in RPT
RS: and that you would like to have that ruleset and that you participate in WG with RS
JG: Is there a name I can give them? That the IBM sales rep could talk to Constantine Grancharov product manager for policy tester
RS: If you're negotiating a deal, would like to have it include the next major update of RPT
RS: includes any IBM-specific rulesets for WCAG compliance
JG: We badly need it here (e.g. Travel Expense Management system which is inaccessible)
RS: WCAG 2 compliance rules are very abstract; to get something that works, we really need something that has been tested by dev. community and end users that addresses rich web app accessibility
JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules
Discussion of headings and landmarks rules
JG: Would like to go over some of the issues with landmark rules; have been working on them in the past week
JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.1_Bypass_Blocks
JG: Under Bypass Blocks, let's look at HEADING_1 rule: Each page must/should contain at least one h1 element and each h1 element must have content
AA: Should HEADING 1 be required or recommended?
AA: For transitional ruleset, do you already have requirement for at least one h1 on a page?
JG: We do internally, but there has been pushback.
AA: What is their reasoning?
JG: For bypass block, some feel that it's not absolutely necessary; could make it required in Strict Ruleset
JG: WCAG WG interpretation: if you do use headings... requirements are AAA
JG: WCAG 1.3.1: If you have things that look like headings, you should use h1..h6
JG: Next rule relates to h1's being used with main landmarks
JG: HEADING 2: h1 elements must/should be used as labels for main landmarks
AA: Will HEADING 2 rule cause redundant content read by screen readers?
RS: They could be different, but in practice they may not be.
RS: Would recommend that we not make it a strict requirement, even in ARIA Strict
PB: What about case where we have more than one h1?
JG: If more than one main landmark, each should have just one h1 per main landmark.
NH: Is this just an AT problem, and they should be able to avoid reading redundant content?
JG: Forms are different because of the way that focus induces AT to read accessible name.
JG: Will review this one next week.