WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Aside element inside and aside?

for

From: David Engebretson Jr.
Date: Jul 23, 2022 12:54AM

I agree. As long as your nested regions are labelled with enough context to the meaning of the region then nest to your hearts/region content.

Without meaningful/accessible labels on the regions, however, you'll find yourself in region soup where people who use assistive technologies won't be able to understand the layout of your pages.

Meaningful regions are as important as meaningful links, and proper heading structure, in my humble opinion. Accessibility and WCAG compliance is all about usability at the core.

Cheers,
David



-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Friday, July 22, 2022 9:16 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Aside element inside and aside?

Nested landmarks aren't disallowed. You see that often with navigation landmarks inside of banner landmarks. Or even navigation inside of navigation.

Complementary inside a complementary might be a little weird, but if they have aria-labels, it could be ok.

My original answer was from an html validation perspective. It's valid.
The original question didn't specify if they were looking for "is this allowed" or "is this a good idea".

On Fri, Jul 22, 2022 at 8:00 PM Jon Gunderson < <EMAIL REMOVED> >
wrote:

> Not a good idea from an accessibility point of view to nest aside
> elements, since aside elements create complementary landmarks. Nested
> aside elements will be confusing to screen reader uses and “polute”
> this list of landmarks view.
>
>