Thread Subject: Re: Authoring Tools
Note
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: Sailesh Panchang
Date: Wed, Apr 11 2007 10:50 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Hoffman, Allen: "Re: Authoring Tools"
- Previous message in thread: Truesdell Nick: "Re: Authoring Tools"
- Messages sorted by: Author | Thread | Date
Nick asked:
"On a note of enforceability if a provision is going to require a
particular tool to provide access to a set of functions/attributes
dubbed accessibility features then would it also be necessary to
quantify these specific features in addition? If so then where would
this be?"
It would be the author's responsibility to be aware of the accessibility
features of the encoding mechanism being employed. The authoring tool for
HTML for instance should allow the author to set an alt or longdesc for an
IMG or a LABEL for an INPUT control or SCOPE for a table cell. If it does
not, it is a weakness in the tool. But knowing when to use alt and when to
use longdesc is primarily the author's duty. One might reasonably expect the
tool to list the accessibility features supported and describe how one might
be able to use them through the particular tool. This is important for
Procurement. The documentation for the content format would be the place to
review what various accessibility features are and how and when they are to
be used.
Thanks,
Sailesh Panchang
Senior Accessibility Engineer
Deque Systems Inc. (www.deque.com)
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)
E-mail: = EMAIL ADDRESS REMOVED =
- Next message in Thread: Hoffman, Allen: "Re: Authoring Tools"
- Previous message in Thread: Truesdell Nick: "Re: Authoring Tools"
WebAIM is an initiative of:
