Based on the initial accessibility audit of the Accordion component (as part of T341493), including a `disabled` state for the Accordion leads to some potential accessibility issues without satisfying any known use-cases ("should a disabled accordion component be always open? does that mean we gray out the content text or just the toggle heading?").
Given this, we are going to **remove the `disabled` prop** from this component for the time being, since we are about to release it for public usage as part of Codex `v0.15.0`. This will allow us to proceed with our original plan to take this component out of WIP status so that people can start using it.
We are open to re-introducing this property in the future once we have an actual use-case to work with. If/when this happens, we should be mindful to study the relevant patterns in the W3C's Aria Authoring Practices Guide (APG) – in particular, [[ https://www.w3.org/WAI/ARIA/apg/patterns/accordion/ | this one ]].
==== Acceptance Criteria
**Design**
- [ ] Update component in the Figma exploration file so we flag this version
- [ ] Remove accordion's disabled state from the Figma library
**Code**
- [ ] Remove the `disabled` property from the component without otherwise changing its behavior
- [ ] Ensure that the Accordion component made public with the next Codex release