Thread Subject: Re: Authoring Tools
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: Judy Brewer
Date: Wed, Apr 18 2007 12:25 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Hoffman, Allen: "Re: Authoring Tools"
- Messages sorted by: Author | Thread | Date
At 03:12 PM 4/17/2007 -0400, Hoffman, Allen wrote:
>These all sound like great ideas, lets consider them, however, from a
>more open "authoring tool" perspective than "web authoring" perspective
>as the WAI is rightfully doing. I don't think we really want to
>advocate for more than a single authoring tool provision that applies to
>web, then to other things. I could be wrong but i doubt we'll get
>multiple authoring tool provisions for various types figured out.
If provisions have been developed that address production of accessible
content by Web authoring tools, wouldn't using those at least help support
the production of accessible Web content?
If we can also figure out provisions -- even on a general level -- that
support production of other kinds of accessible content, then good; but why
forego resources that we have available for Web authoring?
P.S. I've been trying for 5 minutes to dial into the Web conference for
today, and the passcode does not seem to be working...
>Let me try and rephrase what i read in these concepts, and maybe we can
>fill in what I am missing.
>1. Authoring tools (or interoperable components) shall provide the
>capacity to programmatically prompt authors for alternative accessible
>attributes of content elements including tables, form fields, graphics,
>2. When authoring tools or interoperable components provide content
>templates , fully accessible selections shall be available for authors
>3. Authoring tools or interoperable components shall identify formats
>which meet minimum accessibility format requirements when such format
>selections are available to the end-user during file selection or save
>file format selections.
>Allen Hoffman -- 202-447-0303
>From: = EMAIL ADDRESS REMOVED =
>[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
>Sent: Tuesday, April 17, 2007 2:39 PM
>To: = EMAIL ADDRESS REMOVED =
>Subject: Re: [teitac-websoftware] Authoring Tools
>Some thoughts from Katie on authoring tool features from ATAG  that
>would facilitate the creation of accessible content:
>1. User prompts for accessible alternatives 2. User prompts for
>accessible document/content types (on save?)] 3. Providing a myraid of
>accessible-only CSS (XSLT, or whatever) pre-authored (pre-loaded)
>stylesheets for authors to be prompted to choose from.
>4. Providing a myraid of accessible-only tables, frames, skip navs, etc.
>for authors to be prompted to choose from (when choosing to include
>items) in their content.
>We should consider these in our discussion around authoring tools.,
> W3C WAI Authoring Tools Accessibility Guidelines
- Next message in Thread: None
- Previous message in Thread: Hoffman, Allen: "Re: Authoring Tools"