W3C home > Mailing lists > Public > public-html@w3.org > June 2007

RE: the market hasn't spoken - it hasn't bothered to listened [was Re: fear of "invisible metadata"]

From: Alastair Campbell <ac@nomensa.com>
Date: Thu, 28 Jun 2007 00:09:08 +0100
Message-ID: <DBE13196215CF743A3F921EBB877264A14E83A@saturn.intranet.nomensa.com>
To: "Henri Sivonen" <hsivonen@iki.fi>
Cc: "John Foliot" <foliot@wats.ca>, "Gregory J.Rosmaita" <oedipus@hicom.net>, "HTML WG" <public-html@w3.org>, <wai-xtech@w3.org>, <w3c-wai-ig@w3.org>, "Aaron Leventhal" <aaronlev@moonset.net>

Henri Sivonen wrote: 
> "I agree that HTML5 will need to have role='' and headers='' as short-

> term measures and as overrides for handling corner cases when easier- 
> to-author methods fail. It is rather pointless to make non-conforming

> something that Firefox and JAWS already support.
>
> However, I think they should be presented as short-term measures and  
> as overrides when other ways fail instead of being presented as  
> primary way of making HTML accessible on the long term. And the HTML  
> WG should seriously consider the long term."

Hi Henri,

If that is the direction of the WG, that sounds great.

One thing I'd point out though, is that accessibility use-cases
shouldn't necessarily be dropped due to (some of them) being edge cases.


Taking the organisational point of view, certain large organisations
(e.g. government departments) have to produce accessible content across
the board.
Sometimes these organisations have to produce certain content, such as
complex tables that have to look a certain way that (I don't think)
could be covered by the simpler mechanisms proposed.

I don't want to bring in the tables headers issue in here, but just use
it as an example illustrating that sometimes there are edge cases that
should be covered that may require extra effort by authors. For those
relatively rare cases where they need to produce a complex table,
application or whatever, they can put in the extra effort and make it
accessible. (E.g. we occasionally get asked to make annual reports and
similar documents into accessible PDFs.)

So long as the basic mechanisms work for the majority, that's fine, just
don't rule out the (accessibility) edge cases based on numbers, or
necessarily how difficult they are (although easier is always better).
If HTML5 can't support those edge cases, it will push organisations to
other formats.

Kind regards,

-Alastair

--
Alastair Campbell         |  Director of User Experience

Nomensa Email Disclaimer:
http://www.nomensa.com/email-disclaimer.html
Received on Thursday, 28 June 2007 08:16:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:46 UTC