Accessibility Minutes 2009 06 03

From MemberWiki

Jump to: navigation, search

Participants

  • Nathan Jakubiak (ParaSoft)
  • Rich Schwerdtfeger (IBM - chair)
  • David Todd (IBM)
  • Michael Squillace (IBM)

Minutes

Starting with number 10

Labeling rules number 10

From Jon's Best Practices but can't be tested programmatically

dstege (n=chatzill@trio.fit.fraunhofer.de) has joined number oaa-accessibility

Not found in WCAG 2.0

David recommended leaving in with note to Jon re: why included? Group agreed.

http://www.usability.com.au/resources/wcag2/

This channel requires that you have registered and identified yourself with the network's nickname registration services (e.g. NickServ). Please see the documentation of this network's nickname registration services that should be found in the MOTD (/motd to display it).

number 10 made Optional/Manual test

http://www.w3.org/WAI/WCAG20/quickref/20080430/Overview.phpnumber qr-minimize-error-identified

number 11 error identification

Per Rich: all on this page will need to be referenced to WCAG speciific numbering scheme.

number 11 made Manual/programmatic test

number 10 & 11 combined and made Potential Violation

Logical tabbing order must be manual test.

Nathan: results wouldn't be included in report, just a flag to manually test

number 12 = potential violation

http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-parses.html

Michael to reflow per WCAG 2.0

need reporting scheme

need kbd nav scheme

Modeling work and reporting scheme in parallel

Define rule set in script

Action Items

Michael: planning on using Java script

Personal tools