WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Heading or Not?

for

From: Birkir R. Gunnarsson
Date: Mar 28, 2013 6:10PM

I think, as a user at least, that if this is just part of a larger
text, not part of an itemized list of lists it should not be a
heading.
The importance of healthy diet.
Research shows that ... ....
- a
- b
- c

If it is set up as a list of lists (not necessarily semantically, but
if the text is set up that way) one may consider using headings.
vegetables are:
- a
- b
- c

meat is
- d
- e
- awesome if it is a tenderloin.

Then h4 or h5 headings might make sense (too many headings, especially
h1 or h2 or h3 truly distract the screen reader user and end up being
very irritating and unhelpful, too much of a good thing is not a good
thing).

Agai,Again, this is just my end user opinion, so take it as such. ;)
-B


On 3/28/13, David Ashleydale < <EMAIL REMOVED> > wrote:
> Oh man, I've always wished there were a "list header"!
>
>
> On Thu, Mar 28, 2013 at 3:45 PM, Jared Smith < <EMAIL REMOVED> > wrote:
>
>> This is a very interesting question. I don't think there is a "right"
>> answer. If the text in question were standing alone, I probably would
>> not mark it up as a heading. There would be little additional utility
>> provided to users by having this text in a list of headings or making
>> it navigable.
>>
>> If, however, there were multiple sections (maybe one for vegetables
>> and one for grains), then I'd be more likely to mark all of them up as
>> headings because differentiating them semantically could be useful.
>>
>> In the end, there's very little difference to the user.
>>
>> Interestingly, HTML3 had a <lh> (list header) element designed exactly
>> for this type of thing, but it never caught hold -
>> http://www.w3.org/MarkUp/html3/listheader.html
>>
>> Jared
>> >> >> >>
> > > >