Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional and up-to-date details on the updates to section 508 and section 255 can be found at the Access Board web site.

Monday 8-6-2007 General telecon

Minutes for Monday 8-6-2007

  1. Confirm minutes of Last meeting Monday 7-9-2007 General telecon
    • ACTION: APPROVED
  2. Confirm this Agenda
    • Reordered to put FPC first
  3. Review FPC status
    • FPC - purposes
      1. to fill in the gaps in technical provisions which were minimum
      2. to address all of the technologies not covered in technical provisions
      3. to address future technologies and interface techniques that we don't cover with technical provisions
    • Issues
      1. primarily - testability. they are good goals but how do you test them?
    • COmments
      • Problem if we make them aspirational without taking time to do all the additional technical - and still a problem for future technologies and what we dont think of.
      • Concern is both with some of the changes made to performance criteria
        • must work with AT instead of supporting AT
        • adding cognitive
        • no burden on AT to reciprocate
      • Government people looked at this and had a couple issues/problems
        1. Do FPC and Tech Provisions travel together or are they either/or
        2. They used to be later - so it gave us the ability to go back after people
        3. Don't want FPC to go away - but putting first was more problematic - and the ones that were added - though they close some gaps they draw attention to them.
        4. Haven't ..
      • Keep them 'broad'
      • Good for checking work after technical and for equivalent facilitation
      • If FPC are testable then they are a second set of technical requirements
      • There is a role of the FPC and we use them as check at end and when technology doesnt fall in Technical
      • Real issue is 'support for AT' vs works with AT. We work very closely with AT to make sure it works.
        • sometimes AT vendors cant work with us - even if we pay them.
        • both of us must play
        • not possible to 'work with all AT' or 'all versions of AT'
        • not possible to make all controls work with AT
      • a middle ground for this would be to say "FPC is for 'if you cant meet technical then do it some other way and say how you did it' "
      • change FPC into requirement for company to show how it tested and meets the requirements.
      • FPC must be criteria that can be met.
      • Cant be required to demonstrate that things work with AT that does not exist
      • FAQs both say it is AND and OR
      • should check with the Access Board to see what their intent was.
      • What is not working about what was there?

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University