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: Paul J. Adam
Date: Apr 17, 2013 1:02PM

Mark up your HTML5 sections with WAI-ARIA Landmark roles and give them an aria-label, i.e. <nav role="navigation" aria-label="Navigation">. The aria-label should be announced as the accessible name for that container.

Don't limit ARIA to just dynamic content, role=button is great for faux button elements, aria-required=true great for required fields.

If you're planning for the future WAI-ARIA support will only grow and become more consistent just like HTML5 and CSS3.

Paul J. Adam
Accessibility Evangelist
www.deque.com

On Apr 17, 2013, at 1: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
>
>