Geoffry,
I am not sure how to answer your question. I don't know if this is
recommended or best practice. My issue is, I have a very large set of
data (key,value) in xml format. This xml file is to be displayed in the
browser and edited. So, I need to put it in a table, and put the values
an i
> It has always been my assumption (from an accessibility) point of view
> that headers (h1, h2 etc) should always read like a table of contents.
> Hence h1 would be the name of the site, even if it is "hidden" and
> preference given to an image logo or such. News stories should be, in
> theory, h2
---
I always assumed that on a news site, for example, every headline would
be an H1, whereas every subhead would be an H2. I realize there's really no
difference in using H2 for every headline and H3 for subheads, I just
---
haven't set up my news-related pages that way.
Geoffrey:
It has always
Is this a 'best practice' or is it recommended for inclusion in future RFCs?
I'm familiar with the idea of having exactly one id="unique" per page, but
H1? I always assumed that on a news site, for example, every headline would
be an H1, whereas every subhead would be an H2. I realize there's reall
Geoffrey Hoffman wrote:
> Yes, inline styles trump (overwrite) rules set for the element,
Only in the sense that when a property is set both in a style attribute
and elsewhere, that specific property gets the value set in the style
attribute - and only when the !important specifier does not mak
