Monday 11-05-2007 General telecon

Minutes from Monday 11-05-2007 General telecon

Agenda

1. Confirm minutes of Last meeting Monday 10-22-2007 General telecon
2. Confirm this Agenda
3. Further discussion on AT vs API vs etc.
   • clarification and search for language for draft
4. Further discussion of "no reach or touch"
   • address issues raised on list

Notes from Meeting

1. Does current text requires E&IT to work with actual AT?
   • Some say yes.
   • Some say no.
   • if it doesn't then E&IT is not usable by employees - and that is the only purpose of the law
2. what does "works with AT" means?
   • Don't have to support all AT features - just access to function
   • "Works with AT means":
     1. can use AT to access all info
     2. can use AT to carry out all functionality
3. Done as 2 Separate purchases - this is a problem
   • requiring IT but not AT to work together
     • AT already required to work with IT (or at least some IT) or it can't be sold.
4. How is this different than specifying that an app will work with a browser?
   • Web App only run through browser
   • app not necessarily run through AT

PROPOSALS FROM MEETING

1. . To meet these standards via AT compatibility, E&IT must work with some AT that is available to the users with disabilities that are to use the E&IT.
2. . To meet the provisions of this standard via AT compatibility, E&IT allow the provision to be met using some AT that is available to the users with disabilities that are to use the E&IT.
3. . To meet these standards via AT compatibility, E&IT provide access to full information and functionality through some AT that is available to the users with disabilities that are to use the E&IT.

BEST PROPOSAL AT END OF MEETING

To meet these standards via AT compatibility, E&IT must provide access to full information and functionality of the E&IT through some AT that is available to the users with disabilities that are to use the E&IT.