Hello Kim,
When you use accesskey please be sure to identify it using the title
attribute for the anchor. I normally use numbers when using
accesskeys. That helps remove the possibility that I'll be overriding a
key that is used for another function.
On the H1 issue, there are many people that think using an H1 around the
logo or hidden text. Unfortunately, that is improper. Your H1 should
be visible and should support the title of the page.
In my opinion your H3 elements do not qualify as real
headings.
Probably the easiest way to explain how heading tags should be used is to
relate the web page to a chapter in a book. Screen readers do not read the
page title, unless coming through a search engine or a link that uses the title
of the page the link goes to. Therefore, the H1 is the first heading that
should be used.
When we examine further we find subsections within the chapter.
Those subsections are not small paragraphs. So, I would ask why would you
use a heading tag to lead into a single paragraph? There are search engine
optimization companies and web designers that don't understand how these things
work. They regrettably lead people into unfortunate paths or
errors.
Always think of a web page like a chapter within your domain's
book. And remember, books have sections where a series of chapters fit
within that section. That would fall into a directory
situation.
Your H3 elements should be bold text instead of
headings.
I'm glad you have that page meeting Bobby AAA conformance. However,
Bobby is only a machine validator. Since I don't know Danish I'm stuck in
helping further. If you have an English version I would be happy to go
over it further. There may be a few more things you can do to meet WCAG
1.0 AAA conformance. Let me know.
I
hope this helps.
Sincerely,
Lee Roberts
From: Kim Kruse [mailto:[EMAIL PROTECTED] Sent: Sunday, July 04, 2004 3:15 PM To: [EMAIL PROTECTED] Subject: RE: [WSG] Hi Lee,
>Hello
Kim,
>Strict requires all
pages to be opened in the same window.
OK... I thought the
onkeypress combined with onclick would do OK since it validates
strict
>Regardless of how you
do the _javascript_ it will not provide an accessible option. My
recommendation would be to remove the >onkeypress and use tabindex and
accesskey. Then the person can open those links in new windows. I
would have the links >open in a new window and that window be a regular
window - not like you have now.
OK... I'll follow your
recommandation and use accesskey instead.
>Let us discuss
heading tags for a moment. You seem to be using your heading tags
improperly. Your H1 tag is the same on all >pages and linked to your
homepage. That is improper. H1 tags help define the topic of the
page. Subsequent heading tags >should support or be a sub-heading of
the previous heading. .
I use the H1 as a general
describtion for the group (forside) and then I use the H2 to identify the
topic for the page in focus. Is that wrong?
>Your H3 headings seem
to be used for font sizing. You cannot
use >heading tags for font size declarations. They must be >used for
real headings
No... they are used for
paragraph headings (Describtions)
>For example, in HTML, use H2 to indicate a
subsection of H1. Do not use headers for font effects.
So it may be that I use the H1 tag in
untraditional way but still according to the describtion you give... well
almost.
>I hope this
helps further.
Yes it does... but
I'm also quite confused. I thought the way I set up the page would better if
you can't see the pageand have to use a screenreader. Is it better to
use the H1, H2 and H3 tags the way you described or is the way I use them also
OK? (and that would be H1=group describtion, H2=page describtion and H3 as
describtion for the paragraphs which are short news)
I hope I don't ask
too much but I find this stuff rather complicated.
Thanks for all your
help
Kim
>Sincerely,
>Lee
Roberts
|
- RE: [WSG] Rimantas Liubertas
- RE: [WSG] Mike Pepper
- RE: [WSG] Rimantas Liubertas
- RE: [WSG] Mike Pepper
- [WSG] Kim Kruse
- RE: [WSG] Lee Roberts
- RE: [WSG] Kim Kruse
- RE: [WSG] Lee Roberts
- RE: [WSG] Kim Kruse
- RE: [WSG] Kim Kruse
- [WSG] Lee Roberts
- [WSG] Wasabi
- Re: [WSG] Jay Hills
- [WSG] Daniel Wagner-Hall
- [WSG] Steven Clark
- [WSG] Tom Livingston
- [WSG] klessa