E-mail List Archives
Re: Should site logos be H# tags?
From: Joelle Tegwen
Date: Nov 16, 2005 6:20PM
- Next message: Paul Bohman: "Re: Should site logos be H# tags?"
- Previous message: Patrick H. Lauke: "Re: Should site logos be H# tags?"
- Next message in Thread: Paul Bohman: "Re: Should site logos be H# tags?"
- Previous message in Thread: Patrick H. Lauke: "Re: Should site logos be H# tags?"
- View all messages in this Thread
When we asked our disability person (who uses a screen reader) he said no.
It should be
H1 How to pay a ticket
The H1 should describe the page. Remember that when the page is loaded
the screen reader reads the <title> too so if you have <title> Minnesota
Judicial Branch - 2nd District</title> and then
H1 = Minnesota Judicial Branch
H2 = 2nd District
H3 = How to pay a ticket
They would be read all of that information twice.
(aside from the horrendous tables that we're slowly working away from) you can see how we've done it http://www.youthhood.org
Joelle
Austin, Darrel wrote:
>There's the age-old semantic debate as to what should be considered an
>actual header.
>
>On our current site, we have the site title, the 'sub site' title, and
>then the content title:
>
>Minnesota Judicial Branch
>2nd District
>How to pay a ticket
>Page content
>
>>From a semantics standpoint, this is usually the argued solution:
>
>H1 = Minnesota Judicial Branch
>H2 = 2nd District
>H3 = How to pay a ticket
>
>But from an accessibility standpoint, does that make as much sense? I'm
>not sure how likely it is that people navigate a site/page via reading
>down the headers, so maybe this isn't a major issue. I will have 'skip
>to content' links at the very top as well.
>
>-Darrel
>
>
>
>
>
>
- Next message: Paul Bohman: "Re: Should site logos be H# tags?"
- Previous message: Patrick H. Lauke: "Re: Should site logos be H# tags?"
- Next message in Thread: Paul Bohman: "Re: Should site logos be H# tags?"
- Previous message in Thread: Patrick H. Lauke: "Re: Should site logos be H# tags?"
- View all messages in this Thread