Description

An accordion is a list of headers that hide or reveal additional content when selected.

An accordion is similar in purpose to a tabbed interface, a list of items where exactly one item is expanded into a panel (i.e. list items are shortcuts to access separate panels).


Usage & Behavior

An accordion should be used when 

General guidelines

Internal Logic

The accordion component delivers large amounts of content in a small space through progressive disclosure.

Default

The first section content in the accordion should be open when first loading the page.

structure


States (TBD - not final design)

 State

Image

Comment

Section header close

Section header open

Section header hover

Selected content mark

Special States (TBD - not final design)

State

Image

Comment

Selected content mark

Section header with checkbox

Section header with warning

Interaction

Transitions

Clicked Section will side open while the former open section in the accordion will close at the same time

Best practices

Use:

Don’t use:

Usability guidance

Accessibility compliance

<<In general each component should be A11y complied,  please follow the 3 guidelines linked below. At the very least we should document that each component is in compliance with each of the 3>>

Focus management

<<How will the component work with keyboard only - without a mouse. Can be reference if written above

We already set a general guidelines described in /wiki/spaces/UX/pages/308969693 >>

Screen reader support 

<<Make sure the components support screen reader for content or behaviour where needed - see /wiki/spaces/UX/pages/308248620 >>

Contrast & size compliance

<<Visual designers must comply with the minimal of /wiki/spaces/UX/pages/301498483 for each component>>

Design

Zeplin link

Screen thumbnail

https://zpl.io/VkmX6dq



Code

<<a box containing the code - discuss with Femi>>