W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2001

Re: <noscript> interfere with screen readers?

From: David Woolley <david@djwhome.demon.co.uk>
Date: Sat, 2 Jun 2001 08:49:01 +0100 (BST)
Message-Id: <200106020749.f527n1l25989@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org
> 
> It may separate from main subject, but above all that markup is invalid:
> 
> FORM element can't have inline elements just under itself.
> SELECT element must be markup in block element.

These are not true for HTML 4 transitional.  

> LABEL element can't have block element just under itself.
> NOSCRIPT element is a block element, and NOSCRIPT element have block element just under itself.
> 

Unfortunately these are true.  Assuming that you have a DOCTYPE and
a title element, the only validation error is the NOSCRIPT in a %inline
context.

> If that is an XHTML document, INPUT element is an empty element. The start tag must end with " />".

There is no evidence that XHTML was intended.

> Or, if it becomes a HTML document, SELECTED attribute need be omitted. In short, it is specified SELECTED instead of
> SELECTED=SELECTED.

SELECTED=SELECTED is perfectly valid HTML even if there may be some
broken browsers that don't accept it.  Putting just SELECTED doesn't 
omit the attribute, it is simply a shorthand for the full form.

If you want a neutral block element, you should use DIV, not P.
Received on Saturday, 2 June 2001 04:05:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:55 GMT