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

Re: Wording issues

From: Al Gilman <asgilman@iamdigex.net>
Date: Thu, 16 Aug 2001 12:15:22 -0400
Message-Id: <Version.32.20010815233254.040f7150@pop.iamdigex.net>
Message-Id: <Version.32.20010815233254.040f7150@pop.iamdigex.net>
To: w3c-wai-gl@w3.org
At 11:01 PM 2001-08-15 , Jason White wrote:
> > 
> > >           + [47]Checkpoint 3.3 Write as clearly and simply as is
possible
> > >             and appropriate for the site's content.
> > 
> > Or:
> > 
> > Write as clearly and simply as possible
> > in a way that is appropriate for the site's content.
> > 
> > You'll spend the rest of your lives arguing over whether or not 
> > "appropriate" is an adverb (indicative of the level of help WCAG 
> > needs with writing). This way there is no such debate.
>The suggested alternative only makes the sentence harder to interpret
> > and resolves no ambiguity.

The original is still hard to read right.  

A likely expectation at the point where you leave 'possible' <br> and hit
'and'
is to expect a compound predicate or compound sentence, but not to be ready
for
a compound object of the preposition 'as.'

The proposed alternate does not substantially eliminate this problem.  It
still
takes two takes to get "in a way" associated with "as possible" and not
"Write..."

Consider the following other variations:

- Write as clearly and as simply as you can, without misrepresenting the
site's
content. 

- Write in the clearest and simplest language that is still consistent with
the
site's content.

- While remaining faithful to the site's content, write as clearly and simply
as you can.

- Write as clearly and simply as you can while remaining faithful to the
site's
content.

There is a conflict between the wish to front-load a simple imperative and the
fact that this rule involves the interaction of two clauses, one a 'satisfy
constraint' clause and the other an 'optimize quality' clause.

Al 
Received on Thursday, 16 August 2001 11:57:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:11 GMT