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

Re: Proposed list of predefined class names (was: Re: Getting beyond the ping pong match)

From: Matthew Ratzloff <matt@builtfromsource.com>
Date: Sat, 5 May 2007 09:48:01 -0700 (PDT)
Message-ID: <1201.>
To: "public-html@w3.org" <public-html@w3.org>

I'm in agreement that these should NOT be pre-defined classes, but
something akin to "role".  I like your ideas for uses.

For "error", screen readers could have an option to read <error> messages
before anything else on the screen.

For the search, I can see the option being to both jump to the search
element and also indicate it in some way (flashing the input field, for
example).  Of course, many sites have multiple search fields, so maybe
such a button could iterate over them.

These buttons could be included on an optional browser "standard site
navigation" menu (either built in, or available as a plugin), where the
buttons on context-sensitive and display if the corresponding "role"
attributes are found on the page.  By that I mean something like:

Return to top | Jump to search | Jump to errors (3 found)


On Sat, May 5, 2007 6:18 am, Rene Saarsoo wrote:
> I don't think it is a bad list. Many of them seem quite
> useful to me.
> copyright:
> A screen reader user could easily skip to the copyright
> information of the article he is reading.
> error and warning:
> Non-CSS-aware browsers like Lynx could display errors and
> warnings in distinctive way (e.g. in red).
> search:
> A browser could implement a shortcut for jump-to-search.
> example, note and issue:
> Without CSS it might be otherwise quite hard to tell, where
> a group of example paragraphs end and normal content starts.
> The same with "note" and "issue", although I'm not quite sure,
> should the "issue" really be included into that list - doesn't
> seem such a common use-case to me.
Received on Saturday, 5 May 2007 16:48:07 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:20 UTC