That said, I still think we should add aria-label attributes to all elements. There are many of these on each page, and without a label they're each identified by screen readers as "Navigation region" - there's no means of clarifying which navigation region is which. If we add aria-label, screen readers use the value of aria-label when identifying the region (e.g., "Toolbar Items Navigation Region", "Breadcrumb Navigation Region", and the like)
@falcon03 and later on:
Well, I think that hearing messages like "entering navigation", "entering main" and so on doesn't give a real "context". So, as a blind user, I'm completely in favor of adding aria-labels.
@pratikp1 and finally:
Having an effective label is essential. I would like some discussion about that for D8 or D9. Let's see if we can make it more understandable. It will go a long way toward having users understand that landmarks can actually be useful.
I don't know why there isn't any in Seven, but in Bartik, we can find the
<nav> element in:
And in modules it's in:
Where else do we find them?
Some more info on using aria-labels:
|Task||Novice task?||Contributor instructions||Complete?|
|Reroll the patch if it no longer applies.||Yes||Instructions|
|Manually test the patch||Yes||Instructions|
|Add automated tests||Instructions|
|PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 88,692 pass(es).|
|FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 2052473-76.patch. Unable to apply patch. See the log in the details link for more information.|
|FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 2052473-63.patch. Unable to apply patch. See the log in the details link for more information.|