WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Hidden headings with aria-labelledby or just aria-label best for for labelling landmark regions?

for

From: Robert Fentress
Date: Jul 23, 2018 8:51AM

So is the issue with the Farmers <http://farmers.gov>; page the repetitive
use of the phrase "navigation," especially as things are surfaced in NVDA?

That raises another issue in my mind, which is whether to use the phrase
"navigation" in labels for `<nav>` regions. To me, this seems duplicative
as well. If you are using a navigation region, then screen readers will
surface something like the phrase "navigation" anyway, so it seems kinda
pointless. It sort of like providing alt text for an image that says
"Image of a person on a bicycle," rather than, "Person on a bicycle." That
is why, rather than label my site navigation "Site Navigation", I'm
labelling it "Site". But, then, I'm using aria-label, which is one of the
arguments for using it. If you used aria-labelledby, you'd have to do
something more involved to avoid that extra noise, like this: `<h2><span
id="label">Site</span> Navigation</h2>`. I mean, I guess that's not a big
deal, but it seems less than ideal somehow.

On a separate note, I see the Farmers page has nested `<nav>` regions.
Functional
Accessibility Evaluator <https://fae.disability.illinois.edu/> flags things
like this as errors
<https://fae.disability.illinois.edu/pages/164c7921ad31c31b/rc/landmarks/page/1/landmark10/>,
though I haven't been able to find anything in any specs that supports
this. Other checkers don't seem to flag it either. Is this an error, a
best practice violation, or neither? Opinions? Why is this problematic,
aside from the best practice of not having too many navigation regions in
general?

On Mon, Jul 23, 2018 at 10:09 AM Meacham, Steve - FSA, Kansas City, MO <
<EMAIL REMOVED> > wrote:

> I've found that putting aria-label on a <nav> element can also be
> problematic. See farmers.gov for an example.
>
>