Accessibility Minutes 2013 10 28
From MemberWiki
Contents |
Present
- Ann Abbott (IBM)
- Marc Johlic (IBM)
- Rich Schwerdtfeger (IBM)
- Jon Gunderson (University of Illinois)
- Nicholas Hoyt (University of Illinois) - scribe
Minutes
AInspector Sidebar
NH: Main changes in latest prototype relate to recently added rules.
NH: Also tweaked the UI layout to improve consistency across platforms (Mac OS X, Win 7 and Win 8).
Rules and Rulesets
Coverage of WCAG
JG: http://dev.oaa-accessibility.org/rulesets/wcag20/
JG: Link shows mapping of our current rules to WCAG 2.0
JG: The only guidelines where we're lacking rules are 2.2 Timing and 2.3 Seizures
NH: Also do not have rules for 1.3.3, 1.4.1, 1.4.2, 1.4.4, 1.4.5 and 3.2.4, 3.3.1, 3.3.3, 3.3.4
RS: If you have valid attribute from HTML 5 and ARIA invalid, that is a problem
JG: Want to spend some time going over new rules recently added
Ruleset Constituency Groups
JG: Want to validate that IBM is mainly interested in ARIA-STRICT ruleset
AA: Yes, that is true
JG: Still need to validate our main constituent group for ARIA-TRANSITIONAL
JG: Probably will change the name of the latter ruleset
JG: Based on: What is the first thing a developer typically wants to do: workflow, where to start?
Questions re. new rules
JG: Nested heading rules
JG: Have rewritten some of these recently
JG: HEADING 5 is global nesting rule for headings
JG: LANDMARK 6 only looks at nesting of headings within landmarks
NH: IANA is Internet Assigned Numbers Authority
NH: They assign all of the language codes, such as en-US
JG: Re. nesting rules, how should we differentiate between entire page and within landmarks?
JG: In my mind, within a landmark, you should always start with heading level 1 or 2
JG: A stricter rule would say that the only landmark you would start with h1 would be MAIN; other landmarks you could/should start with h2
RS: What about multiple h1s?
JG: Should the rule re. heading levels within landmarks be recommended?
NH: Consensus among AA and MJ: let's make the rule recommended
RS: Recommended is fine
NH: Specifically, re. which heading levels should be used (start with) in various landmarks
JG: Also, global heading rule will be taken out of ARIA-STRICT
JG: MAIN landmark - something that we want on every page, also NAVIGATION
NH: Last entry applies to new section: Landmark rules
JG: Under 2.4.1: every page must have MAIN and NAVIGATION landmarks
JG: 3.2.3 and 3.2.4 are about consistent navigation
JG: and these latter SCs are website scope, where the former is page scope
JG: We could give users the options to say: Don't analyze these pages as part of a website, in which case we would disable rules with website scope, such as those rel. to 3.2.3 and 3.2.4
JG: Is it okay to have the lack of MAIN landmark cause you to fail not one but three rules
JG: Second question: If you only have one MAIN and one NAVIGATION, you probably shouldn't have any labels on them, right?
JG: If you have more than one MAIN or NAVIGATION, then you need labels on each of them
JG: Everyone's okay with violation when you don't have MAIN or NAVIGATION on every page of website?
AA: I think we're going to need user option to switch on or off whether page should be considered as part of website
JG: Another question: I changed rules rel. 2.4.1 re. BANNER and CONTENTINFO landmarks
JG: Do you require both of these at IBM
RS: We require MAIN and that everything being in a landmark
AA: Only one CONTENTINFO landmark is permitted, and is not permitted without presence of MAIN role
JG: What about SEARCH
AA: If you have search function, then you need SEARCH role