W3C home > Mailing lists > Public > public-diselect-editors@w3.org > April to June 2005

WAI PF last call comment

From: Al Gilman <Alfred.S.Gilman@IEEE.org>
Date: Wed, 8 Jun 2005 15:26:47 -0400
Message-Id: <p0611040cbeccf175cfe5@[10.0.1.2]>
To: public-diselect-editors@w3.org
Cc: wai-liaison@w3.org

<comment
class="lastCall workingGroup">
<note
class="inTransmittal">
This comment roughly reflects the sense of the working group. Don't
read too closely; we hope you get the idea. As always we would be
glad to meet with you if you find room for clarification.

Al
/chair, Protocols and Formats WG
</note>

Rotan once put it very succinctly:

To adapt properly, we have to consider information about the content,
the delivery device and the user.

The information about all these three topics come from different
sources. So we struggle to get the information in interoperable terms.

The basic comment is that the decision process as a matter of
comparing content information on the one hand with device and user
information on the other does not leap off the page in this spec.

It matters very much to accessibility that this technology work that
way and that authors learn to use it that way.

So:

1. Please confirm that the full delivery context information space, and
properties of entities in the current host-language document can
be used inside the guard expressions that provide the values of
'expr' and 'when' attributes.

2. Please write the examples to model best practice.

In particular:

When setting 'class' attributes, set semantic values, not
presentation-effect-soundalike values [1]. Use Attribute Value
Templates to insert tokens into the list in the 'class' attribute
value, don't set the value and obliterate pre-existing information.

Examples should favor using content properties in these expressions
rather than just literal thresholds compared with delivery context
properties. The 'metadata for content adaptation' workshop [2] may
suggest common and educative examples of content properties to touch
on. Also the IMS Accessibility Profile [3].

Exemplify the full visibility of the expression space; do not only or
over-use the convenience functions.

Some examples should use delivery-context properties that reflect
user preferences or settings as opposed to just hardware properties.
See the IMS profile for good choices.

<references>

[1] http://tantek.com/log/2004/07.html#classmeaningnotshow

[2] http://www.w3.org/2004/06/DI-MCA-WS/

[3] http://www.imsglobal.org/accessibility/

</references>
</comment>
Received on Wednesday, 8 June 2005 19:51:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:10 GMT