W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2006

Re: Work via the list: role of authoring tools

From: Harvey Bingham <hbingham@acm.org>
Date: Sat, 08 Jul 2006 21:25:57 -0400
Message-Id: <7.0.1.0.2.20060708114545.0282e410@acm.org>
To: <w3c-wai-eo@w3.org>

At 03:34 PM 7/7/2006, you wrote:

>EOWG:
>
>Please continue brainstorming and discussing the questions below on 
>this EOWG list.
>
>Draft minutes from today's teleconference are at:
>         http://www.w3.org/2006/07/07-eo-minutes.html#item03
>
>Thanks!
>~Shawn
>
>
>-------- Original Message --------
>Subject: role of authoring tools [Fwd: EOWG: Agenda for 7 July 2006 
>Teleconference]
>Date: Thu, 06 Jul 2006 22:36:42 -0500
>From: Shawn Henry <shawn@w3.org>
>To: EOWG (E-mail) <w3c-wai-eo@w3.org>
>
><from agenda:>
>3. Messaging the importance of authoring tools
>* Discuss strengthening the "messaging" through metaphor(s) and 
>examples(s),  especially as it fits in with potential outreach 
>campaigns and slide sets
></end from agenda>
>
>EOWG,
>
>Questions for input via e-mail and discussion via teleconference:
>
>1. Examples of authoring tools role -- especially simple, easy to 
>understand examples that are powerful
>1.a. What do authoring tools do now to help develop accessible 
>content (e.g., when insert an image, open dialog box for alt text)?
>1.b. What do authoring tools do now that hinder the development of 
>accessible content?

Microsoft Word 2002.  Need to save as text to avoid embedded 
formatting junk, then
fairly easily I can add appropriate accessible markup.

Microsoft Excel 2002  Cannot save in XML because workspace does not 
contain any
workspace mappings.

"My product key is invalid, you will need to enter a new one to use 
this software."

I"m not about to upgrade, given my frustration with their general 
lip-service to accessibility.

At least that transfers me to an alternative:

http://cita.rehab.uiuc.edu/software/office/

Univ. of Illinois U-C DRES


>1.c. What else could authoring tools reasonably do to significantly 
>improve the development of accessible content -- especially things 
>that would be fairly easy for authoring tools to do that would save 
>developers/authors a lot of work?

Include an "accessibility check" option.

My preference would be link that to the WAI tools so the authors 
could find out what to expect
from any particular tool, and be aware of the extensive list of 
available tools.

>2. Metaphors for:
>2.a. A few 100 authoring tool vendors spending some effort to 
>improve their tools, to help a few *million* developers/authors 
>develop accessible content easier and quicker.

>2.b. Improving authoring tools could make a huge difference in Web 
>accessibility. (perhaps something like: "change the course of 
>history"; or a little rudder changing the course of a large ship, a 
>little bit controlling a horse, a little spark starting a huge 
>forest fire[1]...)
>
>3. Stats (for 2.a.)
>- Rough idea of the number of authoring tools today?

I doubt there are even 100 "serious" authoring tool developers/vendors.

>- rough idea on the number of people developing Web pages?

Thousands.


>Remember that authoring tools include content management systems 
>(CMS), blog software, and many other types, including those listed at:
>         http://www.w3.org/WAI/intro/atag.php#for
>
>Please send comments to the list in addition to discussion at the 
>teleconference.
>
>Thanks!
>~ Shawn
>
>[1] idea from the Bible, James 3:3-5
>
Received on Sunday, 9 July 2006 01:26:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:54 UTC