W3C home > Mailing lists > Public > public-wai-ert@w3.org > July 2005

Re: Formalization of rule 91

From: Vicente Luque Centeno <vlc@it.uc3m.es>
Date: Mon, 4 Jul 2005 20:41:08 +0200 (CEST)
To: Chris Ridpath <chris.ridpath@utoronto.ca>
Cc: public-wai-ert@w3.org
Message-ID: <Pine.LNX.4.61.0507042011150.12445@violin.it.uc3m.es>


>> * It does not validate in XHTML 1.1 (nor XHTML Basic).
>> 
> I modified your original document so it has associated labels. The 'label' 
> elements surround the 'a' elements.
> http://checker.atrc.utoronto.ca/docs/Resource%20booking.htm

I was (a little) wrong. My example (as well as yours) also validated 
against XHTML 1.1 (and Strict, and Transitional). It does not matter 
whether the 'a' surrounds the 'label' or viceversa. Validation is achieved 
in both cases.

However, with my Mozilla browser, the link is followed and the checkbox is 
selected ALL AT THE SAME TIME! So, if I JUST want to see the bookings of 
resource #1, after visiting the link, I MUST UNCHECK the checkbox. None of 
our examples validate against XHTML Basic (because their editors noticed 
that focusable elements should not nest). That XHTML Basic rule prevents 
against this problem.

> I'm not sure how browsers handle this but, as it is valid code, they should 
> be able to handle it.

Validation does not guarantee accessibility. I am afraid there are lots of 
valid things that don't make sense (that's why WAI was created). If all 
the accessibility could fit into validation, WCAG WG would be working only 
in DTD's and Schemas. I am afraid there are some other constraints that 
can not be expressed in a DTD or Schema. As an example: my over 60 XQuery 
restrictions ;-). Very few of them could fit in a DTD or Schema.

The good point, however, is: everything outside my 60 XQuery expressions 
can only be manually evaluated (or with a very complex program). :-). It 
seems to me that most automatable rule related exclusively to markup can 
be described in XQuery. I exclude the ones referring idioms, CSS, 
JavaScript, multimedia, ...

Anyway, and coming back to our example, is there a better way to have 
both link and label functionality sepparately? My answer is: only if the 
title attribute (of the input) is used instead of a label.

Best regards.
Received on Monday, 4 July 2005 18:41:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:26 GMT