E-mail List Archives
Re: building accessible javascript accordions?
From: Alastair Campbell
Date: Aug 1, 2013 3:22PM
- Next message: Bryan Garaventa: "Re: building accessible javascript accordions?"
- Previous message: Chagnon | PubCom: "Digital signatures in PDFs"
- Next message in Thread: Bryan Garaventa: "Re: building accessible javascript accordions?"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: building accessible javascript accordions?"
- View all messages in this Thread
Bryan Garaventa wrote:
> For example, I typically recommend making each triggering element either an
> ARIA Toggle using role=button, aria-pressed=true/false, and
> aria-expanded=true/false, or use offscreen text to indicate the role and
> state, both of which work reliably.
Thanks, that makes sense.
> Personally I'm not a fan of making an accordion have only one tab stop,
> because it doesn't make any sense from a usability perspective.
Agree, but for a regular user I would apply the same logic to tabs as
well though. You know the difference, but what signals the change of
model for a regular user?
Cheers,
-Alastair
- Next message: Bryan Garaventa: "Re: building accessible javascript accordions?"
- Previous message: Chagnon | PubCom: "Digital signatures in PDFs"
- Next message in Thread: Bryan Garaventa: "Re: building accessible javascript accordions?"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: building accessible javascript accordions?"
- View all messages in this Thread