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

RE: [#831] Structural emphasis evident really a user agent issue?

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Mon, 21 Jun 2004 17:21:44 -0500
To: "'Michael Cooper'" <michaelc@watchfire.com>, "'WAI GL (E-mail)'" <w3c-wai-gl@w3.org>
Cc: <w3c-wai-ua@w3.org>
Message-ID: <auto-000002140765@spamarrest.com>

I like any removal of guidelines or success criteria where we can.

I think the idea here was that, given that most people can't figure out how
to change style sheets.  So styles should be such that they would show up
even if a display is set to low resolution.    This was not originally meant
to say (on low fidelity displays) though it has been edited into this.
Originally I believe, it was meant to make formatting obvious enough that
people with low vision could see it.  the low resolution test was just a
means for determining this.  

That said, we should look at whether this is A)important and B) effective
solution.

Because it is level 3 the importance doesn't need to be sky high.  But every
SC we add weakens the others so it should be important -- and of course
effective.

 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Michael Cooper
Sent: Monday, June 21, 2004 3:07 PM
To: WAI GL (E-mail)
Cc: 'w3c-wai-ua@w3.org'
Subject: [#831] Structural emphasis evident really a user agent issue?


While mapping HTML techniques to the guidelines, I tried to think what
technique
I would create for the fifth Level 3 success criterion of 2.4 [1]. This
requires
that structural markup be evident on low-fidelity displays. I could not
think of
any HTML techniques that could guarantee compliance with this requirement;
furthermore it seems that if you follow requirements to use structural
markup
properly this issue should take care of itself. The user agent should make
structural markup evident, that's why we require it. 

So I think this is not a _content_ requirement and should be removed from
WCAG.
It is a user agent requirement, and the UA group should determine how to
handle
it. I propose we remove this success criterion from WCAG.

[1]
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20040602.html#navigation-mechanism
s-distinct-display-types

--- Signature ---

Michael Cooper
Accessibility Product Manager, Watchfire
1 Hines Rd Suite 200, Kanata, ON  K2K 3C7  Canada
Tel: +1 (613) 599-3888 x4019
Fax: +1 (613) 599-4661
Email: michaelc@watchfire.com
Web: http://www.watchfire.com/
Received on Monday, 21 June 2004 18:22:03 GMT

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