W3C home > Mailing lists > Public > public-aria@w3.org > March 2016

Re: Clarification regarding "required owned elements"

From: Michiel Bijl <michiel@agosto.nl>
Date: Wed, 2 Mar 2016 14:42:24 +0100
Cc: public-aria@w3.org
Message-Id: <930B25BC-6ADF-4DDD-9B31-CA153AF7AB2E@agosto.nl>
To: Birkir Gunnarsson <birkir.gunnarsson@deque.com>
Your interpretation is correct; a tablist is a list of tabs (the thing you use to activate a tab panel). Adding the panels to the tablist would make no sense :)

—Michiel

> On 1 Mar 2016, at 20:43, Birkir Gunnarsson <birkir.gunnarsson@deque.com> wrote:
> 
> Oh wise ones.
> I got a question.
> When a role has required owned elements, does that mean that any other element owned by that role is invalid?
> e.g.
> the tablist role must own elements with role=”tab”
> What if the tablist role also owns elements with role tabpanel
> Example:
> <div role=”tablist”>
> <div role=”tab” id=”tab1” aria-controls=”tabp1” aria-selected=”true” tabindex=”0”>Tab 1</div>
> <div role=”tabpanel” id=”tabp1” aria-labelledby=”tab1”>
> Some content
> </div>
> </div>
>  
> If I were designing an ARIA checker, should I call a violation for this code because role tabpanel cannot be owned by role=”tablist”?
> I am 95% sure that is the case, but I want to check with the masters of the art.
> Thanks
> -Birkir
Received on Wednesday, 2 March 2016 13:42:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 13:42:52 UTC