W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2000

Re: "to urge, suggest or dictate"

From: Frederick J. Barnett <fred@eatel.net>
Date: Wed, 24 May 2000 15:46:44 -0500
To: w3c-wai-au@w3.org
Message-ID: <392BF964.29434.F88B40@localhost>
On stardate 24 May 2000, Jutta Treviranus sent a subspace communication stating:

> Towards a better definition of "prompt" the following is my reading 
> of where the group is at with respect to the issues regarding 
> "prompt:"
> 
> We have general agreement that:
> - the use of the word prompt in the guidelines does not refer to the 
> narrow definition of a "prompt" as defined in several software 
> guidelines, rather it is used as a verb with the Oxford dictionary 
> meaning of "To urge, suggest, or dictate (a thing); to inspire, give 
> rise to (thought, action)."

	Agreed.

> - the form and timing of the prompt can be user configurable

	Agreed.

> - equivalent text deserves special support within the authoring tool, 
> because it can involve the greatest amount of work for the author, 
> and because of it's importance within WCAG, therefore we want to do 
> more than what is encompassed within guidelines 4 and 5. We want to 
> do more than check, repair and provide help. We also don't want to 
> depend upon the author to seek out support. The additional support or 
> prompting should be initiated by the tool if a problem is detected, 
> not requested by the author.
>
	That depends on when the "problem is detected." Every time an image is 
inserted into an MS Word document, no. When that document is saved as HTML, 
yes. Note that I'm reading this part to mean a dialog box will pop up each time 
an image is inserted. Something like the blue squiggly line wouldn't be any 
problem, but it would depend on the author to check why it's there. So I don't 
think that fits what you wrote.

> Beyond the implementation details the sticking points we can't reach 
> agreement on are:
> - whether the prompt requires author response or requests author response

	I have to go with request on this one.

> - whether the prompt must occur within the same authoring session

	Again, that depends on what you're writing. I would lean towards no.

> - whether the prompting must be on by default
> 
	I do believe accessibility features should be on be default. Lots of people 
start using a program with out even reading the manual or help file first, an 
so might not even know they're there. Also, I feel on by default helps to show 
how important accessibility is.

> The general goal of the guideline is to:
> - encourage, urge and support the author in creating meaningful 
> equivalent text without causing frustration that may cause the author 
> to turn off access options
> - cause a positive disposition and awareness on the part of the 
> author toward accessible authoring practices.
> 
	Agreed.


Frederick J. Barnett                  http://www.eatel.net/~fred/
E-mail: fred@eatel.net
Member: HWG Governing Board & Assistant Secretary
http://www.hwg.org/
Received on Wednesday, 24 May 2000 16:48:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:44 UTC