Accessibility Minutes 2012 08 20

From MemberWiki

Jump to: navigation, search

Contents

Present

  • Ann Abbott (IBM)
  • Richard Schwerdtfeger (IBM - Co-Chair)
  • Jon Gunderson (University of Illinois - Co-Chair)
  • Prasanna Bale (University of Illinois)
  • Nicholas Hoyt (University of Illinois) - Scribe

Minutes

Cache Inspector Prototype

JG: Any feedback on the prototype?

AA: I liked what you demoed last week.

JG: Next week may be able to demo Firebug extension.

Bypass Blocks Rules

JG: /member/wiki/WCAG_2.0_Principle_2_Operable_Rules#Requirement_2.4.1_Bypass_Blocks

JG: Last time we were working on Bypass Blocks.

JG: At this point we have discussed HEADING 1 and HEADING 2 rules.

JG: Let's start with LANDMARK X rule.

NH: Where is accessible name for landmarks defined?

AA: http://www-03.ibm.com/able/guidelinesa>

AA: The link only applies to main landmarks.

JG: Let's leave the rule as it is for now; will reconsider landmarks to which it applies if we get pushback.

JG: We could rewrite the rule so that it applies only to main, navigation and complimentary landmarks.

AA: We have the same sort of rule for article and group roles (and also abstract region).

JG: What's happening with role=application?

RS: Would like to deprecate it at 1.1

JG: Do we want to make that a separate rule (for article and group roles)?

AA: http://www-03.ibm.com/able/guidelinesa>

RS: The reason we don't have article as a landmark is that you can imagine a discussion with hundreds of article responses (e.g. in a comments section), which would be a lot of landmarks.

JG: Developers seem to want to use role=article, but they misunderstand its intended use.

JG: Have updated LANDMARK X; may want to break this down into two rules, one for the specified landmarks, and one for the roles article and group.

JG: Will likely break them down for the purpose of better results messaging.

JG: LANDMARK_1 rule: Every page must/should have at least one container element (e.g. DIV element) with a role attribute set to the value "main".

AA: Above link is another checkpoint for LANDMARK X.

JG: LANDMARK_1 seems okay.

JG: LANDMARK_2: All renderable content must be contained within a landmark (i.e. application, banner, complementary, contentinfo, form, main, navigation, region, search).

JG: Does this belong in Bypass Blocks section?

JG: Other possibilities: 1.3.1 (single A requirement addressing structure).

JG: Am thinking it should be under 1.3.1.

JG: We are working on reorganizing the rules documentation by rule categories instead of organized by WCAG.

AA: I'm trying to find out where we placed it.

AA: We placed it in 2.4.1

JG: We will leave LANDMARK_2 where it is (2.4.1).

JG: TITLE 6 is subsumed by HEADING 1.

JG: TITLE 7: Skip navigation link: This may be more of a LINK rule than a TITLE rule.

AA: At IBM the rule applies to older browsers.

JG: Is this a requirement?

RS: Why do we require skip links with older browsers?

RS: We could recommend it in the transitional ruleset.

JG: And leave it out of strict ruleset.

AA: Even IE6 and JAWS handles landmarks properly.

Personal tools