WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Carousels again

for

From: Mallory
Date: Jul 16, 2020 10:10AM

A named section would work. The point of having an aria-anything around the thing at all was to denote that there was this whole carousel widget and its edges to those who can't see it.
<section aria-label="[name] carousel">
... carousel stuff...
</section>
Should be fine. And if there's a screen reader out there that ignores even named regions, no big loss, and while I get that sections are so overused that some AT ignores it, if they ignore them when used as intended, it's a bug on their end, like VoiceOver users not being exposed to list semantics in a navigation menu (and honestly, they may not miss that. Menu lists are more likely to be navigated by the links inside than by list-item for example anyway).

You could also name the section with a heading
<section aria-labelledby="aheading">
<h2 id="aheading">[name] carousel</h2> (or whatever)
...carousel stuff with h3, h3, h3, h3 (headings suggested by Birkir, levels just as an example)
</section>
Then the next section outside the carousel has the same heading level:
<h2>next content type section</h2>
For screen reader users who pay attention to heading levels (note, not all do), the fact that the next heading is back at the level of the section heading can suggest that we're out of the carousel content.

cheers,
_mallory

On Thu, Jul 16, 2020, at 2:22 PM, <EMAIL REMOVED> wrote:
> W3C landmark examples also says:
>
> complementary landmarks should be top level landmarks (e.g. not contained
> within any other landmarks).
>
> https://www.w3.org/TR/wai-aria-practices/examples/landmarks/complementary.ht
> ml
>
>