WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: ARIA tab interface

for

From: Tom Livingston
Date: Oct 18, 2019 8:13AM

I looked into disclosure. I cannot construct the source to be inline
with the examples and suggested methods. My design does not lend
itself to having the hidden content be the next item in the source. My
buttons are in a row - like tabs - which is why I started down that
path. I think we will be able to default to the first item being
disclosed on load.

As a second part to my issue, is it difficult or even a bad thing to
have a tab system inside of another? The content of my first 'tab' is
another tabbed interface.



On Thu, Oct 17, 2019 at 7:24 PM glen walker < <EMAIL REMOVED> > wrote:
>
> If you have a series of buttons, perhaps the "disclosure widget" would be a
> better pattern.
>
> https://www.w3.org/TR/wai-aria-practices/#disclosure
>
>
> On Thu, Oct 17, 2019 at 3:06 PM Tom Livingston < <EMAIL REMOVED> > wrote:
>
> > That was my initial thought as well, which is why I asked. I guess
> > what I was looking for was if it is a no-no from an accessibility
> > rules stand point. The design makes sense to look at it. They are more
> > like buttons that tabs - visually speaking - and they represent
> > choices. Once a choice is made, related content appears. I was reading
> > about aria-controls and the design doesn't lend itself to some of the
> > build recommendations suggested to make that a viable option. My
> > content is basically a tabbed interface, but like I said, didn't show
> > tab 1 on load.
> >
> > So, is it a bad thing or just not the norm?


--

Tom Livingston | Senior Front End Developer | Media Logic |
ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com


#663399