Accessibility Minutes 2011 10 31
From MemberWiki
Contents |
Present
- Jon Gunderson (University of Illinois - Co-Chair)
- Ann Abbott (IBM)
- David Todd (IBM)
- Marc Johlic (IBM) - Scribe
- Prasanna Bale (University Of Illinois)
- Philip Ackermann (Fraunhofer Institute for Applied Information Technology)
Minutes
Agenda: http://openajax.org/pipermail/accessibility/2011-October/000638.html
New Member
New member: Philip Ackermann, Fraunhofer Institute for Applied Information Technology, Web Compliance Center (WebCC)
Thanks Philip
Cache Inspector
Jon: Analyzed some 26K web pages using new rule sets / identified some bugs / showed that the rules are working pretty well.
Jon: Working on improving performance on duplicate href rules (had to disable rule during testing of html unit). Will retest with new algorithm
David: What performance increase did you see w/ rules disabled
Jon: Not able to directly identify increase, but it certainly seemed to run faster when those rules were taken out
Jon: New version of Cache Inspector published - using new rules
A new version of the OAA cache inspector is available: http://code.google.com/p/oaa-accessibility-cache-inspector/downloads/list
Jon: Took 5 seconds to analyze a page compared to around a minute before
Rules discussion
Titling Rules
Jon: Titling brings up the need for two separate rule sets.
Jon: Consider naming structure of these two rule sets of "Transitional" (today's rules) and "ARIA"
Transitional would be for non-ARIA web pages
Rules in Transitional rule set would be recommended
Rules in ARIA rule set would be required
This would be a change of our current severitys of "Minimum" and "Strict"
Minimum = Transitional and Strict = ARIA
Ann: Naming convention certainly seems more clear
all agree - that this Transitional and ARIA naming convention makes more sense
Transitional would be folks / pages that have not made the jump to ARIA yet
Title_1 would be violation of both Transitional and ARIA rulesets
Title_2 would be a Recommendation for both
Title_3 would be a Recommendation for Transitional and is not included in ARIA ruleset
Title_4 would be a Recommendation for both
The 100 characters limit of Title_4 could be changed / updated if needed
Title_3 changed to: "The words in the H1 element content on the page should be a subset of the words in the content of the TITLE element "
Title_5 would be a Potential Violation for both rulesets
Jon: next requirement is 2.4.3 Focus Order
No rules written for 2.4.3 yet
/member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.3_Focus_Order
David: Not sure we could develop anything to test specifically for correct focus order
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
http://www-03.ibm.com/able/guidelinesa>
/member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.4_Link_Purpose_.28In_Context.29
2.4.3 Focus Order updated with rule Focus_Order_1 (Potential Violation)
Requirement 2.4.4 Link Purpose
/member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.4_Link_Purpose_.28In_Context.29
1. Provide descriptive link text: Provide link text that describes the purpose of a link.
2. Identify the purpose of a link using enclosing sentence: Identify the purpose of a link using link text combined with the text of the enclosing sentence.
3. Identify the purpose of a link programmatically: Identify the purpose of a link using link text combined with programmatically determined link context.
Jon: We currently don't have any WCAG techniques for these rules
Jon: Have tested it with AT
Jon: We have implementation support and potential support w/ Voice Over
http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/ARIA1
Ann: aria-describedby is only recommended technique in IBM checklist
Jon: For now we need to stick w/ WCAG and will make this one recommended
Call ended at 2:02pm Eastern --MarcJohlic 19:40, 10 October 2011 (UTC)
