W3C home > Mailing lists > Public > www-html@w3.org > November 2003

Re: Accessibility in XHTML 2.0 Draft

From: Toby A Inkster <tobyink@goddamn.co.uk>
Date: Sat, 1 Nov 2003 16:19:49 +0000
To: Seth Honeycutt <honeys0521@ncstudent.net>
Cc: www-html@w3.org
Message-ID: <20031101161949.GA18742@ophelia.goddamn.co.uk>
On Fri, Oct 31, 2003 at 02:44:46PM -0500, Seth Honeycutt wrote:
|    code for a section could look something like this:
|    <section   id="sitenav"  title="Site  Navigation"  summary="Navigation
|    links for our website." >
|        <p>
|        </p>
|    </section>
|    The  <section>  element  could  also  be nested to give a hierarchical
|    structure  view to a web page.  

This can already be done using existing XHTML 2 elements <section> and 

For example:

    <p>I like apples because...</p>
    <p>I like pears because...</p>
  <p>I don't like vegetables.</p>

could be condensed by browsers to a menu like this:


Indeed there are already browsers that do this with the existing HTML 
elements <h1> to <h6>. See http://www.dillo.org/

| A  few  extra  things that you might consider is allowing for a header
| and  footer  to  be  declared in the <head> of the document that would
| insert  code  before and after the code in a section when a section is
| displayed  on  a  screen by itself.

This sort of thing is best handled server-side. Some techniques are 
discussed here:


If you do it on the client side it raises all sorts of XML 
well-formedness issues -- must the XHTML be valid before the external 
file is included? Must it be afterwards?

Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?id=132

Received on Saturday, 1 November 2003 11:23:22 UTC

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