|
|
Posted by Spartanicus on 08/11/06 08:31
"Jukka K. Korpela" <jkorpela@cs.tut.fi> wrote:
>I'm not sure I see what you point really is
>here, since your messages are difficult to see due to _redundant_ quoting in
>them (e.g., a fullquote followed by a one-liner),
I had noticed myself shortly after posting, a most uncharacteristic
mistake for me to make, as such I question the value of drawing
attention to it.
>but if you're telling
>people to dump <h1> in favor of <title>, you're completely wrong.
No that's not what I've been saying, and that is easy to distill from
what I wrote had that been the intention. Used correctly a document's h1
content only needs to work within the context of the site, it should
only provide the page heading. Used correctly a title of a page should
work outside of the context of the site, it should start with the page's
h1 content followed by content that establishes the context that will
allow it to stand on its own.
>> In the audio
>> domain a screen reader would read the title followed by the h1
>> content,
>
>Perhaps. You cannot know how each browser treats the two distinct elements,
>and shouldn't care too much. The <title> element specifies an external title
>for the document, suitable for use in a reference outside the document
>itself, e.g. in a list of Favorites. It need not be rendered at all by a
>browser, and it's practically never rendered as part of the document proper.
Nothing is guaranteed to be rendered, so that's a non issue. What
matters is what we can reasonably expect to happen, in this case every
browser I have on my system renders page title content. IBM HPR, Jaws
and Window Eyes all speak it, Opera doesn't speak it, but Opera's voice
mode is a technology teaser which currently has no practical
application, Opera is not suitable as an AT browser.
>>> 2) Going a bit OT: In the context of making parts of a <h1>
>>> disappear. Do search engines dislike it when you set display: none;
>>> to text?
>>
>> SE's do not parse stylesheets.
>
>Perhaps they don't, perhaps they do - now or in the future. Actually,
>setting display: none has become one of the common methods of keyword
>spamming, so search engines might decide to try to detect such tricks.
This again is about what we can reasonably expect to happen. There are
no indications to suggest that any SE parses CSS. It is unreasonable to
expect that they would ever do so for the purpose of finding CSS hiding
tricks since there are many ways to make content invisible to most users
(using various technologies), using CSS for example by setting
display:none, visibility:hidden, positioning content off screen, by
specifying a colour contrast to low to detect by the human eye etc.
There are many valid reasons to do any of the above, these methods are
often used for such valid reasons, thus penalizing a site for using such
CSS would cause serious problems.
--
Spartanicus
Navigation:
[Reply to this message]
|