Re: <noscript> interfere with screen readers?

> 
> > > 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.
> 
> What you say is right. My poorly English was the cause about this point.
> However, is it good if even a grammar is valid?
> If it was HTML document, it's better to write it as SELECTED, not SELECTED=SELECTED.
> 
> 
> > 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.
> 
> 
> To be sure, HTML tags and HEAD tags are omissible. However, BODY element and tags are not omissible. Therefore, that sample takes

BODY tags are not required, e.g. this is valid (against the HTML4.soc
catalog in nsgmls, i.e. HTML 4.0 transitional; you can include the full
system identifier with the same result):

   <!DOCTYPE HTML SYSTEM>
   <title></title>
   x

> Generally -- if DOCTYPE is lost, it cannot be said that it's not valid or invalid, either.

But you did say that!

> > If you want a neutral block element, you should use DIV, not P.
> 
> Why?

Because the whole purpose of DIV is to provide an element that is block
like but otherwise has no meaning.

> However, that example uses SELECT element.
> By using SELECT element, one of the choice which has more than one is taken out, and it becomes to a sentence. Therefore, P element

Sentences are inline constructs, not block constructs.  You were faking
a block context in order to get NOSCRIPT accepted but really wanted
an inline construct.

Received on Saturday, 2 June 2001 07:34:22 UTC