RE: Live Code for APG: ARIA Accordion design pattern ready for review

"If only one component can be expanded at a time, and expanding a component in a set automatically collapses the previously expanded component, we are using tabs."

I disagree, it depends on the element nesting. Tabs are a different concept because tabs have only one tab stop.

Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
bryan.garaventa@ssbbartgroup.com
415.624.2709 (o)
www.SSBBartGroup.com

From: Birkir Gunnarsson [mailto:birkir.gunnarsson@deque.com]
Sent: Monday, July 18, 2016 9:56 AM
To: 'James Nurthen' <james.nurthen@oracle.com>; public-aria@w3.org
Subject: RE: Live Code for APG: ARIA Accordion design pattern ready for review

Agreed.
The way I envisioned an accordion is as a set of controls that can be expanded or collapsed at will.
All components can be collapsed or expanded, and changing the expanded state of a component does not affect the expanded state of any other component.
If only one component can be expanded at a time, and expanding a component in a set automatically collapses the previously expanded component, we are using tabs.
I wonder whether tabs can encompass a scenario where all tabs are collapsed initially, but once one has been expanded they act like regular tabs.

From: James Nurthen [mailto:james.nurthen@oracle.com]
Sent: Monday, July 18, 2016 12:42 PM
To: public-aria@w3.org<mailto:public-aria@w3.org>
Subject: Re: Live Code for APG: ARIA Accordion design pattern ready for review


Matt,

We have different types of accordions. Sometimes it is allowable to collapse all the panes, sometimes you can expand as many as you like, and sometimes there is one and only one expanded at any time. In this last case expanding one pane collapses all the others. We need to support all of these models.

Regards,

James

On 7/18/2016 9:36 AM, Matt King wrote:

Thank you Bryan!



One thing I don't understand is why it is not possible to collapse the

expanded section.  Why can't all of them be collapsed?



I had also previously thought that one of the differences between tabs and

accordians is that accordians often allow multiple sections to be expanded.



Matt



-----Original Message-----

From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com]

Sent: Sunday, July 17, 2016 11:57 PM

To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com><mailto:bryan.garaventa@ssbbartgroup.com>; ARIA Working Group

<public-aria@w3.org><mailto:public-aria@w3.org>

Subject: RE: Live Code for APG: ARIA Accordion design pattern ready for

review



Okay, files moved, please try this again...



Live page:

http://whatsock.com/test/w3c/ARIA%20Accordions/demo.htm



Download:

http://whatsock.com/test/w3c/ARIA%20Accordions.zip



Bryan Garaventa

Accessibility Fellow

SSB BART Group, Inc.

bryan.garaventa@ssbbartgroup.com<mailto:bryan.garaventa@ssbbartgroup.com>

415.624.2709 (o)

www.SSBBartGroup.com<http://www.SSBBartGroup.com>



-----Original Message-----

From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com]

Sent: Sunday, July 17, 2016 6:28 PM

To: ARIA Working Group <public-aria@w3.org><mailto:public-aria@w3.org>

Subject: Live Code for APG: ARIA Accordion design pattern ready for review



Hi,

The code for the accordion wireframe is ready, which can be tested at

http://snoringfoot.dyndns.org/Webserver/ARIA%20Accordions/demo.htm



At present this is just the coded implementation since my primary objective

was to simply build out what works first, then document it after we finish

any tweaks. For this reason, I'm hosting this temporarily on a test server.



Also, you can download this zip file at

http://snoringfoot.dyndns.org/



Included within this is a vanilla JavaScript helpers lib I've cobbled

together over some years now, which should aid in the process for building

out these widgets in the future. This is included within the file

"helpers.js'.



The design pattern uses the new model for Accordions, which is the use of

individually focusable toggles in combination with aria-expanded to convey

the active state of each toggle.



The setup for this type of implementation is automatically scalable, meaning

that it can include any type of embedded control type within the dynamically

expandable sections, including other complex ARIA widget controls, or even

embedded accordion controls to nest functionality. This is why the named

regions are important for intuitive grouping.



This too works on mobile touch screen devices, and within setup.js,

redundant event handling shows how the same script can be applied to

non-native triggering elements such as Div or Span elements in place of

native links or buttons for use as accordion toggles.



Within this demo, the styling and content are just what I've thrown

together, but all can be changed however you like. It probably needs some

positioning work for the accordion section content for instance. The

triggering elements are presently A tags, but these can be changed to native

buttons, or even simulated elements like Div or Span with tabindex='0' and

role='button', and the scripting will still work accessibly.



Also, please feel free to use the helpers.js file for whatever you wish as

well, it may make this process go faster.



All the best,

Bryan









Bryan Garaventa

Accessibility Fellow

SSB BART Group, Inc.

bryan.garaventa@ssbbartgroup.com<mailto:bryan.garaventa@ssbbartgroup.com>

415.624.2709 (o)

www.SSBBartGroup.com<http://www.SSBBartGroup.com>











--
Regards, James

[Oracle]<http://www.oracle.com>
James Nurthen | Principal Engineer, Accessibility
Phone: +1 650 506 6781<tel:+1%20650%20506%206781> | Mobile: +1 415 987 1918<tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com<sip:james.nurthen@oracle.com>
Oracle Corporate Architecture
500 Oracle Parkway | Redwood Cty, CA 94065
[Green              Oracle]<http://www.oracle.com/commitment>Oracle is committed to developing practices and products that help protect the environment