WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible tab generation using HTML5 and content preloading

for

From: Scott González
Date: Nov 15, 2012 6:07AM

On Wed, Nov 14, 2012 at 8:59 PM, Bryan Garaventa <
<EMAIL REMOVED> > wrote:

> * Any element that is a tab element should not include any other active
> elements (A or Button tags, etc.)
>

What about close buttons?

Also, I'd like to know why you chose not to activate tabs immediately upon
navigation as the ARIA authoring practices suggest. I assume this is to
give screen reader users time to hear which tab they're on before
activating. I did a lot of investigation into how tabs are activated and
have details listed here:
https://github.com/jquery/jquery-ui/pull/666#issuecomment-6192174