WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Landmarks

for

From: Christine Hogenkamp
Date: Jan 14, 2020 12:46PM

For what it's worth, I just happened to test this in NVDA, and if the
landmark doesn't have role="main" etc used, it doesn't show up in the
Elements List section for Landmarks. It may seem redundant to have both
but does appear necessary/not redundant for some assistive devices.

--
*Christine Hogenkamp*
Front-end Developer

CONTEXT CREATIVE
317 ADELAIDE ST. W., #500 | TORONTO, ON CANADA | M5V 1P9
<https://maps.google.com/?q=317+ADELAIDE+ST.+W.,+%23500%C2%A0+%7C%C2%A0+TORONTO,+ON+CANADA%C2%A0+%7C%C2%A0+M5V+1P9&entry=gmail&source=g>

On Tue, Jan 14, 2020 at 2:02 PM < <EMAIL REMOVED> >
wrote:

>
> ---------- Forwarded message ----------
> From: "Swift, Daniel P." < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 14 Jan 2020 17:52:56 +0000
> Subject: Re: [WebAIM] Landmarks
> I'm a little late getting into landmarks. I have a follow-up question to
> this thread. Is it redundant and unnecessary to include both the landmark
> and the HTML5 element? For example, is there any harm (from a SR
> perspective or otherwise) of using <header role="banner"> or <main
> role="main"> for instance? In my reading, it seems like redundancy is
> okay, but I know that from past experience, having the SR repeat the same
> things multiple times is obviously a bad thing.
>
> Thanks!
>
> Dan Swift
> Senior Web Specialist
> University Communications and Marketing
> West Chester University
> 610.738.0589
>
>