Accessibility Minutes 2009 05 27
From MemberWiki
Participants
- Jon Gunderson (University of Illinois)
- Nathan Jakubiak (ParaSoft)
- Vio Onut (IBM)
- Rich Schwerdtfeger (IBM - chair)
- David Todd (IBM)
- Derk Stegemann (FIT)
- Michael Squillace (IBM)
Minutes
Rich: Start with language. If lang attribute is missing generate a violation.
Team: How do we want to structure the rules. Base on WCAG 2.0 structure?
Rich: Inconsistent with the way we have rules structured.
Jon: It makes sense to align rules under WCAG requirements.
Jon: Rules may apply to more than one WCAG guideline. One potential problem. But we could start out with WCAG structure.
Jon: Developers approach accessibility 2 different ways. From an end of development addition to those wanting to incorporate accessibility at development time.
Team: Initial approach will be WCAG structure.
Jon: Will incorporate rules into his best practices document.
Rich: Will initially base structure on WCAG structure.
Rich: starting discussion on language rules.
Jon: Probably should be manual check for multiple languages on a page.
Rich: adding Jon's manual language check as a best practice.
Jon: If user says there's more than one language on a page, do a manual check to see that multiple lang attributes are used correctly.
Rich: Moving to form labeling rules.
Rich: is title attribute legal?
David: WCAG says label is preferred but title is legal.
Jon: ARIA describeby can be used to show relationship between controls and descriptions.
Jon: use ARIA describedby to describe input controls.
Rich: giving a explanation of ARIA describedby.
Rich: ARIA describedby used to provide additional information for example a widget.
Nathan: how does describedby handle required input wording?
Rich: describedby can be associated with multiple input elements.
Rich: Do we want to have a warning that's not programmatically associated with a control? Yes
Jon: Or be marked as presentation.
Rich: Giving explanation for "presentation" role.
Rich: Text in forms must be referenced by describedby or labelledby. Otherwise, the text should be marked as "presentation".
Jon: This should be a failure if not met.
Jon: The WCAG guideline for labels is 3.3.2.
Rich: Do we want to leave bullet 8 in or out?
Rich: We don't need checkpoint 8.
Team: Remove checkpoint 8.
Rich: Maybe give presentation to W3C WAI.
Rich: All major browsers zoom the entire page.
Rich: Do we care to support older browsers regarding zooming.
correction Rich: all older versions of major browsers zoom the entire page.
Jon: Should spend a lot of time with this.
Team conclusion: zooming not addressed because browsers zoom the whole page.
Rich/David: aria-required is required for IBM checklist.
Jon/Rich: Create a potential violation if aria-required is used and a form element has an asterisk indicating required. Only one is required not both.
Jon: Some developers only worry about passing the tool not really accessibility.
Vio: are we changing the meaning of potential violation and violation.
Vio/Nathan: Generate a recommendation instead of a violation.
David: Will have to have both visual indication of required field as well as aria-required.
Action Items
none