E-mail List Archives
Re: Multiple H1 tags in an HTML5 web page
From: Greg Gamble
Date: Mar 10, 2014 2:16PM
- Next message: Bourne, Sarah (ITD): "Re: Sec. 508 Refresh (U.S.)"
- Previous message: Chagnon | PubCom: "Sec. 508 Refresh (U.S.)"
- Next message in Thread: Jukka K. Korpela: "Re: Multiple H1 tags in an HTML5 web page"
- Previous message in Thread: Chagnon | PubCom: "Re: Multiple H1 tags in an HTML5 web page"
- View all messages in this Thread
Well, considering the cats already out of the bag ... If the relevant content in a section deserves an H1, as per the current specification (spec), how would this be a problem for a user?
All I've heard is that it's not correct. OK, fine ... but why is it not correct? And I'm not talking about a missing "outlining algorithm " or a unknown bug ... I'm talking about a user with current technology.
What difficulties, if any, would they have navigating a page? Is there anyone on this list, who is a user of AT , that can give me first hand knowledge?
I try to create pages that work for all users, and that includes users who are accessing my pages via AT. If doing something by a current spec causes problems for the majority of the users, I'm not going to follow that spec. Conversely, if a spec is deemed by some as incorrect, but works ... I'm going to use it.
Just trying to do what's right for my end users.
Greg
- Next message: Bourne, Sarah (ITD): "Re: Sec. 508 Refresh (U.S.)"
- Previous message: Chagnon | PubCom: "Sec. 508 Refresh (U.S.)"
- Next message in Thread: Jukka K. Korpela: "Re: Multiple H1 tags in an HTML5 web page"
- Previous message in Thread: Chagnon | PubCom: "Re: Multiple H1 tags in an HTML5 web page"
- View all messages in this Thread