WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Value and prioritization of large-scale things a web site can do for improved accessibility

for

From: Dave Merrill
Date: Apr 17, 2013 1:08PM


Would aria-labelledby be useful for static content whose best description
was NOT in the first heading inside it?

My overall goal to come up with a cohesive and useful set of tools for site
template designers to make their (largely static) content as widely
accessible as possible. In that sense, aria-labelledby might be worth
providing for the cases where it was useful, even if that wasn't most of
them.

But overall, as I think about it, I think the majority of our customer base
isn't that sophisticated about accessibility. They may well not have an
accessibility specialist even, just somebody with a flair for design and
some HTML experience, possibly also a coder, who's tasked with template
creation. For them, a simpler set of tools that was harder to make a mess
with is probably a better strategy.


On Wed, Apr 17, 2013 at 2:54 PM, Steve Green < <EMAIL REMOVED>
> wrote:

> I think that landmarks are fine but ARIA is primarily intended for dynamic
> content. There comes a point when adding more semantic markup actually
> starts to reduce the accessibility because the 'noise' gets in the way of
> the content. I would therefore reserve the use of ARIA for dynamic content,
> and even then only when it is actually needed. Some well-designed dynamic
> content does not need it.
>
> I think there is already an obvious implicit relationship between a
> heading and its container, and that aria-labelledby is really intended for
> use where relationships are not obvious or implicit.
>
> Steve
>
>