Thread Subject: Re: teitac-websoftware Digest, Vol 2, Issue 4
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: Langum, Michael J
Date: Wed, Nov 01 2006 12:30 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jim Tobias: "Re: teitac-websoftware Digest, Vol 2, Issue 4"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
I've been lurking in the woods following this thread.
You've all made a lot of good comments and suggestions. Here is my
1. I think it might be useful to borrow the concept of "Authoring Tool."
This would mean any application (Word Processor, Spreadsheet, Flow-chart
app., etc.) used to create any content consumed by a human being. Of
course, the Authoring Tools themselves would need to be accessible as
well as their output.
2. This group (or some other standards group), needs to start putting
together guidelines for such tools, just as W3C has done. This will be
a long process, but it would be a good idea to start now, so that the
Application producers can begin to add needed functionality to their
3. MOST IMPORTANT! There will never be a substitute for training of
content creators on the "how-to" of creating accessible content. There
is not a purely technical "fix." Until clever Authoring Tools exist
that will do an "access check/repair," the only option will be old
fashioned training. Maybe each organization should provide at least
basic training on how to produce accessible content (e.g. correct use of
headers, tables, images, etc.)
- Next message in Thread: Jim Tobias: "Re: teitac-websoftware Digest, Vol 2, Issue 4"
- Previous message in Thread: None