Accessibility Minutes 2009 04 15
From MemberWiki
Contents |
Participants
- Ann Abbott (IBM)
- Jon Ferraiolo (IBM)
- Jon Gunderson (University of Illinois)
- Nathan Jakubiak (ParaSoft)
- Vio Onut (IBM)
- Tony Salcedo (ParaSoft)
- Rich Schwerdtfeger (IBM - chair)
- Mike Squillace (IBM)
- Derk Stegemann (FIT)
- David Todd (IBM)
Minutes
innerHTML/document.write
RS: Andi Snow-Weaver says not required, bad requirement
Group: ...no support until told otherwise
use of <b>, <strong>, etc.
JG: should apply to any styling via inner tags (e.g. <em>, <strong>, etc.)
squillace: ...use should result in a violation
JonGund: * The font and center elements must not be used. Instead use structural markup with CSS for styling.
JonGund: * The b element must not be used for bold styling of text content. Instead use heading elements h1..h6 for heading text or the strong element for emphasizing words, phrases or sentences.
JonGund: * The i element must not be used to italicize text content. Instead use heading elements h1..h6 for heading text or the em element for emphasizing words, phrases or sentences.
JonGund: * The u element must not be used to underline text content. Instead use heading elements h1..h6 for heading text or the em or strong elements for emphasizing words, phrases or sentences.
JonGund: * The blink and marquee elements must not be used.
JonGund: Blinking or moving text causes accessibility problems for people with photosensitive epilepsy and visual impairments.
Event handlers
RS: rule: generate violation when only pointing/jouse-oriented event handlers present
JG: finding event handlers in and of itself is expensive
DT: http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/F54
JG: actual WCAG2 criterion seems to indicate pointing device-speicific handlers for script functions, not nodes
VO: RPT looks for particular onmouseXXX/onXXX pairings (e.g. onmouseover, onfocus or onmouseout => onblur)
VO: ...wiki updated with full set of pairs; error generated when one of pair is missing
RS: what if a container element is managing sub-controls (e.g. grid)? How is this algorithm effected?
JG: find event handlers and at least one parent supports onkeyXXX or simulate keystroke into widget and see if it is consumed by it
squillace: ...other issues is just being able to enumerate the handlers; most of them are added in the script code
ACTION: JG to update event handler section due 04/22/2009