WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Odd NVDA reading of role=contentinfo

for

From: Birkir R. Gunnarsson
Date: May 7, 2013 3:37PM

I am seeing a lot of examples of div / landmark roles used with
equivalent html5 roles creating a bit of a landmarks chaos on
websites, not surprised, we are in a transition phase.

Temporarily this definitely makes the use of either set of navigation
markup techniques less useful, as a page now often has 20 to 50
"regions" or landmarks of some description.
(Jaws, at least announced the section element as "region", every
article element is announced etc.).

Definitely make sure to use one or the other, or use one as fallback
for the other where possible, using them together almost makes them
unusuable, especially on sites with a lot of content.
Thanks
-B


On 5/7/13, Jason Kiss < <EMAIL REMOVED> > wrote:
> Can you reverse the markup so the containing div becomes the footer
> element and the nested footer becomes a div, and then have
> role="contentinfo" on the footer element? Whatever you do, the footer
> will be announced as contentinfo landmark by NVDA in FF, as will any
> other element with an explicit role="contentinfo".
>
> On Wed, May 8, 2013 at 9:16 AM, Angela French < <EMAIL REMOVED> > wrote:
>> The footer is nested inside the div. Here is the context: Each page has
>> our standard application footer with a link to our privacy notice, our
>> non-discrimination notice and our contact page. At the bottom of every
>> page's content area is a trademark usage statement that we are required to
>> put on every page of this particular site. Thus the role="contentinfo"
>> and the <footer>.
>>
>> Angela French
>>
>>>