Thread Subject: Re: Authoring tools with no user interface
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: Robinson, Norman B - Washington, DC
Date: Thu, Aug 09 2007 8:40 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Sean Hayes: "Re: Authoring tools with no user interface"
- Previous message in thread: David Poehlman: "Re: Authoring tools with no user interface"
- Messages sorted by: Author | Thread | Date
We should remove the qualifiers "for each accessible content format
supported" as all content covers all scenarios, "with a user interface"
as then you have to qualify what a user interface is or is not, and
delete the reference to _file_ templates entirely. Templates are not
software. A templated HTML form is not software or web-based information
- yet(1 see below). We should certainly expect vendors to provide file
templates that already include accessibility information where possible
but we should be focusing on their _tool's_ ability to create and keep
that information, not on the _file_ itself. Please consider that I can
use many different editors on the same file template - and do today. And
where my coworkers prefer Dreamweaver or some other tool, I prefer BASH
shell script editing or VIM text editor (let the flame wars begin) that
has macros for many of the same functions and in our current definition
would fit the definition of an authoring tool.
Norman B. Robinson
Section 508 Coordinator
IT Governance, US Postal Service
(1) We should address file formats as file formats and not some
umbrella for web-based information. We haven't even gained agreement
amongst ourselves and addressed valid or well-formed HTML! That
logically will fall into software (flash anyone? SVG? PDF?) at some
point. We should focus on what specific techniques or coding is required
for accessibility in the file format in consideration of where we are
failing to provide accessibility and need it mandated (e.g., being
specific on alt text for images is an obvious need; how do we clarify
that for SVG or any other format?)
- Next message in Thread: Sean Hayes: "Re: Authoring tools with no user interface"
- Previous message in Thread: David Poehlman: "Re: Authoring tools with no user interface"