Thread Subject: Re: Acquisition ofsoftwaretools and 508 compliance
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: Hoffman, Allen
Date: Wed, Mar 07 2007 9:15 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: William Loughborough: "Re: Acquisition ofsoftwaretools and 508 compliance"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
I am not following this thinking clearly.
software is covered by Section 508 technical standards, which includes
authoring tools, ditto for web.
How is it outside scope to require specific functionality? authoring
tools are implicit to success in other content being presented via EIT,
so must allow the user to perform certain functions.
I think as a advisory committee we need to recommend such changes and
leave it up to the follow on activities to resolve such questions as
scope when it may be borderline.
Interested in understanding the logic here however.
Allen Hoffman -- 202-447-0303
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of William
Sent: Wednesday, March 07, 2007 10:50 AM
To: TEITAC General Interface Accessibility Subcommittee;
= EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-websoftware] [teitac-general] Acquisition of
softwaretools and 508 compliance
Truesdell Nick wrote:
> This [making acquisition guidelines cover authoring tools] would
without question be something that could be beneficial. It may, however,
be outside of the scope of 508 to actually require this.
Let me put it another way: the process of preparing accessible Web
materials for all practical purposes DEMANDS the use of such software
tools as Content Management Systems, XML/HTML/CSS/XSLT editors,
evaluation/report methods, etc. That such tools, an inherent part of the
accessibility production procedure, might not be a part of the process
is unthinkable. That is; there is no question that they must be
accessible to (usable by) PWD (Persons With Disabilities). Also it would
make no sense whatsoever if they produced inaccessible product.
Therefore the FAR (Federal Acquisition Regulations) clearly require that
such tools be a part of the overall panoply of "needful things" when it
comes to providing accessible Web materials.
- Next message in Thread: William Loughborough: "Re: Acquisition ofsoftwaretools and 508 compliance"
- Previous message in Thread: None