WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tabbed interface on web pages

for

From: Bryan Garaventa
Date: Oct 3, 2013 10:25AM

That is a good article.

You can also use aria-expanded on an element with role=tab to indicate the
expanded state, which I've found to be more informative because it announces
"open" or "closed" for screen reader users.

There are also some important differences between accordions and tabs that
people need to be aware of, the lines of which seem to be blurred in the
comments. An ARIA tablist with role=tab should not be used on accordions.

----- Original Message -----
From: < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Thursday, October 03, 2013 3:00 AM
Subject: Re: [WebAIM] Tabbed interface on web pages


> Marco Zehe also has a nice, brief, and more recent account of ARIA tabs at
> http://www.marcozehe.de/2013/02/02/advanced-aria-tip-1-tabs-in-web-apps/.
> Also suggest reading through the comments.
>
>
> Jason Kiss
> <EMAIL REMOVED>
> http://www.accessibleculture.org
>
>
>
>
> On 3/10/2013, at 10:10 PM, Alastair Campbell < <EMAIL REMOVED> > wrote:
>
>> Jason Kiss's examples here are a good start (if the whatsock framework is
>> more than you were looking for):
>> http://accessibleculture.org/articles/2010/08/aria-tabs/
>>
>> Worth reading this previous thread though, there are some usability
>> implications until people get used to the different interaction approach:
>> http://webaim.org/discussion/mail_thread?thread=5914
>>
>> hth,
>>
>> -Alastair
>> >> >> >
> > >