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.

Tools concall

Contents

Notes for spontaneous conference call 10/12

Most important ideas from this call were sent to the committee in Announcement 10.13.2006.

Agenda

Mike asks: Can we have someone put together a brief outline of the outstanding issues that need decisions?

  • Queuing software / agents
  • Who can edit the wiki?
  • What does subcommittee membership mean?
  • Should we differentiate MailList membership and SC membership?
  • How best to use Jared’s time.
  • Delegation of administrivia?
  • Other tools demos, example: Lets Go Expo.
  • Recommended procedure for subcommittees.

From the Protocols

http://www.access-board.gov/sec508/refresh/protocols.htm

  • Subcommittees may be formed to address specific issues within the scope of the advisory committee’s responsibilities.
  • Subcommittees are open to anyone although balance among interests should be maintained.
  • Subcommittees may meet at the same time the full committee meets, or in between full committee meetings.
  • However, subcommittees are encouraged to meet in between full committee meetings.
  • Subcommittees may offer recommendations to the committee.
  • However, subcommittees are not authorized to make recommendations for the committee.
  • In subcommittees, anyone in attendance can participate.
  • Subcommittee leadership and methods of work shall be decided by the subcommittee.
  • Subcommittee meetings shall be conducted in a manner that is accessible to all those in attendance.
  • Chairs of subcommittees shall be members of the committee.
  • Subcommittees shall publish their meeting schedules and other work mechanisms in advance to the public.
  • A progress report of subcommittee meetings shall be prepared and sent by subcommittee chairs to committee members prior to the next meeting.
  • Full committee and subcommittee meetings will be held in accessible locations and provide for communications and print access.

Decisions / Conclusions

  1. Queuing software / agents
    • Zakim is not looking likely. We will get a demo from the W3C. Without a compatible conference bridge, users will need internet access and if this is the case, then a web-based queue manager will be easier to implement and use.
  2. Who can edit the wiki?
    • People who register for the wiki
    • Address abuse when and if it happens
    • Any page can be protected from further editing. Allowing partial editing access is problematic.
  3. What does subcommittee membership mean?
    • Identification of subcommittee members helpful to chair for knowing when consensus has been reached.
    • Subcommittee members commit to participate in the subcommittee work product.
  4. How does one join a subcommittee?
    • Either:
      1. Email the chair (via the list is easiest and preferred); or
      2. Add you name to the subcommittee participants page.
    • Subcommittees can add additional requirements on members
      • Expectations must be posted to subcommittee work page
  5. Should we differentiate mailing list membership and Subcommittee membership?
    • Yes. The subcommittee work page contains a roster.
  6. How best to use Jared’s time.
    • As we are.
  7. Delegation of administrivia?
    • Not at this time.
  8. Other tools / demos / consideration
    • Example: Let’s Go Expo.
      • ATIA has lots of success with it.
      • May be compatible with RCC.
    • Put suggestions, ideas on the Task Force Wiki page
      • Include concerns / issues
  9. What constitutes public notice?
    • Federal Register?
    • Access Board 508 update page?
  10. Recommended procedure for subcommittees.
    • Use the listservs!
      • Reference good transition examples provided by Larry and Andi.
      • Add notes on what consensus means (see David C.’s slides)
        • Subcommittee can capture minority views
      • No requests for consensus on controversial issues discussed on listserv without allowing at least two full business days.
        • This includes determining subcommittee leadership and methods of work.
    • For teleconference calls:
      1. Arrange for captioning.
      2. Post all dial-in and RCC information at least 48 hours in advance to all of the following:
        1. To the teitac subcommittee distribution list
        2. The subcommittee work page
        3. The calendar.
          • To have an event added to the calendar, contact Jared Smith or Jim Tobias.

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