Thread Subject: Re: Authoring tools with no user interface

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, Aug 08 2007 2:10 PM

Andrew / Sean,

I had brought up this same issue on June 7 when I wrote:

"Is "For authoring tools with a user interface, ", required? For user driven

authoring tools, a user interface is certainly needed and if it is an

automated authoring tool, it should provide a programmable switch or

parameter by which one can turn on / off this mode. So I think it

should simply read:

4. Authoring tools must provide a mode which prompts authors to create

accessible content."



In other words some trigger or interface with a human is needed somewhere
in the process to generate content.

Refer:

http://teitac.org/mailarchives/mail_thread.php?thread=1172&id=4989#post8

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 =

_____

From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Hayes
Sent: Wednesday, August 08, 2007 3:07 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Authoring tools with no user interface



Well I guess that speaks to my concern that the definition includes all
software. Typically one would not think of information typed into the shell
as part of the definition of an authoring tool suite.



Sean Hayes
Incubation Lab
Accessibility Business Unit
Microsoft
Phone:
mob +44 7977 455002
office +44 117 9719730



From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: 08 August 2007 19:58
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Authoring tools with no user interface



How was the information that the sed, awk, perl script obtained? That
information's creation pathway would include other software that is part of
the overall "authoring tool"

AWK




_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Hayes
Sent: Wednesday, August 08, 2007 2:52 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Authoring tools with no user interface

The language was intended to exclude a number of tools such as sed, awk,
perl which modify content but often run silently as part of batch
operations



Sean Hayes
Incubation Lab
Accessibility Business Unit
Microsoft
Phone:
mob +44 7977 455002
office +44 117 9719730



From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: 08 August 2007 19:41
To: TEITAC Web/Software Subcommittee
Subject: [teitac-websoftware] Authoring tools with no user interface



Can anyone name an authoring tool with no user interface? To be specific,
if an authoring tool is "any software, or collection of software components,
that authors use to create or modify content for publication" there seems to
be a need for a user interface in one or more of the tools that are part of
every "authoring tool". Any thoughts?

AWK



Andrew Kirkpatrick

Corporate Accessibility Engineering Manager

Adobe Systems

= EMAIL ADDRESS REMOVED =

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University