W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2003

Re: [techs] New draft: CSS Techniques for WCAG 2.0 (A & R Units)

From: Geoff Deering <gdeering@acslink.net.au>
Date: Thu, 25 Dec 2003 13:22:15 +1100
Message-ID: <3FEA49D7.9070902@acslink.net.au>
To: Jens Meiert <jens.meiert@erde3.com>
Cc: w3c-wai-gl@w3.org

Jens Meiert wrote:

>>New draft of CSS Techniques for WCAG 2.0 available for discussion [1].
>>    
>>
>
>Roughly scanned the Techniques document, but there are at least three issues
>I found worth to announce here... First, in 'Formatting and positioning of
>text' [2] there is a todo item called '@@example showing use of
>"word-spacing"', but you mean 'letter-spacing', I guess. Two ready-to-use examples are
>
>    <span style="letter-spacing: 5px;">HELLO</span>
>    <span style="letter-spacing: 5px; text-transform:
>uppercase;">hello</span>
>
>  
>

What is the Accessibility / Usability rule of thumb for using absolute 
and relative units?  Can someone please point me to a very good 
explanation to this (with examples), because it seems to me that 
something like the above example is much better being addressed in 
relative units (maybe I'm wrong). 

I use relative as much as possible.  For what cases should absolute be 
used in place of relative?   In the case of this CSS Tech doc, which 
encourages absolute for margins, in pixels, does that only apply to 
media for screen only?  What do you do for handhelds, etc.  Doesn't 
there need to be a distinction here?  What is wrong with

BODY { margin-left: 0.5em; margin-right: 0.5em}

instead of 

BODY { margin-left: 15px; margin-right: 15px}

Isn't the relative one more flexible for user and device?

Regards
Geoff Deering
Received on Wednesday, 24 December 2003 21:23:04 GMT

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