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

RE: Conveying metadata unobtrusively in HTML

From: Harry Woodrow <harrry@email.com>
Date: Mon, 3 Jun 2002 11:18:36 +0800
To: "Nick Kew" <nick@webthing.com>, <w3c-wai-ig@w3.org>
Message-ID: <LDEMKFBKJGCANBEJGEOIMEHCCEAA.harrry@email.com>

Of course if you use colour to indicate information you are excluding not
just those who cannot see the site but also the many that have
colour-blindness.  Any use of title or similar artificial constructs are
unlikely to assist them.


Harry Woodrow

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On
Behalf Of Nick Kew
Sent: Monday, 3 June 2002 6:10 AM
To: w3c-wai-ig@w3.org
Subject: Conveying metadata unobtrusively in HTML




Colour - and other visual styling - is a great tool for conveying
information.  For example, if we are evaluating something, we may
use red to highlight an error, amber for a warning, and green for OK.
But of course, that raises the obvious accessibility issue for the
visually impaired.

In Page Valet, visual information is duplicated in text: in particular,
accessibility messages are prefixed with, for example, "WCAG2/High"
to indicate a WCAG level 2 checkpoint that we have diagnosed with
a high level of certainty.  This is visually obtrusive, and I don't
really like it.

Another option I'm playing with is to abuse the "title" attribute
for this kind of thing.  The logic is that this becomes unobtrusive
for visual users, but accessible to non-visual devices.  It's not
really right: technically there isn't a better mechanism in HTML,
but an equivalent scripting solution is likely to be horribly
long-winded and less well supported by assistive devices.

I have a new service in preparation, and have just opened the first
preview prototype at <URL:http://valet.webthing.com:8000/html-form.html>.
This uses the title technique to highlight whether an attribute is
valid, deprecated or bogus, duplicating visual information conveyed
by colour.

Comments please: is this technique a reasonable approach to the problem?
Can anyone suggest a better approach?


--
Nick Kew

Available for contract work - Programming, Unix, Networking, Markup, etc.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.368 / Virus Database: 204 - Release Date: 29/05/2002

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.368 / Virus Database: 204 - Release Date: 29/05/2002
Received on Sunday, 2 June 2002 23:19:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:04 GMT