Wednesday 1-17-2006 General telecon

Wednesday 1-17-2006 General telecon

AGENDA ITEMS FOR JAN 17 MEETING

1. Continued discussion of Characteristics
   • TAGs from "Functional Components View"#Current Working list of Product Characteristic Tags Current Working list of Product Characteristic Tags
   • GreggV's Analysis and Sorting Tool for 508, 255, and EITAAC provisions
     • TAGs from "Functional Components View"#Sort Categories for Provisions New Sort Categories
2. 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?
   • 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.

Attendees

• captioner
• Tom Albin, Auburn Engineers
• Tom Brett
• Michael Takemura, HP & ITI
• Nick Truesdell (IRS)
• Robert Baker (SSA)
• Michae
• Andrew Kirkpatrick (Adobe)
• Deb Cook; ADA & IT Centers
• Michael Cooper, W3C
• GreggVan (Trace)
• Mike Fratkin (SSA)
• Terry Weaver, GSA
• Shannon Rapuano - IBM
• Alex Li - SAP

Misc Notes from meeting

• Master Analysis Sheet
  • looks good
  • no suggesting for improvement yet
• (re)Organization of provisions by General Need / Strategy
  • Looks like it would be useful to purchasers/companies
• TO DO - as soon as possible
  1. Attempt to Create a Common View of provisions
     • useful to all stakeholders (best common view)
     • used as common view and way to communicate between
     • complement custom views tailored for particular stakeholders
  2. Suggest ways to Reduce the number of provisions if possible
     • possibly by combining very similar items
     • possibly by putting specific as implementations of general
     • other ways?
     • pass any ideas on to groups that are working on them
  3. Refine the categories
     • some items like "Alternative Info and Control" have 25 provisions. should this be broken down differently?
     • better grouping or names?
  4. Any proposal for a Reorg that could be used for a combined 508 255
     • Web content and Applications combined?
     • Use the Common View?

Transcript

Transcript of Wednesday 1-17-2006 General teleconn