WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Landmarks

for

From: Isabel Holdsworth
Date: May 2, 2019 5:53AM

Thanks guys. It's actually a <div> with a banner role, sometimes
inside a <div> with a main role, sometimes randomly inside a dialog.
Sometimes they wrap it around heading tags.

These random banners are quite a clear-cut fail, but what about
instances where there's a <div role="main"> wrapper around the main
content, but the header, navs and footer don't have landmarks? Is this
a fail too?

I know this issue won't stop anyone from using the content, but we
have time to do a comprehensive audit, and the devs will probably have
time to fix most of the issues we find, so why not!

Cheers, Isabel

On 02/05/2019, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
> You could pin it un 1.3.1 or 4.1.1 (ARIA is not being used according
> to spec, so it feels like 4.1.1 is a valid argument).
> I push for people using the big 3 correctly, header/main/footer
> (banner/main/contentinfo) but usually stop there, because in my
> usability testing I didn't see anyone use landmarks and too many
> landmarks on a page quickly render them pretty useless.
> Your plague of banner landmarks is probably caused by use of the
> <header> element (it maps to the banner role if it is a child of the
> <body> element and should only be used in connection with <article> or
> <section> elements if not used for the webpage header).
> Jaws is overly generous when it comes to mapping the <header> element
> to a banner landmark.
>
>
> On 5/2/19, Steve Green < <EMAIL REMOVED> > wrote:
>> My view is that it is a violation of 1.3.1 if landmarks are not used or
>> are
>> used incorrectly. In most cases I would expect all page content to be in
>> at
>> least one landmark - there may be exceptions where that is not
>> appropriate
>> but I can't think of any.
>>
>> Steve Green
>> Managing Director
>> Test Partners Ltd
>>
>>
>>