Monday 6-25-2007 General telecon

MINUTES FROM 6-25-07 General Teleconference Meeting As ammended and approved 7/9/07

1. Confirm minutes of Last meeting Monday 6-18-2007 General telecon
   • Minutes Approved
2. Add a functional PC for "those without reach, without strength, who cannot touch the product" ?
   • people with limited reach and strength, it is also about people with no reach and no strength, who cannot touch the product? Those who cannot use their arms. And those who cannot use any appendage including a head or mouthstick. That must control things using eye gaze, head movement, sip/puff, brainwaves etc - and must therefore have a way of connecting their own interfaces to the product rather than operating the products buttons.
   • this would have to be an AT access provision no?
     • speech is non-touch but not cover all.
     • eyegaze - ditto
     • DISCUSSION
       • Does there need to be a provision?
         • There are many people who can not otherwise reach out and touch the product. CP, High Spinal Cord injury. Need to not leave them out.
         • Agree that we need to do this but is this the right place. If there are not solutions today should it be a FPC. If no built in today -then we force AT - and we don't force AT today in other provisions. (what about closed systems?). Is there another way to address this?
         • There are techniques that are available, they just aren't built in today. Examples include
           • Head tracker that doesn't require anything be attached to the head
           • Speech input
           • Eye Gaze
         • Don't leave these people out just because it is hard area today. Things are changing rapidly and we shouldn't leave this out or else the pressure to address it will all disperse. It can be met in some cases today and this will increase with the future.
         • Should we special case this - to avoid the situation where no closed product can meet this for the foreseeable future.
         • One concern was how to allow connection to voting or financial machines via USB without creating a security problem.
         • Also the physical manipulation aspects area problem
       • Should it say just "via AT" or "directly or via AT"
         • No need to remove direct access option. Only removes options and limits what might be done in the future.
   • DECISION: Did not reach consensus. some ideas:
     • Keep the functional performance criteria general but put a comment in the Closed section that limits it.
     • Write a FPC that includes the limitation for closed products.
     • Put in an FPC like this and push really hard for a "safe" way to have open public products. That is - products should always (or almost always) allow connection of AT through a "safe" mechanism.
       • Or at least ' for those disabilities where you cant build access in - provide a way to allow connection via a 'save" mechanism.
   • DECISION-ACTION ITEM: People need to propose specific language to the list for discussion.
3. Users' AT
   • "User's AT" proposal out for review
   • Best approach as of end of meeting: just use "AT"
   • DECISION: To change "users' AT" to "AT"
4. BIOS ISSUE
5. Cognitive FPC
   • At least one mode shall be provided that accommodates cognitive, language or learning impairments, directly or with users' AT.
   • Is this harder than other FPC
   • Better wording?
   • Cost benefit language?
     • DECISION - Add following note to current draft item on cognitive: "This provision is here as a placeholder. The general group identified the following issues and questions in trying to move this forward.
       1. Should we have an FPC when we dont have very many technical provisions saying to this would be done?
       2. The range and variety of cognitive, language and learnign disabilities is so wide that the question arises , could any product meet this FPC for the full range of people with CLL disabilities.
   • Cognitive still needs more work.
6. New provisions needed but not yet defined by any group

Action Items (Individuals)

• Action All: read 255, 508 and EITAAC technical provisions to see what is missing
• { Past work items DONE . }