Atomic Accordion element for Elementor Editor V4

[rajin-skele]

Describe the Problem

Elementor Editor V4 is moving toward a more atomic, composable workflow, but there is currently no dedicated atomic Accordion element that fits naturally into that system.

Accordion-style UI is very common for FAQs, product details, service breakdowns, legal disclosures, onboarding sections, account panels, and mobile content compression. Right now, creating these patterns in a clean atomic way is either not possible or requires workarounds with containers, custom interactions, custom CSS/JS, or older widget-based approaches that do not feel native to the new model.

This creates a few problems:

• it slows down building common interface patterns
• it breaks the consistency of the atomic workflow
• it makes reusable design systems harder to maintain
• it pushes users toward custom code for something that should be a core structural element
• it is harder to create accessible, predictable accordion behavior in a native Elementor way

For users trying to build modern component-based systems in V4, Accordion feels like a missing foundational element.

Propose a Solution

It would be great to add a native Atomic Accordion element to Elementor Editor V4.

Ideally, this would work as a first-class atomic element that can be inserted, styled, and repeated like other V4 building blocks. A good implementation would include:

• accordion item structure with a trigger/header and a content panel
• support for multiple items in one accordion
• option for single-open or multi-open behavior
• option for default open item(s)
• accessible keyboard and ARIA behavior out of the box
• full support for nesting standard atomic elements inside the accordion content
• styling controls for header, content, spacing, borders, icons, and open/closed states
• support for reusable classes, variables, and global styling patterns

This would make it much easier to build FAQs, disclosure panels, settings sections, and other collapsible UI patterns in a way that feels fully aligned with the V4 atomic direction.

Additional Context

Accordion is one of those UI patterns that appears in many real projects:

• FAQ sections
• pricing comparisons
• course or lesson outlines
• product specs
• account/settings panels
• mobile-heavy layouts where content needs to be compressed

Right now, these often require workarounds or older patterns that do not feel native to the atomic editor experience.
A native Atomic Accordion would help users stay inside Elementor’s intended V4 workflow instead of reaching for custom code or pieced-together solutions.

If helpful, I’d suggest treating it as a foundational interactive element alongside other layout/content primitives, rather than only as a legacy-style widget.

Agreement

• I confirm I have read and followed all the guidelines and instructions outlined in the Feature Request form.
• I agree that my discussion may be closed without further action if it doesn't meet all the requirements outlined in the Feature Request form.