WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Re[2]: Unclosed list tags

for

From: Victoria Hamill
Date: Oct 7, 2004 6:10AM






Thanks all for your help on this. I'll stick to lists, as that seems to be
the most harmless.

In answer to Deryck's question about what DOCTYPE we're using, I wish we
even had one! The site in question is running on Domino 5, which refuses to
produce a doctype at all, so all of our attempts at accessibility are
hindered immediately. Fortunately the latest version of Domino, and thus
our later sites, do generate a DOCTYPE, so at least the future is bright
:-)

Victoria
-----------------------------------------------------
Victoria Hamill
NetInfo
Phone: (44) 1628-687863
Email: <EMAIL REMOVED>
URL: http://www.netinfo.com
- More than meets the eye



"jkorpela"
< <EMAIL REMOVED> .
fi> To
"WebAIM Discussion List"
06/10/2004 21:21
cc

Please respond to Subject
"WebAIM Re: [WebAIM] Re[2]: Unclosed list
Discussion List" tags
<webaim-forum@lis
t.webaim.org>









On Wed, 6 Oct 2004, Jared Smith wrote:

> > but real XHTML won't be suitable for the WWW for years (since IE
> > does not support real XHTML).
>
> Could you please explain why? IE is far from perfect, but it certainly
> seems to support XHTML to me (at least in recent IE versions).

The operative word is "seems".

If you send a document labelled (in HTTP headers) with
Content-Type: application/xhtml+xml
to IE, it will get mad - just start a "Save As" dialogue.

The only way to make IE understand XHTML at all is to mis-label
it as text/html, which means that IE will process it as HTML.
If you are cautious and apply the (in)famous appendix C of the
XHTML 1.0 specification, you might manage to fool IE into treating your
XHTML document the right way.

> It may not
> have the best support for CSS styling of XHTML content, but I don't
> see any cases where true, standards-based XHTML breaks in IE.

_Any_ true XHTML breaks it.

Besides, XHTML 1.0 gives _no_ functional improvement over HTML 4.01.
It's only when you go beyond XHTML 1.0 in the XHTML road when you find
something potentially useful. But then you can't any more fool IE
into processing it as HTML, so it goes into pieces. And this will probably
remain the situation until Longhorn is on the market, and how long will it
take before it gets even 50 % penetration worldwide?

--
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/

----
To subscribe or unsubscribe, visit http://www.webaim.org/discussion/