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

Fwd: Re: Mistake in "Accessibility Features of CSS" note

From: Jens Meiert <jens.meiert@erde3.com>
Date: Wed, 31 Aug 2005 15:15:01 +0200 (MEST)
To: ij@w3.org, jbrewer@w3.org
Cc: w3c-wai-gl@w3.org
Message-ID: <952.1125494101@www85.gmx.net>

Hi Judy, Ian,


sorry for "top-posting" - is there any new status regarding either the
correction of the mentioned errors (partially, I consider them urgent) and
typos, or a new draft addressing these issues?


 Jens.



--- Weitergeleitete Nachricht ---
Von: "Jens Meiert" <jens.meiert@erde3.com>
An: ij@w3.org, jbrewer@w3.org
Kopie: ivan@w3.org
Betreff: Re: Mistake in "Accessibility Features of CSS" note
Datum: Tue, 14 Dec 2004 22:28:43 +0100 (MET)

Hi Judy, Ian,


beside the first and already mentioned "word-spacing" issue (see attached
mail), there is also another mistake in the "Accessibility Features" note
[1] as well as some typos:

The second mistake I noted is severe but not very spectacular -- if you use
strings in CSS, you need to quote them, so "content: End Example" [2] is
incorrect ("End" and "Example" ain't CSS keywords), but "content: 'End
Example'" is valid.

Typos:

* "before or after and element's content" [2];
* "This properties" [2];
* "See th 'list-style-type'" [2];
* "The following example show" [3].

I hope all of this helps to fix the current note or helps to release a new
revision which contains corrections.


Best regards!
 Jens.


[1] http://www.w3.org/TR/CSS-access
[2] http://www.w3.org/TR/CSS-access#Generated
[3] http://www.w3.org/TR/CSS-access#ACSS



--- Weitergeleitete Nachricht / Forwarded Message ---
Date: Sun, 12 Dec 2004 14:59:13 +0100 (MET)
From: "Jens Meiert" <jens.meiert@erde3.com>
To: ij@w3.org, jbrewer@w3.org
Subject: Mistake in "Accessibility Features of CSS" note

Hi Judy, Ian,


I found a more or less severe mistake in the "Accessibility Features of CSS"
note [1]: In "Spacing, alignment, and positioning" [2] it's written that
"authors may create the same visual effect with the 'word-spacing' property
applied to "HELLO"" -- this is wrong since you need to use 'letter-spacing'
for the desired outcome.

Also, 'letter-spacing' is missing in the introductory enumeration of
properties (same list item). -- Third and though this is optional, I'd also
propose to encourage the use of the 'text-transform' property to achieve an
uppercase "HELLO".

Finally, I suggest the following formulation:

"'text-indent', 'text-align', 'word-spacing', 'letter-spacing',
'font-stretch'. Each of these properties allows users to control spacing
without adding additional spaces. For example instead of writing "h e l l o"
(which users generally recognize as the word "hello" but users of speech
recognition tools would hear as individual letters), authors may create the
same visual effect with the 'letter-spacing' property applied to "hello"."

(Thereby introducing 'letter-spacing' as well, solving the 'word-spacing'
issue and circumnavigating the mentioned 'text-transform' best practice by
using a lowercase "hello".)

Please note that I'll include the 'letter-spacing' correction in the
forthcoming German translation, and that I'll add a translators note that
'text-transform' might be an appropriate measure to pass on an uppercase
"HELLO" which is not unproblematic.

I look forward to any feedback, hopefully including that this will be fixed
in the note, too.


Kind regards,
 Jens.


[1] http://www.w3.org/TR/CSS-access
[2] http://www.w3.org/TR/CSS-access#Positioning


-- 
Jens Meiert
Information Architect

http://meiert.com/

http://uitest.com/ < Reloaded
Received on Wednesday, 31 August 2005 13:15:23 GMT

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