WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Heading Structure - Must vs. Nice to habe

for

From: Birkir R. Gunnarsson
Date: Jan 22, 2018 4:25PM

WCAG 1.3.1 basically says that if information is available visually it
also needs to be able semantically.
So if something looks like a heading, it should be identified as a
heading (either using the appropriate HtML heading element or ARIA).
Also, if one heading appears to be bigger than another heading, that
needs to be communicated programmatically, e.g. by giving it lower
level, and h2 heading should appear bigger than an h3 heading.
So those are the minimum heading requiremens as I interpret them.
If all headings on the page appear the same size, using the same
heading element for all meets WCAG 1.3.1 even if the content is
structured. WE are giving the same info to all users, even when that
info is wrong.
Of course oth heading structure and heading appearance should
describe the content, but that becomes a usability problem.



On 1/22/18, Wolfgang Berndorfer < <EMAIL REMOVED> > wrote:
> Hi Tinkerers,
>
>
>
> Am I right with my impression that SC 1.3.1 describes the *necessity* of
> adequate semantic markup and hierarchy for headings, while SC 2.4.10 advises
> that it's *fine* to have heading information for sections e.g. via
> aria-label additionally or principally to optimize navigation to navs,
> articles, etc?
>
>
>
> Thanks for clarifications!
>
>
>
> Wolfgang Berndorfer
>
> > > > >


--
Work hard. Have fun. Make history.