E-mail List Archives
Re: Accordion semantics?
From: James Nurthen
Date: Jun 18, 2014 9:28PM
- Next message: Detlev Fischer: "Re: Accordion semantics?"
- Previous message: Sean Curtis: "Re: Accordion semantics?"
- Next message in Thread: Detlev Fischer: "Re: Accordion semantics?"
- Previous message in Thread: Sean Curtis: "Re: Accordion semantics?"
- View all messages in this Thread
I agree with Bryan.
I also find the keyboard navigation very confusing for a keyboard-only user.
I've started telling people to code accordions as a bunch of expandable
I'm going to raise an issue against the ARIA 1.1 Authoring Practices to
provide an alternate pattern like this for accordions.
On Wed, Jun 18, 2014 at 7:29 PM, Bryan Garaventa <
<EMAIL REMOVED> > wrote:
> Personally I've never been fond of using ARIA Tab constructs for
> because it's impossible to tell the difference between a tab group and an
> inline accordion, because the feedback is the same for screen reader users.
> E.G if you have a tab group nested in an accordion, how do you know which
> which for instance, which may be important because accordions render
> inline whereas tabs render content after a tablist group.
> Is there something wrong with just keeping it simple?
> ARIA Toggles:
> Expandable ARIA Links:
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Jesse Hausler
> Sent: Wednesday, June 18, 2014 5:32 PM
> To: WebAIM Discussion List
> Subject: [WebAIM] Accordion semantics?
> Thoughts on the best semantic for an accordion component?
> I'm good with the keyboard and ARIA recommendations in the ARIA Authoring
> I'm just don't care for the semantics in their only example:
> Paired headings and divs as the way to go?
> > > messages to <EMAIL REMOVED>
> <mailto: <EMAIL REMOVED> >
> > > >