W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2010

Re: summarization information delivery options: attribute or element

From: Gez Lemon <g.lemon@webprofession.com>
Date: Fri, 26 Feb 2010 10:44:34 +0000
Message-ID: <e2a28a921002260244u2b966868k6557cbc992e12e22@mail.gmail.com>
To: Joshue O Connor <joshue.oconnor@cfit.ie>
Cc: "Gregory J. Rosmaita" <oedipus@hicom.net>, public-html-a11y@w3.org
Hi Josh,

On 26 February 2010 10:33, Joshue O Connor <joshue.oconnor@cfit.ie> wrote:
> Finally, as I know that we (sic) have all done a lot of advocacy work to
> argue for the retention of @summary, to be clear, I think @summary is
> great for the audience that it was designed to serve (blind users), and
> I would hope for the sake of backwards compatibility within HTML5 that
> its use would still be considered valid /but/ we do need a richer more
> capable element to future proof this functionality and potentially
> extend this usefulness to other user groups.

My issue with this is that by addressing the needs of all user groups,
the group that summary was originally intended for will be left out. I
can't imagine many authors writing a long description that contains
things that visually obvious. I don't see the purpose of introducing a
new element to do something that can already be done.



Supplement your vitamins
Received on Friday, 26 February 2010 10:45:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:09 UTC