Thread Subject: Re: Beyond the Calendar
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Gregg Vanderheiden
Date: Wed, Oct 11 2006 8:25 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Beyond the Calendar"
- Previous message in thread: Bailey Bruce: "Re: Beyond the Calendar"
- Messages sorted by: Author | Thread | Date
Lets stop calling it the WIKI and provide links to each subcommittee WIKI
page from the Main Website page - and call them simply "XXXXXX
Subcommittee Workpages" People who know WIKI will recognize them as such.
Those who don't will just see kind of plain looking web pages of
Gregg C Vanderheiden Ph.D.
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
The Player for my DSS sound file is at http://tinyurl.com/dho6b
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Andi Snow-Weaver
> Sent: Wednesday, October 11, 2006 6:55 AM
> To: TEITAC Communications Task Force
> Subject: Re: [teitac-tools] Beyond the Calendar
> With regard to the wiki, maybe we should stop calling it that
> if it scares people. It's just a website that everyone can
> look at and those who "choose" to can edit it. I don't
> believe everyone has to learn to edit it.
> You just need a few techies on each subcommittee to do the
> editing. The convenors might not know how to do it but there
> are probably techies on the subcommittees that do. I bet the
> only subcommitte that might be short of techies is the one on
> Subpart A.
> With regard to the listserv, the minimum thing that everyone
> has to do is simply e-mail. They can choose to archive all of
> the e-mail themselves in a way that is comfortable to them or
> they can access the archive site to see them all. I did
> notice one problem when I looked at the archives earlier this
> week: it looked like the first message on a topic was listed twice.
> That will be an efficiency problem for screen reader users
> and those with mobility issues and may confuse anyone with a
> cognitive problem. It would be good if that could be fixed.
> Jessica, what do you think is the issue with the listservs?
> "Bailey Bruce"
> Sent by: "TEITAC Communications
> Task Force"
> < = EMAIL ADDRESS REMOVED = >
> = EMAIL ADDRESS REMOVED = .o
> [teitac-tools] Beyond
> the Calendar
> 10/11/2006 03:43
> Please respond to
> Task Force
> We (the Access Board staff) had a meeting about this
> yesterday afternoon.
> Conference calls will probably be too unruly to be
> interactive without queue management. Gregg is looking into
> using the W3C Zakim software for that. Jared is also working
> developing queuing software.
> Fed RCC can be used to make teleconferences accessible
> between 8am and 5pm EST.
> There are free teleconferencing services available. If
> anyone feels they cannot participate because of the cost of
> making a non toll-free call, David Capozzi is willing to have
> the Board reimburse them for their expenses.
> Jessica, I think I have hit all your points below. The one
> exception is getting committee members comfortable with using
> the listserv and Wiki. Does anyone have ideas about
> addressing this need?
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED = on behalf of
> Jessica M. Brodey
> Sent: Tue 10/10/2006 11:43 PM
> To: 'TEITAC Communications Task Force'
> Subject: Re: [teitac-tools] Calendar
> I agree . . . most of the groups have already begun to
> schedule meetings and many of the conveners do not understand
> either how to use/access the listserve, or the wiki.
> If we want to use other tools for the conference calls, we
> need to be moving quickly. It also sounds as if the access
> board stated that there were no funds available to pay for
> accessibility for the subcommittees, but that somehow we have
> to ensure the accessibility of all subcommittee meetings.
> That is potentially a great concern if there is a significant
> cost involved in making the calls accessible.
> (See attached file: winmail.dat)