E-mail List Archives
Re: ARIA tab interface
From: Tom Livingston
Date: Oct 17, 2019 5:58PM
- Next message: mhysnm1964@gmail.com: "Re: UX design query for a11y and screen reader user"
- Previous message: glen walker: "Re: ARIA tab interface"
- Next message in Thread: Tom Livingston: "Re: ARIA tab interface"
- Previous message in Thread: glen walker: "Re: ARIA tab interface"
- View all messages in this Thread
I will look into this. Thanks for the help.
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
- Next message: mhysnm1964@gmail.com: "Re: UX design query for a11y and screen reader user"
- Previous message: glen walker: "Re: ARIA tab interface"
- Next message in Thread: Tom Livingston: "Re: ARIA tab interface"
- Previous message in Thread: glen walker: "Re: ARIA tab interface"
- View all messages in this Thread