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: Al Gilman <Alfred.S.Gilman@IEEE.org>
Date: Mon, 21 Jun 2004 16:43:02 -0400
Message-Id: <p06110408bcfcf6297d84@[10.0.1.2]>
To: "WAI GL (E-mail)" <w3c-wai-gl@w3.org>
Cc: <w3c-wai-ua@w3.org>

At 10:21 PM +0200 6/21/04, Roberto Scano - IWA/HWG wrote:
>Agree... this is User Agent Issue.

Are stylesheets cited in LINKs in the HTML and served from the server
'content'? Are they within the domain of the WCAG?

WHILE the WCAG is in deep trouble trying to create a normative, testable,
Recommendation for Universal Content at the user-experience level (independent
of the formats used), the criterion set out is, at the user-experience level,
valid.

As the horizion in view in the viewport shrinks, the presentation of structural
signs should adapt.

Both the User Agent and the stylesheet writer have, in the current state
of practice on the Web, an opportunity to do something about this.  Also
the adaptation server in a "Device Independence" setup.

Those with a need for strenuous accomodation will usually want to ignore the
presentation hints from the server.  But the crossover point is not clear
at this time.  I would suggest it is premature to rule the stylesheet and the
server-side content adaptor out of this game.

Media queries in CSS3 are specifically targeted at providing this sort of
adaptation for commercial reasons.  It would be odd if we did not work with
CSS to come up with techniques that show how this dollar-demanded capability
can be turned to the benefit of people with disabilities accessing the Web.

Al

>----- Original Message -----
>From: "Michael Cooper" <michaelc@watchfire.com>
>To: "WAI GL (E-mail)" <w3c-wai-gl@w3.org>
>Cc: <w3c-wai-ua@w3.org>
>Sent: Monday, June 21, 2004 10:06 PM
>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 17:30:39 GMT

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