Re: [orca-list] Text after <a /> is presented as a link

[Steve Holmes <steve holmes88 gmail com>]

I'm finding this conversation increasingly interesting.  I've
undertaken a course of personal study of HTML/XHTML and PHP and was
leaning towards XHTML.  I thought XHTML was the up and coming way to
go.  I actually prefer XHTML because of its tighter structure and
adherence to consistency.  I still would like to continue to code any
future web content with XHTML structure.  I would only supply the
XMLNS parameter on the top line and not bother with the <!DOCTYP
entry.

On Fri, Sep 03, 2010 at 02:16:14PM +0200, Mallory van Achterberg wrote:
> Hi Marcus,
> Re the meta tag: with that alone, you cannot set the MIME type for 
> the page. User agents can and will ignore meta tags and let the
> server override with HTTP Headers (this is also true with the charset).  
> If you really want the page to be XHTML, you'll have to set it that way 
> on the server or with HTTP Headers.  
> However, be aware this means Internet Explorer will not display the page, but
> will ask the user to either download it or open in another application
> (because while it understands XML, it does not recognise XHTML correctly).
> I don't remember if Internet Explorer 9 was going to change this, but
> so far it seems it won't.
>
> For this reason, I've stopped writing any new pages in XHTML, and just
> stick to HTML4.01 Strict.  If you want stricter validation from the
> w3c validator (validator.w3.org), you can tell it to pretend the page is 
> XHTML1.0 Strict and get useful error messages there.  This is what I use
> to catch errors like my bad closing anchor tags as I couldn't for the
> life of me figure out what the heck Firefox was doing <smile>.
>
> Also, if your named anchor is supposed to be a destination for a skip link,
> I've discovered a few browsers won't move the focus there with the anchor
> the way you've got it written.  Internet Explorer 8 seems to want an href
> attribute (I set mine to the same as the skip link's to avoid problems), 
> whle Opera requires there is text content inside the anchor (but that content
> can be a single space character, which works for me).
>
> If Orca worked with webkit browsers, it would be interesting to see what
> it did in the face of such an HTML error...
>
> Greets,
> Mallory 
>
> On Fri, Sep 03, 2010 at 12:36:55PM +0200, Marcus Habermehl wrote:
> > Am 03.09.2010 08:57, schrieb Mallory van Achterberg:
> >
> > > The HTML code in that site is poorly and incorrectly written.  First,
> > > while a construct such as <div/> might be considered valid XHTML (or
> > > valid XML), this is only true if the document is sent as XHTML 
> > > (application xhtml+xml for MIME type), which this page tries (with the
> > > content meta tag) but fails (server is sending it out as text/html, which
> > > is the only reason why this page actually works in Internet Explorer).
> >
> > The meta tag content-type was written 2 times into the header. The first
> > one with text/html and the second one with application/xhtml+xml.
> >
> > > Since the page is really text/html, this  means the browser interprets the 
> > > code as bad "tag soup" HTML.  According to the W3C specs, anchors are
> > > not EMPTY elements like IMG and BR. Also, "name" attributes have been
> > > deprecated for anchors in XHTML.  So whoever wrote this page wrote
> > > it wrong and it's confusing poor stupid Firefox.  Orca can't be 
> > > blamed.
> >
> > I must be blamed. I have written this page and stoled the empty anchor
> > tag by an other page. After changing this <a ... /> to <a>...</a> the
> > page is correct presented.
> >
> > > Strangely enough, JAWS does not consider it a link in Firefox.  Does Orca
> > > read "generated" source while JAWS reads straight source?
> >
> > Because the page was correct presented by JAWS, I was thinking it's a
> > at-spi/GAIL problem.
> >
> > > So, does this information help?
> >
> > Yes, it does. :-)
> >
> > Greetings
> > Marcus
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp