Description
Consider the following markup:
<div role=tablist>
<button role=tab aria-selected=false>foo</button>
<button role=tab aria-selected=true>bar</button>
</div>
<article>
bar content goes here
</article>
running a bunch of automated checkers, no issue is raised that there is no association between the selected tab and its content. which is not unexpected, since the aria spec says authors SHOULD ensure there's an association between the currently active tab and tabpanel.
But, the issue here is there's no explicit role=tabpanel element at all, and from my reading of the spec it seems more of an "well if you're creating a tab widget of course you would mark elements as tab panels" - but there is no overt author requirement to do so.
Is this a gap? Or, is there an unstated opportunity for a tablist to not just be used for showing/hiding tabpanels - but other non-tabpanel content as well? (i say this not because i think it's a good idea, but as the only logical explanation i can think of for why there is no overt requirement that if someone implements tabs within a tablist - that they could reasonably no also be required to declare at least one element in the UI as a tabpanel).