Thread Subject: Re: "Content" in our subcommittee
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: Mon, Nov 06 2006 3:56 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jim Tobias: "Re: "Content" in our subcommittee"
- Previous message in thread: Andrew Kirkpatrick: "Re: "Content" in our subcommittee"
- Messages sorted by: Author | Thread | Date
>Let me propose that we consider the following requirements for industry of
content-producing software tools:
> 1. The tool itself should be accessible to operate. (This would apply to
all software, not just content-producing software).
This is really needed. it will make companies regard authoring tools
accessibility guidelines (ATAG) more seriously.
>2. The content produced by the tool should be able to support all the
relevant features for accessible content.
>And the following requirement should apply to the federal entity producing
> 3. The content should contain all the relevant features for accessible
How can this be part of the S508 standards. it is upto the user how the tool
is used and cannot be part of procurement precondition.
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: Jim Tobias: "Re: "Content" in our subcommittee"
- Previous message in Thread: Andrew Kirkpatrick: "Re: "Content" in our subcommittee"