Monday 12-18-2006 General telecon

Monday 12-1-2006 General telecon

AGENDA ITEMS FOR DECEMBER 18 MEETING

1. Review of Current Working list of Product Characteristic Tags
2. Review of GreggV's Analysis and Sorting Tool for 508, 255, and EITAAC provisions
   • What can we learn about the guidelines from it
     • Some initial Observations from GVan
     • Observations from others
3. Deliverables continued - What might we be working toward
   • New cross-technology way of looking at guidelines?
   • Set of TAGs that can be used by companies to reduce the listings?
     • (e.g. my products does not a,b,c -- which would lead to a reduced listing of guidelines)
   • How to handle Performance Guidelines?
   • Guidelines + Success Criteria + Sufficient Techniques?

Attendees

• tom brett
• Jim Thatcher
• captioncolorado
• Hajime (JAPAN)
• David Oyola (Ricoh Corporation)
• Bruce Bailey (Access Board)
• GreggVan (Trace)
• Alex Li - SAP
• Debbie Cook: ADA & IT Centers
• Tom Albin Auburn Engineers
• Kate Walser (SRA)
• Rob Nerhood
• Whitney Quesenbery (UPA)
• Katie Haritos-Shea
• Michael Cooper, W3C
• Terry Weaver - GSA
• Jim Allan (W3C)
• Rob Haverty, Microsoft

Misc Notes from meeting

• Types of AT compatibility / openness
  1. Not interfere - with use of AT in the area
     • Hearing aids (some phones and some old monitors with large magnetic fields)
     • Wheelchairs
     • Ability to use alternate keyboards and mice through USB port
  2. Allow use of Particular personal AT - but not cover access by AT across all disabilities)
     • allows use of prosthetics and headpointers (e.g. not require human touch)
     • assisted listening devices - (e.g. provide headphone jack)
  3. Internal AT - Full function Access - All function of device interface can be achieved across disabilities through AT that can (physically and via policy) be installed in product
     • Screen readers
     • On screen keyboards and pointing device substitutes
  4. External AT - Full function Access - All function of device interface can be achieved across disabilities through AT that can be connected via external connector
     • (basically the ability to plug an alternate full interface into product)
     • Copier company(s) have done this - but connection is not standard so they created their own AT that would work with it
     • Copier company(s) have also created a workstation program that would connect via the connector where the workstation program was on a computer that did allow installation of AT. The combination of copier and workstation then became an "open" system under #3.
• Types #2 and #3 would be 'open' systems if the connection point were supported by AT.
• can user do along?
• is OS the right word?
  • in ISO they use Platform and Application
  • browsers fall into both Application and Platform category

• Discussion of possible deliverables - added some so that the list now reads
  • New cross-technology way of looking at guidelines?
  • Set of TAGs that can be used by companies to reduce the listings?
    • (e.g. my products does not a,b,c -- which would lead to a reduced listing of guidelines)
  • How to handle Performance Guidelines?
  • Guidelines + Success Criteria + Sufficient Techniques?
  • Need for usability testing by PWD?
    • If so - all types? which types, degree, and combinations need to be included?
    • CIF (Common Industry Format for summative usability test reporting ) requires that you report who you test with but not who you test or that it cover the range of users.

Transcript

Transcript of Monday Dec 18 General telecon